Could someone comment about how this compares with other projects like:
https://github.com/react-community/react-navigation
and https://github.com/facebook/react-native/blob/master/docs/Us... ?
Awesome docs, BTW!
Awesome docs, BTW!
React Router v4 is building a react-native integration to show that it is capable of working on Native. It's centered around URLs so it's attempting to make Deep Linking into your application easier, as well potentially re-using the same navigation on the web.
That being said react-navigation can do both of those things as well and is fully supported by react-native core contributors.
1) In RR, nav state is the URI. Because mobile nav state is complex, React Navigation treats URIs as actions to modify a more complex navigation state
2) RR uses React Components for navigation logic. In React Navigation, the isolated nav logic is statically available, (without rendering).
3) React Navigation is composable, so navigators can be configured to delegate navigation logic to child routers.
2) In React Router you can have a statically available route config. This is React. Make an array then map it to render.
3) React Router is all components, so it composes exactly like the rest of your app. No new API to learn. It's Just React™
For example: your app may have a stack of modal screens, and each of those screens may have tabs or a stack, and there may be another tab or stack navigation within each of those. In React Navigation, each node can be a router that manages its own navigation state.