With Flutter 3.44, released as part of Google I/O in late May 2026, the Flutter team has addressed two long-standing structural issues at once: the tight coupling of the design libraries to the SDK release cycle, as well as the long-standing performance trade-off associated with embedding native Android views. Neither of these decisions is merely a cosmetic improvement; rather, they set the course for the Flutter platform architecture in the coming years.
The most significant change is the decoupling of the Material and Cupertino libraries from the core framework. These libraries have been frozen with this release: Flutter 3.44 contains the final version before Material and Cupertino appear on pub.dev as standalone packages, `material_ui` and `cupertino_ui`. Starting with the next stable release, the previous versions will be deprecated within the framework itself. What may sound like a restructuring effort at first glance is, in reality, the solution to a fundamental architectural problem. As Flutter has grown from a mobile UI toolkit into a multiplatform environment for the web, Windows, macOS, Linux, and embedded systems, this tight coupling has become a hindrance: Core widgets are tied to specific design systems, which makes it difficult to create fully custom UIs and prevents the independent further development of these design libraries.
The practical impact on project teams is immediate: Until now, every Material 3 customization and every Cupertino bug fix had to wait for the next quarterly release. With the standalone packages, the design team now has its own release cadence. A `material_ui: ^1.0.0` in the `pubspec.yaml` delivers Material updates as soon as they land on pub.dev, decoupled from the Dart SDK version in your own CI pipeline. For teams that run projects on a frozen Flutter version across multiple quarters—which is common in enterprise environments—this means that design system changes can be managed independently of framework upgrades. Another effect relates to binary size: After the full transition, apps that use only Cupertino will no longer include Material’s theming, typography, and icon set in the bundle.
Justin McCandless precisely describes the starting point of the process: “We’ve been hard at work preparing to decouple Material and Cupertino from the framework, and now our first major milestone has arrived! As of April 7, all contributions to the Material and Cupertino libraries in flutter/flutter are frozen.” (blog.flutter.dev, April 2026) The migration has been deliberately designed to be seamless: The existing import `package:flutter/material.dart` still works in 3.44, but generates a deprecation warning. The actual switch to `package:material_ui/material_ui.dart` is a mechanical process and can be performed using `dart-fix`.
At the same time, Flutter 3.44 uses Hybrid Composition++ (HCPP) to resolve a technical issue that has regularly forced compromises in production projects involving maps, WebViews, or video players. The previous model offered two inadequate options: Virtual Display with input latency and SurfaceView limitations, or classic Hybrid Composition with performance losses due to additional GPU compositing passes. HCPP delegates layer compositing directly to the Android operating system, leveraging Vulkan’s low-level access via hardware buffer swapchains and SurfaceControl transactions to synchronize the Flutter UI with native Android views. The result: high-performance scrolling and precise touch input, as well as reliable SurfaceView support that older modes could not provide. Touch events are now correctly routed for both Flutter widgets and embedded native views—a long-standing source of hit-testing bugs.
HCPP is opt-in in 3.44. It can be enabled using the `--enable-hcpp` flag or via a manifest entry. This is the right decision: Teams that make heavy use of Platform Views—such as in fintech apps with embedded camera flows or navigation apps with Google Maps integration—should test HCPP on real devices now, before the mode becomes the default in an upcoming release.
For Portalworks projects, this results in a concrete need for action on two levels. First: Existing codebases that import `package:flutter/material.dart` or `package:flutter/cupertino.dart` will generate deprecation warnings starting with the next stable release. The previous architecture forced unexpected UI-breaking changes during SDK upgrades due to transitions from Material 2 to Material 3 and tied design improvements to the quarterly release schedule. Migrating to `material_ui` and `cupertino_ui` early on prevents this technical debt from accumulating. Second: Projects with native Android embeds should evaluate HCPP during a dedicated testing phase. Production teams should test the feature on real devices, especially if the app relies heavily on WebView, Maps, Ads, or Video.
Flutter 3.44 balances significant architectural shifts with a clear focus on quality: The strategic decoupling of the Material and Cupertino libraries runs parallel to extensive web rendering improvements and deeper platform integration. This is not a short-term feature drop, but rather the culmination of several years of restructuring work—and the beginning of a more flexible, modular Flutter architecture that is significantly better suited for long-term enterprise projects than the previous monolithic SDK model.
