flutter-mobile-patterns

Use Provider for computed immutable values, StateProvider for simple primitives, StateNotifierProvider or NotifierProvider for complex state with business logic, FutureProvider for one-shot async loads, and StreamProvider for live updates like telemetry or FCM events.

Create one dio singleton via a Riverpod Provider with auth, refresh, and logging interceptors, then inject it into repository classes. UI and notifiers must call repository interfaces, never dio directly, keeping the network layer testable and centralized.

This happens when code touches BuildContext or state after an await while the widget was unmounted. Add if (!mounted) return after every await, and dispose Timers, StreamSubscriptions, and controllers in dispose before calling super.

No, background handlers cannot navigate because there is no active widget tree. Store the deep link in shared preferences inside the background handler, then read it and route through GoRouter when the app resumes.

Use minimum 16sp body text, 48dp touch targets (56dp for emergency UI), 4.5:1 contrast ratio, and Semantics labels on all interactive elements. Place primary actions in the bottom 40 percent of the screen for thumb reachability.