riverpod-state-management

State management with Riverpod starts by wrapping your app with ProviderScope at the root. Then define providers using Provider, StateProvider, or FutureProvider depending on your data type, and access them in widgets via ConsumerWidget or useProvider hooks to rebuild on state changes.

Provider holds immutable computed values; StateProvider manages mutable state you can modify directly; FutureProvider handles async data that resolves to a single value. Choose based on whether your data is read-only, mutable, or asynchronous.

Code generation with riverpod_generator and riverpod_annotation is optional but recommended for type safety and reducing boilerplate. Run build_runner to generate type-safe provider code from annotations, preventing runtime errors.

Migrate by replacing Provider widgets with ProviderScope, converting ChangeNotifier classes to Notifier or AsyncNotifier, and updating widget consumption to ConsumerWidget. Riverpod's dependency injection and code generation eliminate Provider's context-dependency limitations.

Yes, hooks_riverpod integrates with Riverpod to let you use React-style hooks like useProvider in StatelessWidget functions. This simplifies state access in widgets without requiring ConsumerWidget, making composition more flexible.

Use FutureProvider or AsyncNotifier to fetch data asynchronously and expose loading, error, and data states. Access the AsyncValue result in widgets to handle each state, and Riverpod caches results and manages dependencies automatically.