Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Chore] Migrate gluestack to react-aria #42

Closed
1 of 2 tasks
shawnmclean opened this issue Oct 21, 2024 · 0 comments · Fixed by #46
Closed
1 of 2 tasks

[Chore] Migrate gluestack to react-aria #42

shawnmclean opened this issue Oct 21, 2024 · 0 comments · Fixed by #46

Comments

@shawnmclean
Copy link
Owner

shawnmclean commented Oct 21, 2024

Dropping Expo for now completely as maintaining 2 separate apps and the UI in a cross-platform way is painful.

Gluestack does not have enough examples and components.

This is what the NativeWind guys have to say, which is essentially to maintain 2 separate UI components for expo and web. So it coincides with the pain I'm feeling.

So making the decision to completely drop mobile app and have the app mobile friendly.

NativeWindUI Faq

####What is the difference between cross-platform and multi-platform?

Cross-platform prioritizes writing once and running everywhere which often comes at the cost of the look and feel of your app. Meanwhile, multi-platform prioritizes feeling native on every platform which occasionally comes at the cost of writing platform-specific code. It's worth noting that NativeWindUI will let you use the look/feel of iOS for both iOS and Android (and vice versa); however, we do not encourage it.

####What is native feel?

Native feel refers to an experience that feels as if it belongs to its parent platform (iOS or Android). Our components are designed to provide this native experience while remaining customizable. For a deeper dive into the importance of crafting a native feeling experience, check out this talk by Dan Stepanov at Chain React 2024.

####Does this support web?

Not in the way you think. NativeWindUI strives to achieve native feel with a familiar web-like interface. However, as the web does not have a concept of a 'native' experience, we don't have dedicated flows for that purpose. We recommend using a monorepo where you use your favorite framework for web while using Expo and NativeWindUI for mobile. Meanwhile, you can share your business logic between the two. We'll provide an example of this shortly.

####What if I want a cross platform experience?

We offer a free library for this purpose called React Native Reusables which mirrors shadcn/ui and also utilizes NativeWind for styling.

Action Items

  • Test JollyUI
  • Test NextUI (this one might be the better based on stars)
@shawnmclean shawnmclean changed the title [Chore] Migrate UI to react-aria [Chore] Migrate gluestack to react-aria Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant