riverpod-select

To reduce widget rebuilds in Riverpod, use ref.watch(provider.select(...)) to watch only the specific subset of state your widget needs, triggering rebuilds exclusively when that selected field changes.

Your Flutter widget rebuilds unnecessarily because standard ref.watch(provider) triggers rebuilds whenever any part of the provider's value changes, even if your widget only depends on a single field of a large object.

Yes, you can use selectAsync for async providers when available to watch subsets of state, ensuring that the selected value remains immutable to guarantee correct rebuild behavior.

You should use Riverpod's select when a widget depends on a single field of a large object or when performance is degraded by frequent rebuilds caused by frequent state changes.

A key limitation is that the selected value must be immutable; if the selected subset of state is mutable, Riverpod's select mechanism will fail to correctly detect changes and trigger necessary widget rebuilds.