Redux isn't complicated, it is the ecosystem around it which can be overwhelming or partly overengineered. When you get started with React, you should use setS

Redux isn't complicated, it is the ecosystem around it which can be overwhelming or partly overengineered. When you get started with React, you should use setState. You should use it until you get the feeling you really need a state management library to deal with most of the setState implementations. That removes the urge to learn another library next to React in the beginning. Afterwards I agree: MobX is easier at the start, because it can be used similar like setState https://medium.com/@mweststrate/3-reasons-why-i-stopped-using-react-setstate-ab73fc67a42e#.kskio1lqw https://medium.com/@mweststrate/3-reasons-why-i-stopped-usin... But at some point the developer team might decide to use MobX' useStrict to have more explicit actions and more predictable state changes. It removes the feeling of having two-way data binding and after all goes in the direction of the Redux constraints.