Flutter 3.44 Hybrid Composition++ (HCPP) Delivers High-Performance Native Android Views

Among the many improvements packed into Flutter 3.44 — the major release that debuted at Google I/O 2026 — one feature stands out for the fundamental architectural change it represents: Hybrid Composition++ (HCPP). This experimental new hybrid composition strategy for Android platform views leverages Vulkan and the Android SurfaceControl API to solve one of Flutter's longest-standing performance pain points: embedding native Android views inside a Flutter application without visual jank or frame drops.

The Platform View Problem

Platform views are Flutter's mechanism for embedding native Android or iOS UI components inside a Flutter widget tree. They are essential for integrating components like Google Maps, WebView, camera previews, and native advertising SDKs that are distributed as Android SDKs rather than Flutter packages. Historically, embedding these views has involved a performance trade-off: the view hierarchy must bridge between Flutter's rendering engine (Impeller or Skia) and the Android view system, and that bridge has been a source of dropped frames and visual artifacts.

Flutter previously offered two strategies for Android platform views: the virtual display strategy, which rendered native views into an offscreen buffer and composited them into the Flutter scene, and the original hybrid composition approach, which overlaid native views on top of the Flutter surface. Both approaches had drawbacks. Virtual displays suffered from touch event issues and input latency, while hybrid composition could introduce flickering during scrolling and animation because the native views and the Flutter content were composited separately by different system components.

How HCPP Changes the Equation

Hybrid Composition++ approaches the problem from a fundamentally different angle. Instead of compositing native views as separate layers over the Flutter surface, HCPP delegates the entire compositing responsibility to the Android operating system through the SurfaceControl API, backed by Vulkan graphics operations. This means all content — both Flutter-rendered widgets and native Android views — passes through a single compositing pipeline, eliminating the synchronization issues that caused stutter in the previous approaches.

The key technical innovation in HCPP is the use of Android's SurfaceControl API with Vulkan interop. SurfaceControl, introduced in Android 10 and refined in subsequent releases, allows applications to manage surfaces as first-class compositing objects. By surfacing native views as SurfaceControl nodes within Vulkan's command buffer, HCPP ensures that the GPU sees a unified scene graph. The result is platform view rendering that matches the performance of fully native applications, even during complex animations, scrolling lists, and transitions.

The feature is available as an opt-in experimental option in Flutter 3.44 and later, including the 3.44.8 hotfix release. Developers enable it by passing a specific flag in the Android manifest or through the Flutter engine configuration API. The Flutter documentation provides detailed guidance on the configuration steps and compatibility requirements:

• Device Requirements — HCPP requires Android 10 (API 29) or higher and a Vulkan-capable GPU. Devices running older Android versions or using software rendering fall back to the previous hybrid composition strategy automatically
• Opt-In Configuration — Developers must explicitly enable HCPP in their AndroidManifest.xml or through Flutter's engine initialization API. The feature is classified as experimental, and the APIs may change in future releases
• Compatibility Notes — HCPP is compatible with Impeller but not with the legacy Skia backend (which is being phased out on Android 10 and above). Applications still using Skia on modern Android devices will use the previous hybrid composition strategy
• Expected Improvements — Early benchmarks shared by the Flutter team show a 40 to 60 percent reduction in frame drop rates for applications using platform views during scroll and animation scenarios. Touch latency is also improved because input events no longer need to traverse the virtual display buffer

Practical Implications for Flutter Developers

For most Flutter developers, the immediate benefit of HCPP is invisible but tangible: applications that use Google Maps, WebView, camera previews, or native ad SDKs will simply feel smoother when running on supported hardware. The feature is particularly impactful for developers building map-heavy applications like ride-sharing, delivery logistics, and real estate platforms, where a janky map experience can directly affect user satisfaction and retention.

The HCPP feature also removes a barrier for enterprise teams evaluating Flutter for applications that must integrate vendor SDKs distributed only as native Android libraries. Historically, teams in banking, insurance, and healthcare have been hesitant to use Flutter for applications requiring native biometric authentication, document scanning, or video conferencing SDKs because of the platform view performance penalty. With HCPP, those concerns are substantially mitigated.

Looking ahead, the Flutter team has indicated that HCPP is the first step in a broader effort to deepen Flutter's integration with the Android graphics pipeline. Future releases are expected to expand the feature to cover additional use cases, improve performance further, and eventually graduate it from experimental to stable status. The deprecation of the Skia backend on Android 10 and above — also announced with Flutter 3.44 — means that the Vulkan-based path represented by HCPP is not just an option but the strategic direction for Flutter's Android rendering architecture.

For developers ready to experiment with HCPP today, the full implementation guide and known limitations are documented on the Flutter platform views documentation page, which was updated in mid-July 2026 to reflect the latest APIs and compatibility information.