React Native declarative and reactive navigation.
This repo focuses on grouping screens by business conversion tunnels called canals. Why did I call it react-nonav
? Just because I though of this package when I was visiting Venice... and I kind of hope that using this package will feel like navigating in Venice 📸
When you use React Nonav, you define several screens and you have the possibility to control their visibility with YOUR state machine. You define the rules of WHEN some screens should appear; react-nonav
takes care of the rest.
- you want to group screens by business conversion tunnels rather than transition.
- you want to control your navigation state with YOUR state machine.
- you want your navigation to react to YOUR store changes.
- you want to navigate imperatively.
- you need to use Native navigation (react-nonav's navigation is powered by JS code only).
The docs are here: https://react-nonav.netlify.com/ Powered by the incredible docz.
- Clone this repository.
- Run
yarn
in the root directory. - Run
yarn
in theexample
directory. - Add your code and its test in the
<rootDir>/src
directory. - Add your example code and its test in the
<rootDir>/example
directory. - Open a pull request !
- Clone this repository.
- Run
yarn
in the root directory. - Run
yarn
in theexample
directory. - In the
example
directory, run eitherreact-native run-ios
orreact-native run-android
.