As of today, React Navigation version 1.0 has been released! To see a list of recent improvements leading up to the release, refer to the “Renewed Path to React Navigation V1.0” issue. Thank you to everybody who has filed high-quality bug reports, submitted pull requests, and helped out fellow developers while we were in beta!

This release isn’t meant to be interpreted as a signal that React Navigation is “finished" — work is already underway on a number of significant changes to the API that aim to make React Navigation easier to use and more powerful. These changes will be run through our new RFC process. For example, the Navigator View API RFC outlines a a plan to decouple views from the router in order to make it easier for other navigation APIs, such as react-native-router-flux and react-router-native, to build on top of the same navigation views. We’re also very excited about a plan (no RFC is open yet, but keep an eye out for it) to use react-native-gesture-handler to run navigation gestures (sliding a drawer open, or swiping back on a stack, for example) on the UI thread using the Animated native driver.

Last week we released an updated version of our documentation website, built using Docusaurus. We hope that the new documentation will help newcomers get onboarded with the fundamentals of React Navigation, and serve as an ongoing resource to handle specific use cases as you come across them (under the “How do I do..?” section). Contributions to the documentation are very welcome.

Give React Navigation 1.0 a try, post a feature request if you think something is missing, open a RFC if you have an idea of how to implement it, file a detailed bug report when you encounter problems (or open a pull request if you know how to fix them)! Updating your existing installation should be easy if you have tracked releases over recent months — read the brief release notes for more information.