mobile-flutter-state-management

For shared cross-screen state in Flutter, Riverpod is recommended for predictable and scalable architecture, while Bloc is suited for complex event-driven flows. The Skill provides a decision matrix to choose between setState, Riverpod, and Bloc based on your app's needs.

To handle asynchronous API data with Riverpod, use AsyncNotifier patterns. This Skill provides integration steps for AsyncNotifier to manage API-backed state, ensuring data fetches are persisted and UI updates automatically when the async state changes.

Choose Riverpod for shared and async state, Bloc for complex event-driven architectures, and setState for simple widget-local state. This Skill offers a decision matrix mapping each approach to specific use cases, including migration notes for Provider-based codebases.

Set up riverpod_generator and build_runner by installing the dependencies and running code generation commands to create provider boilerplate. This Skill outlines the installation, integration patterns, and code generation steps needed to streamline Riverpod usage.

Using ref.read inside a build method instead of ref.watch is a common mistake that prevents UI updates. This Skill covers testing best practices and pitfalls like missing ProviderScope, mutable states, and incorrect ref usage to ensure predictable state.