flutter-riverpod-architecture

To set up Riverpod 2.x state management with codegen, apply the @riverpod annotation to your providers, declare the required part directives in your file, and run the build step to generate the .g.dart files for consumption.

Using Riverpod code generation is the best way to reduce provider boilerplate, as it automates provider creation via annotations and standardizes state management patterns across your Flutter application.

You consume generated Riverpod providers in widgets via ref.watch for reactive UI updates, and access them in business logic using ref.read to trigger state mutations without rebuilding the widget tree.

Yes, Riverpod codegen supports mutable Notifier-based states alongside simple read-only providers, generating the necessary boilerplate to handle scalable state mutations across your business logic.

Yes, you must include part directives in your Dart file before running the code generation step, ensuring the build process can correctly link and produce the required .g.dart files.