flutter▌

Embed native views and web content into Flutter apps across Android, iOS, macOS, and web platforms. \n \n Supports Android Hybrid Composition (native fidelity) and Texture Layer (Flutter performance), iOS/macOS Hybrid Composition, and web full-page or embedded multi-view modes \n Provides complete Dart and native code templates (Kotlin for Android, Swift for iOS/macOS, JavaScript for web) with factory registration patterns \n Requires decision tree upfront to determine target platform and embedd

Cross-platform native interoperability for Flutter apps on Android, iOS, and Web. \n \n Provides decision logic to select the optimal integration strategy: FFI for C/C++ code, Platform Channels for OS-specific APIs, Platform Views for native UI components, and JS Interop for web \n Implements modern FFI architecture using build hooks (Flutter 3.38+) with native toolchain compilation and Dart bindings \n Supports asynchronous Platform Channels (MethodChannel) with complete Kotlin and Swift implem

MVVM architecture for Flutter apps with unidirectional data flow and strict layer separation. \n \n Implements three-layer architecture: Data Layer (Services and Repositories), Domain Layer (UseCases for complex logic), and UI Layer (ViewModels and Views) \n Uses provider for dependency injection and ListenableBuilder for reactive UI updates with the Command pattern for user interactions \n Enforces unidirectional data flow: data flows down from Repositories to ViewModels to Views; events flow u

Implement MVVM and Unidirectional Data Flow patterns for Flutter state management. \n \n Provides decision logic to differentiate between ephemeral state (local UI state via setState ) and app state (shared state via MVVM and provider package) \n Enforces strict separation of concerns: data layer (Repository as Single Source of Truth), logic layer (ViewModel extending ChangeNotifier ), and UI layer (pure functions of immutable state) \n Includes complete code examples for implementing the MVVM p

Navigate between screens, handle deep linking, and manage data passing in Flutter applications. \n \n Evaluates app requirements to select the optimal routing strategy: imperative Navigator for simple flows, declarative Router / go_router for deep linking and web support, or nested Navigator for independent sub-flows \n Supports data passing between routes via constructor arguments (preferred) or RouteSettings with type-safe argument extraction \n Implements named routes with MaterialApp.routes

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

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

Adaptive Flutter layouts that respond to screen size, platform, and input device across mobile, tablet, desktop, and web. \n \n Three-step workflow: abstract common widgets, measure available space with MediaQuery or LayoutBuilder, and branch UI based on width breakpoints (compact <600, medium 600–840, expanded ≥840) \n Covers layout fundamentals including Flutter's constraint system, common patterns (Row, Column, Expanded, Container), and responsive grid/navigation examples \n Best practic

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