Pragmatic State Management in Flutter
summary
Shows how to stop fighting Flutter and lift shared state into a model provided with Provider (examples use ChangeNotifierProvider, MultiProvider and StreamProvider), wiring a slider to a pie chart, disposing resources via the provider dispose hooks, and testing with Flutter driver and profiler. A real app, Developer Request, is built live, measured, and tuned — one setter optimization cuts CPU time by about 12% (statistically significant).
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:38Why State
- 1:59Overview
- 2:30Pragmatic
- 3:27State Management
- 5:15Demo
- 8:23Whats wrong
- 11:53Pragmatic State Management Packages
- 19:58Pragmatic App
- 20:37Company
- 21:21Dispose
- 22:32MultiProvider
- 23:18Listening to Parts
- 26:05Performance Measurement
- 29:24Providers
- 30:42Testing
- 31:52Summary
related talks
44mState Management in Flutter
46mHow to Cook Flutter Properly
22mFlutter State Smackdown: Comparing BLoC, Provider, Riverpod
45mArchitectural Thinking on Flutter State Management- 46mHow to Cook Flutter Correctly
49mReactive Architecture for Flutter
41mCrash-Proof Flutter: Building Apps That Refuse to Die
21mBuild a reactive Flutter App