|
|
|
|
|
by nomnombunty
3384 days ago
|
|
We are currently planning on switching from Navigator (https://facebook.github.io/react-native/docs/navigator.html) to React Navigation (https://reactnavigation.org/docs/intro/). After seeing Airbnb's React Native Navigation library, I am not sure what to choose any more. React Navigation seems to be the framework that is endorsed by the react native team. However, Airbnb's React Native Navigation library seems to be more proven since they had been using it in production. I am wondering if anyone know what are the benefits of using React Native Navigation vs React Navigation |
|
"The problem with all the JS based navigation stacks for React Native (react-native-router-flux, react-router, React Navigation) that I have tried is that if you need to have a back stack, they keep the previous scene in memory. i.e if you look at the 3D view hierarchy in XCode you will see the screen prior to the one you pushed."
The docs for airbnb's new navigation stack says the following:
http://airbnb.io/native-navigation/
"React Native Navigation by Wix engineering is an alternative library that uses "Native" navigation components of each platform, and has been around longer than Native Navigation. If you need a stable / production-ready navigation library today that uses native platform based navigation components, we recommend you check this library out."
They also claim they are not using this library in their main app yet.
I'll be writing up a blog post about my experiences with the wix nav stack migration once we get our app out.
It's a shame the situation around navigation stacks with React Native is so confusing right now.