Introduction
RNTester is the easiest way to demostrate what React Native can do. It has been that for a long time, but for a while now it hasn’t received much love. It has been in a kind of maintenance mode. It’s time to make RNTester shine!
Tasks
Ideas for discussion
Extract to a separate repo?
Would that make is easier to handle/upgrade?
- Make sure it always is up to date with latest master?
Is it useful to have RNTester up to date with master, so new development there can use RNTester as a testbed and showcase of new functionality/features/UI?
- Use react-native-navigation or react-navigation?
Fight!
Appendix
Inspiration issue
@cpojer
Introduction
RNTester is the easiest way to demostrate what React Native can do. It has been that for a long time, but for a while now it hasn’t received much love. It has been in a kind of maintenance mode. It’s time to make RNTester shine!
Tasks
This is just the base of everything.
We can use RNTester as a testbed of the upgrading process. It is also important for people to be able to clone the react-native repo and compile and run RNTester using the latest release.
I guess this is self-explanatory. React Native does not provide navigation, so this will make a great example of one, and at the same time we can simplify the current navigation in RNTester.
The
RNTesterListfiles can probably be simplified, maybe we can put the key in the actual example. Ideally this list file would be one line per example, not 4-5 like now.This will be a good way to show off any new features/UI, and make it easy for someone to just see the app in action, without needing to setup and compile themselves.
Ideas for discussion
Extract to a separate repo?Would that make is easier to handle/upgrade?Is it useful to have RNTester up to date with master, so new development there can use RNTester as a testbed and showcase of new functionality/features/UI?
Fight!
Appendix
Inspiration issue
@cpojer