flutter▌

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

Select and implement the optimal Flutter animation strategy for your UI requirement. \n \n Includes a decision tree to choose between implicit animations, explicit tweens, physics-based motion, hero transitions, staggered sequences, and page route transitions \n Provides complete code examples for each animation type, from simple AnimatedContainer to complex staggered multi-tween setups \n Enforces strict memory management with mandatory AnimationController disposal and performance best practice

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

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

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

Visual feedback, transitions, and physics-based motion for Flutter apps using the Animation framework. \n \n Four animation strategies: implicit animations for simple property changes, explicit animations with playback control, Hero transitions for shared elements between routes, and physics-based animations for gesture-driven natural motion \n Core typed Animation system with AnimationController , Tween , and Curve classes; always dispose controllers to prevent memory leaks \n Staggered animati

$22