| I've built the same app in both Redux and MobX. Things I noted: 1) Agree with your #1. It's a pain of boilerplate. 2) Agree, Redux is very easy to reason about and debug. 2) MobX was definitely much faster to develop. 3) MobX performance was better out the box. I may have done something wrong, however I have noted this with the mortgage example. 4) MobX has its own pain points when trying to build more advanced (tree) data structures. Creating a nested observable object requires creating map objects at every step of the tree. This makes using libraries such as lodash difficult. 5) I prefer the redux dev tool 6) Redux containers works well at the top level, however implementing a reusable container requires more boilerplate code. Since there is no consensus library or approach here - I implement my own solution with caution. 7) It is possible to use both redux and mobx on the same app, but you need to know what you're doing. Additionally you seem to lose some of the benefits of redux when you do this. 8) You can communicate between stores, but I feel this is a bad approach and will lead to messy code. In the end I chose to proceed with Redux, however I think MobX implemented with proxy objects would be amazing. I look forward to a framework that sits on the top of React and Redux designed to reduce the boilerplate. Perhaps Vue2 will be what I'm after |