| My team is in the process of swapping out the navigation stack in one of our apps (we are going with the one from wix for now). Something you might want to consider is the following (copy pasted from my other comment): "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. |
Would be really interested in this, have been looking at doing exactly the same and am attempting to quantify how much work it would take.