Is this the intended way to use the Navigator API? https://github.com/h87kg/NavigatorDemo/blob/master/index.ios.js
The first thing I'm faced with when I google "react native navigation" is Navigator and NavigatorIOS. Which one should I use? Okay, one wraps UIKit's implementation and one is more cross platform - I choose the more generic Navigator.
Now these docs (https://facebook.github.io/react-native/docs/navigator.html) don't give an example of how to do navigation. I end up doing more googling and find the link at the top of this post. It seems lame to just have a ton of if statements. I suppose it could be done with a map though.
Can we have an awesome, pretty, easy, well-documented API like react-router? :)
@evv: Done. I also made you a rep for React Native so you're able to manage RN posts.
Sweet, happy new year!
I noticed that this thread has been silent for sometime. The 0.31 documentation is still a struggle. is @Andrew Rasmussen way the right way to do it ?
I've moved over to https://github.com/facebook/react-native/tree/master/Libraries/CustomComponents/NavigationExperimental as the Navigation API is too limited. I was under the impression the Navigator component was no longer being maintained?
We're working on this - "we" being @evv and @skevy. The best way to do navigation right now i think is probably ExNavigation, but stay tuned.
Is there any news on this? I am evaluating navigators right now and its hard to since what @evv and @skevy are working on is supposed to deprecate all the built in ones and ex-navigation. I can't find any indication of how this is going or what direction it is going in even though it is marked for release this month on the roadmap.
Looks like we can't incorporate ExNavigation with TypeScript at present - looking forward to whatever next iteration you have planned.
Actually, I also moved to https://github.com/facebook/react-native/tree/master/Libraries/CustomComponents/NavigationExperimental, and I wrote my own components, based on this: http://oramind.com/react-native-navigation/ (shameless self-promotion - I wrote it with whatever information I could gather by taking a look at the code) . There is absolutely nothing I can think of NavigationExperimental can't do.
One complaint of mine is the docs. I would really like to see some documentation on custom animations, custom interpolators, etc. There are some examples on UIExplorer but still...
I wrote a fairly abstract navigation lib that works on all platforms (iOS, Android, and web): https://github.com/tuckerconnelly/react-stack-nav
Supports android back button and deep linking, among other things :)
I created a simple navigator which supports navParams, save history of params & previous states:
I like exnavigation from exponent!
Hi, check out this new library that just shipped (beta): https://reactnavigation.org/blog/2017/1/Introducing-React-Navigation
It builds upon the lessons learned from Navigator, NavigationExperimental, Ex-Navigation. It is meant as a long-term replacement for all of these.
Please try it out and report issues and send pull requests on GitHub:
With the launch of https://github.com/react-community/react-navigation , I'm going to mark this feature request as fixed. While react-navigation isn't perfect, I think we can confidently recommend it over Navigator. There is additional work planned on the React Native roadmap at https://github.com/facebook/react-native/wiki/Roadmap where folks at Airbnb are working on another navigator with a different set of tradeoffs, so if you're interested in the navigation space that is coming down the pipe as well. Thank you for everyone who contributed to this feature request and helped us figure out that we should prioritize work on navigation!
I've started on a new navigation API and am ready for feedback on the code, examples and docs: https://github.com/ericvicenti/navigation-rfc @Andrew Rasmussen, you can mark this as "in progress"!