Application state management
summary
Explains why MobX replaces handwritten plumbing for app state and how it actually behaves when integrated into a React Native app: uses @observable/@action/@computed/observer decorators to wrap state, batches mutations as transactions so UI updates once, caches computed values, and logs actions for debugging. Describes an architecture of component → container → service → store → viewmodel, offline data flow, and pitfalls: older MobX versions treat arrays oddly, v5 moves to ES6 proxies, and improper use of observables causes keyboard/reactivity glitches.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:02What is state management
- 3:49When to use state management
- 4:34State management approaches
- 6:41Observer pattern in state management
- 8:27MobX library overview
- 10:57Using MobX in React example
- 16:52Data flow architecture approach
- 23:35Summary and benefits
- 24:38Q&A
related talks
14mState management without pain
09mMobX - Performance and Sanity
41mThe Battle of State Management in modern frontend applications
41mMobX, or: Going from Mutable to Immutable to Reactive State Management
48mGoing big with MobX
27mReact, But For Data
18mState Management — One Meta-Model to Rule Them All
25mMobX vs Redux: Comparing the Opposing Paradigms