01d37bc80f
The wiki is supposed to be for team-focused documentation, but this page was client-focused. That was resolved at some point via the creation of https://docs.flutter.dev/platform-integration/android/platform-views, https://docs.flutter.dev/platform-integration/ios/platform-views, and https://docs.flutter.dev/platform-integration/macos/platform-views, and this page is now a somewhat outdated (e.g., in doesn't use code excerpting to ensure correctness like the docs page does), less client-friendly version of those pages. This removes essentially all of the duplicated content, and makes it a much smaller, team-focused page, following the format of the corresponding TLHC page in the wiki. Since there are likely external pages that linked here for the old content, this leaves a breadcrumb to the client-facing docs at the top. Fixes https://github.com/flutter/flutter/issues/124801 --------- Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2.3 KiB
For information on using platform views in a Flutter app, see the documentation for Android, iOS, and macOS.
Background
Hybrid Composition (HC) refers to a method of composing native views (for example, a native webview) alongside Flutter widgets. On Android, it is one of several modes for displaying platform views; see Android Platform Views for an overview of modes. On iOS and macOS, it is the only mode used for displaying platform views.
Approach
HC creates multiple layers of native views that are composited by the standard platform UI toolkit rather than by Flutter. This requires separating the Flutter rendering into separate views, one containing the things that are behind the native view, and another things above the native view, so that everything looks correct when composited by the system.
Because it involves coordinating multiple native views, it adds complexity to the rendering pipeline (requiring synchronization between OS rendering and Flutter rendering to avoid tearing) and event handling such as gesture resolution.
Limitations
- Thread performance. Normally, the Flutter UI is composed on a dedicated raster thread. This allows Flutter apps to be fast, as the main platform thread is rarely blocked. While a platform view is rendered with Hybrid Composition, the Flutter UI is composed from the platform thread, which competes with other tasks like handling OS or plugin messages.
- Gesture handling. Coordinating gesture resolution between Flutter's gesture arena and the native gesture system sometimes results in unexpected behaviors, such as specific gestures not working correctly over native views.
Android
- Prior to Android 10 (API 29), Hybrid Composition copies each Flutter frame out of the graphic memory into main memory and then copied back to a GPU texture. As this copy happens per frame, the performance of the entire Flutter UI may be impacted.
To see all known issues specific to this mode on Android, search for the platform-views: hc label.