We all know about “controlled components”, right? The wonderful invention that almost effortlessly keeps our form inputs in sync with our state. It should come as no surprise that the “controlled component” idea extends to whole forms too and covers them quite nicely.

Everyone knows that the rate of which new Javascript frameworks are released is hectic, to say the least. For every deprecation, there’s a bunch new ones to take its place. When someone strikes gold on a new pattern that promises to change the world, there’s 20 new implementations released in a short amount of time. How to make sense of it all?

MobX has been surging in popularity during the last year. It is being used as the state container in apps of all shapes and sizes. Redux vs MobX comparisons are made constantly, with MobX being praised for its simplicity and ease of use. But MobX is very unopinionated about the structure of your app; the only thing MobX does is guarantee that your view stays in sync with your state. So what does it mean to "replace Redux with MobX"? What does using MobX look like in a real app?