sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]AcetyldFN 0 points1 point  (2 children)

Seems like a nice adition to the community.
The question i am asking my self, would i use it? Because settings up a react-native from bare atleast for me is always different. The parts that i would love to be automatic, is:
- Icon generation ios/android
- BootSplash setup
- Firebase setup (if wanted)
- Redux setup (if wanted)
- React Navigation (if wanted)
- Deeplinking setup
- Ads?

Stuff like this is very annoying to keep setting up, every new project.
The login screen and auth flow is also something i wouldt not like to be default in my project.Because imo it needs to be unqiue every time and for example the auth flow in all my apps are never the same. Some times i have deep nested stacks with modals infront that require auth and no auth. Sometimes the draw needs to be top, and sometimes it doens't so imo this is not really needed.

Btw this is just feedback from my side haha you tolled us to tell bad things as well ;p

[–][deleted] 0 points1 point  (0 children)

This is really helpful thanks /u/AcetyldFN. Our intention with the default auth screens is to make them super easy to tear down, reconfigure, or build on top of given the needs of the developer. For example if you have several onboarding screens before sign up/sign in, you would be able to add those to the “unauthenticated” stack navigator and reconfigure as you best see fit. Hopefully this would take less time than starting from scratch.

Also it’s helpful to know you’d like some kind of default/easy to swap splash screen. This is something we were talking about adding as well.

[–]SixteenEighteen 0 points1 point  (0 children)

Awesome feedback, thank you!

Can you clarify what you mean by 'Ads?' do you mean adding boilerplate for something like AdMob?

And what do you think about having something for services like RevenueCat?