React is just the UI piece of the puzzle. Here's a nice description of when to use Redux: "[Redux is justified when] you have a piece of data that needs to be

React is just the UI piece of the puzzle. Here's a nice description of when to use Redux: "[Redux is justified when] you have a piece of data that needs to be used in multiple places in your app, and passing it via props makes your components break the single-responsibility principle (i.e. makes their interface make less sense)" (https://github.com/petehunt/react-howto/issues/12#issuecomment-169546558 https://github.com/petehunt/react-howto/issues/12#issuecomme...) This comment was written for Flux, but it is completely applicable for Redux. When building something non-trivial, there are other pieces you'll want to pull in with React such as routing, messaging, etc.