By ByteBot
Flutter 3.44 landed at Google I/O on May 19 with a full changelog and the usual wave of feature posts. Most of it is incremental. Two things are not. AI coding agents can now auto-hot-reload your running Flutter app through the new Dart and Flutter MCP server — closing a feedback loop that has been broken since agentic tools entered the picture. And Swift Package Manager is now the default for iOS and macOS, which starts the final countdown on CocoaPods.
Agentic Hot Reload: The Feedback Loop Is Finally Closed
If you have been using Cursor, Claude Code, or any other AI coding agent with Flutter, you know the manual tax: agent suggests a UI change, you copy it, paste it, trigger hot reload, look at the result, describe what’s wrong, repeat. The Dart and Flutter MCP server, shipping with Flutter 3.44, eliminates that cycle.
The Dart Tooling Daemon now automatically exposes your running app’s connection details through the MCP server. Your agent discovers the app, makes the code change, triggers hot reload, and sees the live result — zero configuration required. It works with any MCP-compatible agent: Cursor, Claude Code, Google Antigravity, and others.
This is what agentic Flutter development actually looks like. Not a smarter autocomplete — a genuine closed loop where the agent modifies code, observes the outcome, and iterates without you managing the handoff. For teams already running AI coding workflows, this removes the most common manual bottleneck in the Flutter-specific stack.
The full documentation for the Dart and Flutter MCP server is available at docs.flutter.dev/ai/mcp-server.
SwiftPM Is Default. CocoaPods Is Done.
Swift Package Manager is the new default dependency manager for Flutter iOS and macOS apps in 3.44. CocoaPods is now in maintenance mode. The CocoaPods registry becomes permanently read-only on December 2, 2026 — seven months away.
The migration is automatic for most projects. Run flutter upgrade to get 3.44, then run flutter run. The CLI detects the version, migrates your Xcode project to SwiftPM, and downloads the Swift packages your plugins depend on. You lose the Ruby dependency, the pod install step, and the Podfile.lock conflicts. Build times typically improve 10-20%.
The catch is plugin support. If a plugin in your pubspec.yaml has not migrated to SwiftPM yet, Flutter prints a warning and falls back to CocoaPods for that specific dependency. Most major plugins have already made the switch, but you will likely hit at least one warning if your project has a long dependency list. Contact the maintainer, find an alternative, or use the opt-out flag in pubspec.yaml if needed.
If you are a plugin author: the December deadline is real. The SwiftPM migration guide covers what plugin authors need to do. The short version: create a Package.swift in your iOS folder and restructure sources under Sources/<PackageName>/.
Android: Hybrid Composition++ Clears the Platform Views Backlog
If your app embeds native Android views — Google Maps, WebView, ad units — you have dealt with Platform Views jank. The original Hybrid Composition approach copied Flutter frames from GPU memory to main memory and back, per frame. The result was degraded scroll performance and unreliable touch input.
Hybrid Composition++ (HCPP) delegates compositing directly to the Android OS using Vulkan and SurfaceControl. No frame copying. Smooth scrolling, reliable SurfaceView support, and predictable touch input. It requires Android API 34 or later and Vulkan support — devices that don’t qualify fall back automatically to the previous strategy.
HCPP is opt-in in 3.44 via the --enable-hcpp flag. It will become the default in a future release. Worth testing on your Platform Views-heavy screens now.
Dart 3.12: Three Things to Know
Dart 3.12 ships alongside Flutter 3.44 with two stable additions and one preview. Private named parameters let constructors accept named parameters that initialize private fields — the underscore is stripped at the call site, so this._count as a parameter becomes count: for callers. Cleaner without being magical.
Primary constructors are in experimental preview (--enable-experiment=primary-constructors). If you have written Kotlin data classes and then come back to Dart, you know the problem they solve. Expect them in stable form in a future Dart release.
Genkit Dart launches in preview — Google’s framework for building full-stack agentic Dart and Flutter apps. Worth watching if you are building AI-integrated Flutter applications. Read the Dart 3.12 announcement for the full picture.
The Bigger Picture
Flutter reached 1.5 million monthly developers in this cycle — a 50% increase year-over-year — and is now the second most popular mobile SDK on both the App Store and Google Play. The 2026 Toyota RAV4 multimedia system runs Flutter, and LG’s webOS SDK with Flutter support is coming. The embedded target is no longer hypothetical.
The 3.44 release reflects a deliberate push into AI-native development. Agentic Hot Reload, Genkit Dart, and the Dart and Flutter MCP server integration are all part of the same bet: that the next generation of Flutter apps will be built by developers and agents working together, not developers alone. The official Flutter 3.44 blog post covers the full release scope.
For most teams, the immediate action is straightforward: upgrade, run the app, check for SwiftPM warnings, and configure your AI coding agent to use the Dart MCP server. The rest can wait.
