| I recently gave a talk at Chain React in Portland (first ever React Native only conference) where I compared these two nav stacks: https://www.youtube.com/watch?v=kFyaj5HmMEY&t=1059s The situation with navigation and React Native is a bit of a mess right now. Basically all navigation stacks can be broken down into two categories, those that are native (i.e built on top of the OS's existing navigation stack) and those that are not (pure javascript, emulates what the native stack does). Examples of Native navigation stacks: -> React Native Navigation (wix) -> Native Navigation (Airbnb) Examples of Javascript navigation stacks: -> React Navigation -> React Native Router Flux -> React Router Native An example app I wrote with React Navigation + Redux: https://github.com/hgale/ReactNavigationDemo Same app but built with React Native Navigation + redux: https://github.com/hgale/ReactNativeNavigationDemo The main differences are that the native nav stacks have better performance, stuff like accessibility works right out of the box and they work the same way that the underlying native system works. The main downside to using Native navigation stacks right now is that setting then up & upgrading them can be a real pain. It can also require native knowledge when things go wrong. I would recommend staying with react navigation (Javascript based nav stack) unless you absolutely need some feature from one of these native nav stacks. It's going to be a lot easier to upgrade and you won't run into issues doing over the air updates with your production apps. It's also the one that Facebook promotes in their docs: https://facebook.github.io/react-native/docs/navigation.html Right now both React Native Navigation and React Navigation are under heavy development. No matter which one you choose, budget for some pain in the next year when upgrading. |