flutter-state-management

Topics in the source

• Flutter state management
• 1. Pick one (per codebase) and record why
• 2. Load only the reference you need
• 3. Universal async rules (all libraries)
• 4. Review checklist
• Sources

Verified against official docs and pub.dev on 2026-09-25: Flutter 3.47 / Dart 3.13, flutterriverpod 3.4, flutterbloc 9.1 / bloc 9.2, provider 6.1. The rules that matter more than the library: ephemeral (UI) state stays in the widget, shared business state lives outside it; every async operation has explicit loading/data/error; one-off effects are not state. | | Pick when | Cost | |---|---|---| | Riverpod 3 (most downloaded: 3.3M/30d) | You want DI + state + caching in one tool; async-heavy data; compile-safe dependencies; less boilerplate | Flexible, so the team must enforce boundaries or the provider graph sprawls | | Bloc / Cubit 9 (2M/30d) | Large teams, strict and traceable state transitions, event transformations (debounce, droppable), regulated or long-lived apps | More boilerplate | | ChangeNotifier MVVM + provider (Flutter's official architecture guide) | You want to follow docs.flutter.dev exactly, fewest dependencies, a team new to Flutter | You hand-write Commands/Result; less tooling | | setState, ValueNotifier + ValueListenableBuilder, ListenableBuilder, flutterhooks | Ephemeral state: selected tab, form input, animation, text controllers, expanded/collapsed | Doesn't

This is an excerpt. Refer to the complete source and its current requirements.