Add support for React-Native-Navigation
closed
Javid Jamae
At the moment, react-navigation is the primary / recommended choice for navigation, but it is fraught with issues including performance, lack of idempotent pushes, lack of commitment from contributors, etc.
React-Native-Navigation is backed by Wix, should generally have better performance, and has clear and simple documentation.
It would be great to have a choice in navigation libraries and RNN seems like the best alternative option.
Ardi Bello
Supporting this ticket as well. React Native Navigation is much more performant and has great documentation. Expo should support this library so that ejection is not needed. Until then, a lot of us are forced to eject.
Mark McFarlane
Absolutely agree on this. We use RNN in all of our projects, and this is stopping us from using Expo.
BTW if anyone's interested (and also feedback appreciated!), I wrote an article about the differences between the two libraries at https://www.tacchistudios.com/blog/2019/11/14/navigation-in-react-native/.
Harry Billinis
Any plans to add support?
Jose
Definitely a mess to use expo with react-native-navigation. Are there any plans to improve this?
Sam Holmes
Jose: or at least some discussion about the prohibitive factors would be amazing
Brent Vatne
Jose: you can use it with the 'bare workflow' - https://docs.expo.io/versions/v33.0.0/bare/hello-world/
see this note for how to configure it for rnn: https://github.com/unimodules/react-native-unimodules#configure-ios
Sam Holmes
There are still many things that react-native-navigation offers over react-navigation.
Is implementing support for this a prohibitively technical issue?
Petr Peller
Sam Holmes: I wonder the same. react-navigation is really not suitable for a big production app. It's really great and easy for very simple MVPs, but really struggles scaling up (mostly because of the declarative API that forces you to nest Navigators to insanity).
Would be great to have the possibility to choose between react-navigation and react-native-navigation without ejecting.
Jesper Madsen
react navigation 3 might negate the need for react native navigation due to it's incoorporation of Screens - check out the release notes (https://reactnavigation.org/blog/2018/11/17/react-navigation-3.0.html), the repo (https://github.com/kmagiera/react-native-screens) and this talk from React Native EU 2018 by the author:
Neal Morris
Please reopen, having a ton of issues with the react-navigation. (V2)
P
Pedro
Can we reopen this? It's the end of 2018 and react-navigation is still terribly slow. And v2 is out.
Brent Vatne
closed
we're not planning on doing this any time soon. when react-native-navigation v2 is released we may be interested in re-assessing it. the comments about react-navigation in the initial post no longer apply. react-navigation still needs a lot of work but it's made a bunch of progress and we have some significant improvements coming for it soon
S
Sourcebit Apps
I read all the comments here, and i strongly feel react-native-navigation should be supported provided react-navigation is having so many issues. I just started my app development and facing this issue to not able to use react-native-navigation with expo, as a result im moving out of expo.
Load More
→