Jamon Holmgren

Holmgren traces his team’s path from Flux to Redux, which they used on React Native projects starting in 2015. He cites Redux’s learning curve, boilerplate, side-effect handling, and inconsistent team patterns as reasons they explored other options.

Holmgren describes MobX, MobX-React, and MobX-State-Tree as a connected state-management setup. Models define typed data, actions control changes, and asynchronous flows can use MST’s `flow`. Components wrapped in `observer` rerender when the properties they read change.

Holmgren recommends hooks for local component state and React context to access MobX-State-Tree stores. For navigation, he describes keeping screen parameters in a navigation store and using React Navigation’s hooks. He also explains how MST can manage asynchronous permission flows.

Holmgren recommends the Ignite Bowser boilerplate, which includes MobX-State-Tree, MobX-React, and React Navigation. He introduces React NavX as an experimental library intended to connect these tools, provide persistence, and remove about 500 lines of glue code. He says the patterns are more established than the new library, which was still broken at the time.