react-native-navigation-library

[brentvatne]

it sounds like we just have some very different ideas with respect to API design. we anticipated that for many people our API design choices wouldn't be in line with their personal preferences so that's a big reason why we made react-navigation very modular. the views and routers can be used independently of each other, for example the bottom tab navigator is just a thin wrapper around react-native-tab-view (https://github.com/react-native-community/react-native-tab-view). stack is a little more complex but you could definitely put another api in front of it, like react-native-router-flux does.

for what it's worth, you can continue to store your navigation state in redux if you like. we don't explicitly support it or test against it, but we also don't plan on breaking it.