flutter▌

Architectural guidance for scalable Flutter apps using MVVM, layered design, and feature-first organization. \n \n Supports two project structures: feature-first (recommended for teams and medium-to-large apps) and layer-first (for smaller apps or solo developers) \n Defines three core layers: UI (Views and ViewModels), Data (Repositories and Services), and optional Domain (Use-cases) \n Covers key design patterns including Command Pattern, Result Type for error handling, Repository Pattern, and

Build responsive Flutter layouts by composing widgets, managing constraints, and adapting to screen sizes. \n \n Provides a decision tree for selecting the right base layout widget (Row, Column, Stack, ListView, GridView, CustomScrollView) based on content dimensionality, overlap, scrolling, and responsiveness needs \n Enforces Flutter's core constraint system: constraints flow down, sizes flow up, parents set position; includes ConstrainedBox patterns for forcing specific dimensions \n Implemen

Manage ephemeral and app-level state in Flutter using StatefulWidget, MVVM, and Provider. \n \n Distinguishes between ephemeral state (single widget, managed with setState() ) and app state (shared across widgets, managed with MVVM and provider package) \n Implements unidirectional data flow with a single source of truth: Models handle data, ViewModels manage UI state via ChangeNotifier , Views consume and display state \n Provides sequential workflow for MVVM implementation: define Repository,

SQLite and offline-first data layer architecture for Flutter apps with structured local persistence. \n \n Separates data layer into stateless Services (raw data wrappers) and business-logic Repositories (single source of truth per domain entity) \n Implements offline-first synchronization: reads yield cached local data immediately then fetch remote updates; writes save locally first, then attempt API sync with background queue fallback \n Covers SQLite setup with safe parameterized queries, Dom

Measure and optimize Flutter app bundle size across platforms with analysis tools and reduction strategies. \n \n Generates detailed size analysis JSON files via --analyze-size flag to identify large packages, libraries, and assets contributing to bloat \n Visualize and compare builds using DevTools app size tool with treemap inspection and diff functionality to track optimization progress \n Supports Android (APK/AAB), iOS, and desktop platforms with platform-specific workflows, including iOS a

$22

Automates Linux environment setup for Flutter desktop development with dependency installation and validation workflows. \n \n Covers three core workflows: installing system dependencies (build tools, GTK libraries, C/C++ toolchain), validating the environment with flutter doctor , and preparing Snap packages for distribution \n Provides ready-to-run commands for Debian/Ubuntu systems and includes conditional setup for ChromeOS Linux containers \n Includes a baseline snapcraft.yaml template for

Automated Windows environment setup for Flutter development with SDK, tooling, and platform configuration. \n \n Guides SDK installation, PATH configuration, and dependency validation via flutter doctor \n Covers Visual Studio C++ workload setup for Windows desktop compilation and Android emulator/device configuration \n Includes workflows for building release binaries, packaging distributable archives with required DLLs, and generating self-signed certificates for MSIX deployment \n Provides st

Validated Flutter forms with field-level error handling and submission workflows. \n \n Requires StatefulWidget hosting with a persistent GlobalKey<FormState> to manage form state and validation across rebuilds \n Use TextFormField widgets with validator() callbacks that return error strings on failure or null on success \n Call _formKey.currentState!.validate() on submit to trigger all validators and automatically display error messages below fields \n Includes complete code example demons

Imperative and declarative routing patterns for Flutter screen transitions and deep linking. \n \n Covers both Navigator (imperative, stack-based) and Router (declarative, URL-synchronized) approaches with guidance on when to use each \n Supports deep linking on iOS, Android, and Web; includes data passing via constructors, route arguments, and return values \n Implements nested navigation for multi-step flows (e.g., setup wizards) with independent sub-navigators and back-button interception \n