busic-state-management

Riverpod provider selection depends on module complexity and cross-feature coordination needs. Apply standardized decision rules to evaluate manual Provider versus @riverpod codegen, ensuring consistent architecture and clear Notifier orchestration across your Flutter application.

AutoDispose lifecycle management is needed when coordinating Notifiers that consume temporary resources or require state resetting. Apply enforceable lifecycle patterns to manage provider disposal automatically, preventing memory leaks across feature boundaries in Flutter apps.

Cross-feature Notifier coordination requires clear rules for composing state across layers. Establish centralized state management guidelines that define dependency injection practices and enforce how Notifiers interact, ensuring predictable data flow and reusable patterns.

Refactoring to Riverpod begins by auditing your current Notifier usage. Apply standardized guidelines to refactor existing state management into Riverpod-based patterns, establishing provider choices and dependency injection guidance for consistent module architecture.

Dependency injection works with both manual Provider and @riverpod codegen approaches. Concrete codegen references and dependency-injection guidance ensure consistent architecture, allowing you to compose Notifiers across layers regardless of provider selection.