riverpod-consumers

To read and listen to Riverpod providers in Flutter widgets, use ref.watch inside the build method to react to live provider value changes, and use ref.read for one-time reads inside event handlers to access current state without subscribing.

Use ConsumerWidget for stateless widgets that only read providers to reduce boilerplate. Use ConsumerStatefulWidget when your widget needs local state alongside provider listening, such as for animations or controller-driven UI that requires lifecycle management.

Yes, you can wrap a specific portion of your Flutter UI tree with Consumer. This allows you to access a WidgetRef and call ref.watch on Riverpod providers locally without converting the entire parent widget to a consumer-based base class.

Riverpod prefers ref.watch over context-based provider lookups because it directly wires provider state into the UI, enabling reactive interfaces without prop drilling. Additionally, Riverpod's auto-dispose model prevents memory leaks that context-based lookups might cause.

Select your Riverpod consumer base class based on state needs: ConsumerWidget for simple stateless provider reads, ConsumerStatefulWidget for local state and controller-driven UI, and Consumer for localized WidgetRef access without altering the base class.