To be honest, with all the effort not to stay behind, I had never heard of MobX
I’m still not convinced about redux (or any centralized state management system), when it comes to state that naturally belongs to a single component. Seems like an antipattern to me. I prefer to isolate that state.
My current focus is on rapid prototyping. I save a lot of time when I don’t prematurely split up a component (that is, before I need to reuse its parts). The result are somewhat deep/structured components.
As a result, often only sections of a component will need to maintain certain state, or even load certain data. What one would normally do (at least, what I’ve done for a while) in this cases is to split these sections into new components, and wrap them with a certain composer that maintains the state or loads the data (see the react-komposer, react-komposer-plus or the library that @sashko mentioned).
The point of calling this thread “wrap element with state” and not “wrap component with state” is not having to split a component in the above cases.