react-native-navigation的迁移库
Guy Carmeli a3b4caf707 Support setting button font family on Android 7 年前
..
_images New Documentation (#819) 7 年前
v2 Fix v2 docs basePath (#1157) 7 年前
.nojekyll New Documentation (#819) 7 年前
README.md Update readme and docs after publishing v1.1.0 (#1092) 7 年前
_navbar.md New Documentation (#819) 7 年前
_sidebar.md Typo Fix (#1134) 7 年前
adding-buttons-to-the-navigator.md Update adding-buttons-to-the-navigator.md 7 年前
android-specific-use-cases.md Update android-specific-use-cases.md (#1678) 7 年前
deep-links.md Update Docs (#1206) 7 年前
index.html Update Docs (#1206) 7 年前
installation-android.md Update installation-android.md 7 年前
installation-ios.md Update Docs (#1206) 7 年前
screen-api.md customize tab badge color (#1932) 7 年前
styling-the-navigator.md Support setting button font family on Android 7 年前
styling-the-tab-bar.md Doc update for tabFontFamily (#2033) 7 年前
sw.js Update Docs (#1206) 7 年前
third-party-libraries-support.md RNN + MobX boilerplate link added (#1178) 7 年前
top-level-api.md Update the document for tabsStyle in Android (#1869) 7 年前
usage.md Update Docs (#1206) 7 年前

README.md


React Native Navigation

App-wide support for 100% native navigation with an easy cross-platform interface.


Important

Latest stable version is 1.1.x and is published to npm under tag latest. It supports react-native 0.43 and above.

We are currently redesigning and rewriting this project under branch v2.
As a result, new features and pull requests on the current stable version will take more time to process.

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.