consider https://github.com/wix/react-native-navigation as well, I am using it without any problems.

You can use higher order components, wrap your root component with a HOC and in that HOC's render method, If there is an error, instead of returning the wrapped component return something else gives information about the error. If you use the higher order components you do not need to change the existing component, just wrap it by some HOC. For reference my favorite article about HOCs https://medium.com/@franleplant/react-higher-order-components-in-depth-cf9032ee6c3e#.ae9ungvk0 const errorWrapperHOC = function (wrappedComponent) { return class ErrorHoccedComp extends Component { render() { const { error } = this.props; // pass it here somehow. if (!error) { return <WrappedComponent {...this.props}/> } if (error == '404' ) { return <h1> 404 </h1> } if (error == '500' ) { return <h1> 500 </h1> } return <h1>unknown error happened.</h1> } } }

I think the url scheme you suggested makes sense and react-router already have support for parameterized paths, that even makes your job easier. I would use the route scheme you have suggested. One of the examples: https://github.com/ReactTraining/react-router/tree/master/examples/dynamic-segments .