I&#x27;m a little confused by what you&#x27;re trying to say, so help me out here. You say &quot;it&#x27;s overly decoupled for simple applications&quot; and then &quot;it is only a tool you should reach for after you find you need it.&quot; This would imply that you view Redux as a tool that primarily helps maintain larger React applications -- does that mean you think it doesn&#x27;t make sense as the defacto standard as compared to, say, Flux? Or that there shouldn&#x27;t be a defacto standard, or that neither of these is a good enough defacto standard?<p>I&#x27;ll take this as an opportune time to link to two very helpful and useful posts about Redux from its author (Dan Abramov) about upsides (<a href="http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;32461229&#x2F;why-use-redux-over-facebook-flux" rel="nofollow">http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;32461229&#x2F;why-use-redux-ov...</a>) and downsides (<a href="http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;32021763&#x2F;what-could-be-the-downsides-of-using-redux-instead-of-flux&#x2F;32916602#32916602" rel="nofollow">http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;32021763&#x2F;what-could-be-th...</a>) of using Redux.<p>Namely, I see Redux offering a nice advantage over flux in encouraging reducer composition (and functional purity) for modularity. &quot;This pattern also enables wonderful features like no-user-code undo&#x2F;redo. Can you imagine plugging Undo&#x2F;Redo into a Flux app being two lines of code? Hardly. With Redux, it is—again, thanks to reducer composition pattern. I need to highlight there&#x27;s nothing new about it—this is the pattern pioneered and described in detail in Elm Architecture which was itself influenced by Flux.&quot;<p>In short, the key value add for Redux, is not necessarily that it&#x27;s (overly&#x2F;inadequately) decoupled, but that it is necessarily forcing a decoupling via functional purity for the &#x2F;purpose&#x2F; of modularity. That is, it is taking a more functional approach to state management for React components, favoring the event log paradigm rather than black box paradigm. This brings with it the ability to be &quot;designed with use cases such as logging, support for Promises, Observables, routing, immutability dev checks, persistence, etc, in mind.&quot; Of course, these aren&#x27;t impossible with Flux, but these things follow intrinsically from Redux.<p>Take my opinion with a grain of salt because I&#x27;m not super experienced with Redux yet, but I really like what I&#x27;ve seen so far playing with it.