Flutter 3.44's HCPP Eliminates the Performance Tax on Android Platform Views

For any Flutter app that embeds maps, video players, or WebViews on Android, HCPP removes the long-standing choice between janky scrolling and broken text selection. It makes a single, high-quality platform view implementation viable for the first time, provided the device runs Android 14 or newer.

Embedding native views like Google Maps or WebView in Flutter has always forced a trade-off: Virtual Display runs fast but breaks interaction, while Hybrid Composition fixes interaction at a steep frame-rate cost. HCPP sidesteps the old pixel-merging bottleneck entirely. Instead of copying GPU textures between Flutter's render thread and the Android main thread, it hands two independent Surfaces to the OS compositor, SurfaceFlinger, which layers them in hardware.

The result is a single approach that delivers both high rendering performance and full native interaction. The catch is a hard dependency on Android 14 or later, Vulkan graphics support, and Flutter's Impeller engine. On older devices, the engine silently falls back to the existing TLHC mode, so a single code path covers both new and old hardware.

Enabling HCPP requires a manifest flag, using PlatformViewLink with AndroidViewSurface on the Dart side, and running with the --enable-hcpp flag in profile mode. The feature is still opt-in but marks a significant step toward making Flutter's Android embedding feel truly native.