flutter▌

Navigate Flutter apps across mobile and web with Navigator API or go_router, including deep linking and browser history. \n \n Choose Navigator API for simple apps without deep linking; use go_router for production apps requiring deep links, browser history support, and URL-based navigation across platforms \n Pass data between screens via constructor arguments (Navigator) or URL query parameters (go_router); return data using Future-based pop with typed results \n Configure deep linking through

Flutter development with Riverpod state management, Freezed immutable models, go_router navigation, and mocktail testing. \n \n Riverpod provider ecosystem covers simple values, mutable state, async operations, streams, and parameterized data with family modifiers; AsyncValue pattern handles loading, error, and data states uniformly \n Freezed generates immutable data classes and union types for sealed state modeling; integrates with JSON serialization via json_serializable \n go_router provides

Expert guidance for Flutter 3.x+ development across mobile, web, desktop, and embedded platforms. \n \n Covers Flutter 3.x architecture, Dart 3.x advanced features, and Impeller rendering engine optimization with performance profiling across all target platforms \n Specializes in state management solutions (Riverpod, Bloc, GetX, Provider) and clean architecture patterns with modular code organization \n Provides platform integration expertise for iOS, Android, web, and desktop with native plugin

Comprehensive guide for using drift database library in Flutter applications.

Linux environment setup for Flutter desktop development with OS detection and toolchain validation. \n \n Automatically detects Debian/Ubuntu or ChromeOS and halts with instructions for non-apt systems \n Installs core dependencies (curl, git, unzip, libglu1-mesa) and Linux desktop toolchain (clang, cmake, ninja-build, GTK libraries) \n Prompts for optional IDE setup (VS Code or Android Studio via snap) \n Runs flutter doctor -v and flutter devices to validate the environment, automatically inst

Automated Windows Flutter development environment setup with platform-specific toolchain configuration. \n \n Configures Flutter SDK paths, Visual Studio C++ toolchain installation, and platform-specific settings via interactive prompts for Windows Desktop, Android, or both targets \n Handles Android Studio setup, device/emulator configuration, and USB driver installation when Android is selected \n Generates self-signed MSIX certificates using OpenSSL for local Windows app packaging and deploym

Duit enables backend-driven UI in Flutter applications. The server controls both data and layout via JSON, allowing UI updates without app releases.

Scaffolds Flutter plugins with native interop, method channels, FFI integration, and federated architectures. \n \n Generates standard plugins, FFI plugins, or federated multi-package architectures based on native code requirements and team structure \n Configures Android v2 embedding lifecycle interfaces, platform-specific native environments (Kotlin/Java, Swift/Objective-C), and method channel registration \n Implements package-separated federated plugins with app-facing and platform-specific

Secure HTTP networking and JSON handling for Flutter apps with background parsing support. \n \n Implements CRUD operations (GET, POST, PUT, DELETE) using the http package with safe URL construction via Uri.https() and strict status code validation \n Provides strongly typed JSON serialization and deserialization using Dart 3 pattern matching with factory constructors and toJson() methods \n Offloads large JSON parsing to background isolates via compute() to prevent UI jank on payloads exceeding

Background JSON parsing and state management for jank-free Flutter UI rendering. \n \n Provides decision tree for choosing between manual serialization ( dart:convert ) and code generation ( json_serializable ) based on model complexity \n Supports three concurrency strategies: main-thread async/await for small payloads, short-lived Isolate.run() for heavy one-off computations, and long-lived isolates with ReceivePort / SendPort for continuous two-way communication \n Includes platform-aware fal