riverpod-select

You can prevent unnecessary Flutter widget rebuilds by using Riverpod's `select` filter to watch only specific subsets of a provider's state. This ensures widgets only rebuild when the exact fields they consume actually change.

The best way to watch a single property of a large state object in Riverpod is using `ref.watch(provider.select(...))`. This selectively subscribes your widget to a specific subset of the provider state, minimizing rebuilds when other fields update.

You should use select for Riverpod state management in performance-critical applications with complex state objects. It is specifically needed when a widget consumes only a small portion of a larger state object and you want to avoid rebuilding when unrelated fields change.

Yes, Riverpod select requires adherence to immutability principles for selected values. Maintaining immutable state objects ensures that changes to the watched subsets are correctly detected, which is necessary to trigger accurate widget rebuilds.

Your Flutter widget may still rebuild if immutability principles are not followed for the selected values. If the watched subset of the provider state is not properly immutable, Riverpod cannot detect that the specific field remained unchanged, triggering unnecessary rebuilds.