Tag: dart

The 2026 way to set an accent color in Flutter with Material 3: ColorScheme.fromSeed, the colorSchemeSeed shorthand, the seven DynamicSchemeVariant options, dark mode, dynamic_color on Android 12+, and harmonizing brand colors. Tested on Flutter 3.27.1 and Dart 3.11.

Call native Android (Kotlin) and iOS (Swift) code from a Flutter 3.x app without writing a plugin: MethodChannel, EventChannel, BasicMessageChannel, the StandardMessageCodec type table, threading rules, and the cases where a plugin still wins.

When async/await is not enough: spawn a Dart isolate to run CPU-bound work off the UI thread. Isolate.run, Flutter's compute, long-lived workers with SendPort/ReceivePort, what can cross the boundary, and the JS/web caveat. Tested on Dart 3.11 and Flutter 3.27.1.

Practical guide to running one Flutter project against multiple SDK versions in CI: a GitHub Actions matrix with subosito/flutter-action v2, FVM 3 .fvmrc as the source of truth, channel pinning, caching, and the gotchas that bite when the matrix grows past three versions.

Fluorite is an open-source 3D game engine that embeds Google Filament rendering inside Flutter widgets and lets you write game logic in Dart.

Droido 1.2.0 landed on Feb 8, 2026 as a debug-only network inspector for Flutter. The interesting part is not the UI. It is the packaging story: keep a modern inspector in debug builds while ensuring release builds remain clean, small, and unaffected.

biometric_signature 10.0.0 adds simplePrompt() and new BiometricError values. Here is how to handle the breaking change and future-proof your Flutter 3.x auth flows.

The leadingDistribution property in Flutter's TextHeightBehavior controls how extra leading is distributed above and below glyphs. Here is when it matters and how to fix text that looks vertically off.

TypeMonkey, a Flutter desktop typing app, shows why desktop projects need clean architecture from day one: sealed states, interface boundaries, and testable logic.

Dart 3.12 dev tags are landing fast. Here is how to read the version string, pin a dev SDK in CI, and triage failures so your Flutter 3.x migration is a small PR instead of a fire drill.