You don’t know MobX State Tree
summary
DAZN rewrites its front end for millions of users and chooses MobX with MobX State Tree to manage state, arguing runtime type checks and snapshots enable safe time travel. The talk shows concrete patterns: multiple root stores vs one and when to share the injected environment, why many small observers beat one giant one, how to test by injecting mocks, and a working composition that unifies mobile inertial scrolling and desktop arrow navigation used in production.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:39Agenda
- 1:10MobX vs Mobile State
- 1:32MobX Engine
- 4:23Observable State
- 8:11State Tree
- 9:20Model
- 14:18Tree
- 18:09MobX Store
- 23:47Structure
- 25:17One Root Store
- 27:04Multiple Root Stores
- 29:34Stores Communication
- 30:06Default Approach
- 32:24Action Wrapper
- 33:49Dependency Injection
- 36:55Store Composition
- 38:45Mobile vs Desktop
- 41:10Derivation
- 42:04Summary
related talks
43mYou don’t know MobX State Tree
21mNext-gen React state management with MobX State Tree
32mMobX State Tree React pure reactivity served
25mNext generation state management
41mmobx-state-tree, stop getting into all those states!
34mImmer-mutable state management
21mState Management is Easy
27mReact, But For Data