State Management in Flutter
summary
A React Native to Flutter rewrite leads to a custom state library replacing Redux+sagas and stream-based BLoCs: code uses atomic async updaters queued so only one updater runs at a time, emits multiple immutable states, and uses immutable union-typed state for compiler-checked UI shapes. Blocks are small, provided via a with-block widget and Provider, HTTP caching prevents duplicate requests, tests await block completion, and an app-restart by key recreates all blocks; clarity and performance improve, with some UI-blocking tradeoffs.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:12Overview
- 4:00Redux
- 5:12Redux Recap
- 6:30Read our Saga Recap
- 9:12Flutter Blocks
- 10:22Streams
- 12:15State Enrichment Library
- 21:12UpdateState
- 24:00Recap
- 25:56Waveform
- 27:53Blocks
- 28:26Combining Blocks
- 28:46State Hierarchy
- 30:42Globus
- 31:45Testing
- 32:48App Restart
related talks
45mArchitectural Thinking on Flutter State Management
33mPragmatic State Management in Flutter
49mReactive Architecture for Flutter
52mState management beyond the libraries
41mThe Battle of State Management in modern frontend applications
19mA humble approach to Flutter app architecture
22mFlutter State Smackdown: Comparing BLoC, Provider, Riverpod
46mHow to Cook Flutter Properly