mobile_flutter

Use a feature-first structure where each feature contains its own data, domain, and presentation layers, with shared code in a core directory. This keeps business logic separated from UI widgets and makes features independently testable.

Define providers like StateNotifierProvider that expose a notifier class holding immutable state, then update state via copyWith methods. Riverpod code generation with the @riverpod annotation simplifies provider creation and dependency injection.

Riverpod is the recommended evolution of Provider, offering compile-time safety, no BuildContext dependency, and better testability. This Skill standardizes on Riverpod with NotifierProvider and code generation.

Use the flutter_secure_storage package, which writes values to platform keychains (Keychain on iOS, Keystore on Android). Call storage.write with a key and value, then read it back with storage.read when authenticating API requests.

Frame drops (jank) usually come from rebuilding large widget trees or doing heavy work on the main isolate. Use ListView.builder for lazy rendering, wrap expensive widgets in RepaintBoundary, and offload parsing to compute isolates.

Use MediaQuery to check screen width or LayoutBuilder to read constraints, then switch between wide and narrow layouts at breakpoints like 600 pixels. This handles tablets and foldables without separate codebases.