Google shipped Flutter 3.44 alongside Dart 3.12 at Google I/O 2026, and the headline architectural change is what the Flutter team calls the Great Thread Merge: Dart execution moves off its own dedicated UI thread and onto the native platform thread, eliminating the barrier that previously separated Dart code from native iOS and Android code and enabling synchronous FFI calls without the overhead of Flutter's platform channel messaging layer. For teams building Flutter apps that lean heavily on native platform integrations, camera pipelines, ML inference via native SDKs, or any functionality that requires tight, low-latency coordination between Dart and native code, platform channels have historically been both a performance bottleneck and a source of subtle bugs around async message ordering. Removing that barrier by running Dart on the same thread as native code is a meaningfully different architecture, not just an optimization, and it closes a category of "why is my native integration janky" complaints that have followed Flutter since its early releases. The release also brings Hybrid Composition++ improvements for Android and better Vulkan support for the Impeller rendering engine, continuing Flutter's multi-release effort to replace the older Skia-based rendering backend with the more modern, lower-overhead Impeller pipeline. Alongside the runtime changes, Flutter 3.44 formalizes Swift Package Manager as the new default dependency manager for iOS and macOS builds, replacing CocoaPods, whose registry is scheduled to become permanently read-only in December 2026, making this release the point at which Flutter iOS teams still on CocoaPods should treat migration as time-boxed rather than optional.