A small demonstration app showing how to use Redux to manage navigation state in a React Native (>0.21) application using NavigationExperimental
JavaScript Objective-C Python Java
Clone or download
Latest commit 28bc4a9 Sep 24, 2016



A small demonstration app showing how to use Redux to manage navigation state in a React Native (>0.21) application using NavigationExperimental.

Screencast of flipping through a few different screes

The key elements to note when trying to implement NavigationExperimental with Redux include the following:

  • <NavigationTransitioner> is the base component upon which you can build many different navigation paradigms. It requires that you pass it, at minimum, the current state of the navigation (navigationState) and a method to render contents to the screen (render).
  • Your navigation state as Redux will handle it must conform to the NavigationState type defined for NavigationExperimental, which is as simple as this:
	index: [number representing currently displayed screen],
	routes: [
		// Array of NavigationRoute objects, which must contain at minimum a `key` property:
		{ key: 'MyScreen', title: 'A Title is Optional', [...other props here for your own use] }
  • This implementation uses NavigationStateUtils to do the dirty work when reducing state (see reducers.js)
  • You can skip your own implementation of the reducers and use React Native's versions. See this comment and the pure-rn-reducers branch.

Finally, this was just an attempt to figure out how to connect Redux and NavigationExperimental, and does not represent an ideal implementation. If you see room for improvement, please let me know.

Two approaches for dealing with card-based apps

Starting with v0.29, I've included two different main components that demonstrate approximately the same functionality in two different ways. The first is <AppContainer>, which implements a <NavigationTransitioner> in a barebones example, and the second is <AppContainerWithCardStack>, which does the same but uses a <NavigationCardStack> component to do some things for free.

Switch between the two approaches by editing app.js. You'll note the following:

  • The approach using NavigationTransitioner loses out on some nice functionality like maintaining the current scene when pushing and animating a new scene into place. The approach using the CardStack does not have this issue.
  • The CardStack example loses out on some of the modal functionality, such as disabling the back gesture responder, and "closing" the modal results in a horizontal transition instead of a vertical. These things cannot be overriden due to how the CardStack component is currently written.

Again just as a reminder, this little sample repo is not meant to be a starting point for your own apps, just a handy reference! :) Because of this, I've included both approaches. With the <AppContainer> you can build a large variety of navigation structures, but you just might need to write a little more code. With the <AppContainerWithCardStack> you can see how to very quickly bootstrap out a typical navigation flow, but might run into issues when you want to override something. Good luck!

A note about branches

At this time, NavigationExperimental is moving quite quickly and the API is still a bit of a moving target. Master branch will attempt to follow the current stable release (this is a change from previous) since things are starting to quiet down. For version-specific implementations older than the current stable release, I'm creating a branch per RN version. For example, see the 0.23 branch of this repo to see how to implement against the NavigationExperimental API in RN 0.23.

In the future, when NavigationExperimental is changing little between versions, we'll switch to a tag-based approach instead of branches.