Guy Carmeli
fcc4d99bad
Update docs after adding support for custom left button on Android (#1014)
|
7 jaren geleden | |
|---|---|---|
| .. | ||
| _images | 7 jaren geleden | |
| .nojekyll | 7 jaren geleden | |
| README.md | 7 jaren geleden | |
| _navbar.md | 7 jaren geleden | |
| _sidebar.md | 7 jaren geleden | |
| adding-buttons-to-the-navigator.md | 7 jaren geleden | |
| android-specific-use-cases.md | 7 jaren geleden | |
| deep-links.md | 7 jaren geleden | |
| index.html | 7 jaren geleden | |
| installation-android.md | 7 jaren geleden | |
| installation-ios.md | 7 jaren geleden | |
| screen-api.md | 7 jaren geleden | |
| styling-the-navigator.md | 7 jaren geleden | |
| styling-the-tab-bar.md | 7 jaren geleden | |
| third-party-libraries-support.md | 7 jaren geleden | |
| top-level-api.md | 7 jaren geleden | |
| usage.md | 7 jaren geleden | |
README.md
React Native Navigation
App-wide support for 100% native navigation with an easy cross-platform interface.
Important
We are currently working hard on redesigning and refactoring this project with high quality and robustness in mind. As a result, issues and pull requests will take more time to process.
To avoid any confusion and breaking existing projects, all continuous development is published under the npm tag
next, with version2.0.0-experimental.x. Once stable, we will publish it as2.0.0. This version supports react-native0.40.0 and above.The last stable version is
1.30.xwith npm taglatest. This version supports react-native0.25.1. It’s installation instructions are here.
Why use this package
One of the major things missing from React Native core is fully featured native navigation. Navigation includes the entire skeleton of your app with critical components like nav bars, tab bars and side menu drawers.
If you’re trying to deliver a user experience that’s on par with the best native apps out there, you simply can’t compromise on JS-based components trying to fake the real thing.
For example, this package replaces the native NavigatorIOS that has been abandoned in favor of JS-based solutions that are easier to maintain. For more details see in-depth discussion here.