Hacker News Reader

Comment by spion | Hacker News Reader

MobX+React would be just like Vue, but with the benefits of the larger React ecosystem and full type checking with typescript/flow, and the drawback of mandatory build tooling.

View on HN

It is similar, but it will mean you get off the highway of React "preferred way" - for example, in case you start working with React Native you might have an issue of using different state management solutions for your web and mobile stack - it looks like nobody is using Mobx with RN in serious projects.

I've used MobX for React Native (though I went back to Redux for familiarity). I found it to be transparent enough.

We're using RN with mobx and it has been great. We'd probably have 3x more code if we went with redux.

Actually we use React+mobx on both our web and RN stacks and it's been great. What we really like is that it is simple and extremely performant since in most cases it automatically updates only the React components that need to be re-rendered based on the state that's been modified.

We jumped directly from a flux-like state management to mobx (skipping Redux) and the development time has gone down significantly as well.

Cool! I think you guys should do a writeup since "react native mobx" results in google clearly state the mind share is not there yet.

Chiming in with another "we use mobx and react native." Sorry for the overload of comments like this but I think it's perfectly fine.

There is no react preferred way of state management. I have used mobx in many of my reactjs native projects.

i've been wondering about that too, and would love to see some write-ups of people that have react+mobx for at least a few months if not more, how it worked out for them, plusses and minuses.

Also tutorials for react+mobx.

Reply on news.ycombinator.com