## I Embedded a Native Camera Preview in Flutter (And Learned Exactly Where MethodChannel Stops Being Enough) Seven years into mobile engineering, I wanted to answer a question I've seen a few times: when do you actually need PlatformView instead of MethodChannel? Most answers I've seen are either "PlatformView is for native UI" (true, but not useful) or skip straight to copy-pasteable boilerplate with none of the failure modes that actually teach you anything. Over the weekend, I built a small Flutter app that embeds a native Android camera preview with a live ML Kit face-detection overlay, drawn natively, not through a Flutter widget stacked on top. This article is the build and, more usefully, the three things that broke along the way and what each one taught me about how Flutter's native bridging actually works under the hood. ## Why MethodChannel wasn't the question Before touching code, it's worth being precise about something I initially framed loosely myself: `MethodChannel` isn't "too weak" for native work; it's just the wrong tool for a specific job. It's a request/response bridge. Dart calls a method, native code handles it, returns a result. For one-off calls, biometric auth, reading an NFC tag, taking a photo, it's genuinely the right tool, no asterisk needed. What it categorically cannot do is put a native `View` inside your Flutter widget tree. It moves data, not UI. The moment you need an actual native surface rendering live inside your layout- a camera preview, a map SDK's own view- you need `PlatformView`. That's not a performance tradeoff or a style preference. It's the only mechanism Flutter gives you for that job. So the real architecture question for LensBridge wasn't "MethodChannel or PlatformView". It was "PlatformView for the pixels, MethodChannel for the commands," running side by side, each doing what it's actually built for. ## The architecture * **`PlatformView`** hosts a `PreviewView` (CameraX) wrapped in a `FrameLayout`, with a second custom `View` stacked on top for drawing detection boxes * **`ImageAnalysis`** (a separate CameraX use case from `Preview`) feeds frames to ML Kit's on-device face detector * **`MethodChannel`** handles the three things Dart needs to _tell_ native code to do: switch lens, stop, start class CameraPlatformView( private val context: Context, viewId: Int, private val lifecycleOwner: LifecycleOwner ) : PlatformView { private val previewView: PreviewView = PreviewView(context).apply { implementationMode = PreviewView.ImplementationMode.COMPATIBLE } private val overlayView: OverlayView = OverlayView(context) private val container: FrameLayout = FrameLayout(context).apply { addView(previewView, FrameLayout.LayoutParams(MATCH_PARENT, MATCH_PARENT)) addView(overlayView, FrameLayout.LayoutParams(MATCH_PARENT, MATCH_PARENT)) } override fun getView(): View = container // ... } Two lines in there, `implementationMode` and the explicit `LayoutParams`, look unremarkable. They cost me two separate debugging sessions. More on both below. ## What actually broke ### 1. `unbindAll()` doesn't clear the surface After wiring MethodChannel controls for Stop, hitting it left the last camera frame frozen on screen instead of going blank. Not a bug. `PreviewView` is backed by a `SurfaceView`/`TextureView`, and `unbindAll()` stops new frames from being pushed but never explicitly clears the existing buffer. Nothing tells the GPU to draw anything else over it, so the last frame just sits there. Confirmed it was genuinely stopped (not stalled) by waving a hand in front of the camera. No update. Fixed it by explicitly toggling `previewView.visibility` on stop/start rather than relying on frame delivery to communicate state. ### 2. A completely silent 0×0 view Once ML Kit was wired up and logcat confirmed detection was running (`face_count=1` in the stats), nothing appeared on screen. No crash, no warning. The overlay simply didn't render. The cause: I added the overlay view to its container with `addView(view)` and no explicit `LayoutParams`. Default behavior is `WRAP_CONTENT`, and since `OverlayView` has no intrinsic content, it's just a custom `View` doing manual canvas drawing, it measured out to 0×0. `onDraw()` was being called the whole time, just onto a canvas with no area to draw into. addView( overlayView, FrameLayout.LayoutParams( FrameLayout.LayoutParams.MATCH_PARENT, FrameLayout.LayoutParams.MATCH_PARENT ) ) This is the one I'd flag hardest to anyone stacking a custom-drawn view over a CameraX preview: the pipeline can be entirely correct and you'll still see nothing, because the bug isn't in your detection logic at all. ### 3. SurfaceView doesn't respect view z-order Even after fixing #2, the overlay _still_ didn't show, except for a single frame that flashed the instant I hit Stop. That flash was the clue. `PreviewView` defaults to `ImplementationMode.PERFORMANCE`, which renders through a `SurfaceView`. `SurfaceView` content composites through a separate hardware layer, outside Android's normal view-drawing pass, meaning it can visually sit above other views in the same layout regardless of their z-order in code. My overlay was drawing correctly the entire time. It was just being painted over, every frame, by the camera feed's hardware-composited layer underneath it. The fix is a documented tradeoff, not a hack: previewView.implementationMode = PreviewView.ImplementationMode.COMPATIBLE `COMPATIBLE` forces a `TextureView` instead, which renders as a normal part of the view hierarchy, with predictable layering, at the cost of losing `PERFORMANCE` mode's hardware-layer fast path. For a demo like this, that's the right trade every time. ## The part I'd actually reconsider If I rebuilt this today, I'd add the `COMPATIBLE` implementation mode from the start rather than discovering it two bugs deep. It's a known CameraX behavior. I just hadn't hit it firsthand before. Code's on GitHub: https://github.com/droidchief/lense_bridge

You Know MethodChannel. There Are Three Others — and Each Solves a Different Problem.

Bluetooth, NFC, biometrics, background sensors — sooner or later every Flutter app needs something the framework doesn’t expose. Platform…

Taqlyn deferred deep links Flutter plugin — thin MethodChannel bridge to native SdkCore. Changelog excerpt: - Initial Flutter plugin: MethodChannel bridge to native SdkCore - Dart facade: configure, resolveDeferred, observeLinks, consume, setReadyForNavigation - Optional linkProcessingMode: all | webOnly | deferredOnly

Manda byte a una stampante termica da Flutter - trasporto TCP in Dart puro e trasporto USB via platform channel verso Kotlin, con gli stati della stampante su un flusso. Changelog excerpt: Prima versione. - `PrinterTransport`: aprire, scrivere byte, chiudere, e un flusso di stati. - `TcpPrinterTransport`: Dart puro verso una stampante di rete, porta 9100. - `UsbPrinterTransport`: `MethodChannel`per le operazioni ed `EventChannel`per gli stati, verso il codice Kotlin. - `PrinterStatus`: decodifica dei quattro byte dell’Automatic Status Back, con la verifica dei bit fissi. `PrinterStatusReader`accumula e riallinea i byte che arrivano a pezzi. - `PrinterFailure`: gerarchia chiusa, c[...]

The platform interface contract for zuraffa_permissions: the MethodChannel protocol and the PermissionPort bridge platform implementations conform to. Changelog excerpt: - Initial release: the platform interface contract for `zuraffa_permissions`. - `PermissionPlatformInterface`(`plugin_platform_interface`token) with the factory default and `MethodChannelZuraffaPermissions`driver. - `MethodChannelPermissionAdapter`: the `PermissionPort`implementation bridging the typed Dart contract onto the native MethodChannel protocol (request/check/openSettings per scope). - Endorsed platform implementations (`zuraffa_permissions_android`/`_ios`/`_macos`) conform to this con[...]

Replay test kit for kamera. A thin controller that drives the native KameraReplay facade over a control MethodChannel for E2E tests. Pixels never cross the bridge — only fixture ids and the machine-re [...] Changelog excerpt: ### Fixed - React Native (Android): the preview no longer renders black. React Native never re-lays out children a native view adds after mount, so PreviewView's lazily added TextureView stayed 0×0 and CameraX timed out waiting for the preview surface (no preview, no analysis frames); the view manager now hosts the preview in a view that re-runs measure/layout itself. - Publishing: `publish-all`no longer reports the Flutter and React Native wrapper jobs as failed while their dispatched runs are[...]

Replay test kit for kamera. A thin controller that drives the native KameraReplay facade over a control MethodChannel for E2E tests. Pixels never cross the bridge — only fixture ids and the machine-re [...]

Flutter bridge for the debug_control_plane Kotlin core (Android only). MethodChannel bridge: Dart Capability -> native ControlPlane. Changelog excerpt: - 首个 pub.dev 版本。Android MethodChannel 桥:Dart Capability 注册到原生 ControlPlane(via NanoHTTPD server),支持正向调用 / SSE 事件流 / 反向 invoke(native → Dart capability)。 - Kotlin 核心经 JitPack 坐标 `com.github.xiaolutang:debug_control_plane:0.2.0`分发(源码 tag v0.2.0,同一 repo)。 - Dart 侧依赖 debug_control_plane ^0.1.1(pub.dev)。

iOS federated implementation for Vesper Player Flutter plugin. Changelog excerpt: ### Added - Added MethodChannel mapping for external subtitle configurations and `setSubtitleStyle`, backed by the iOS host-kit subtitle overlay. - Added complete RTMP, RTSP, and HTTP-FLV protocol wire mapping with explicit iOS unsupported playback errors. - Added track support, catalog revision, playback-path, and structured fixed-track error mapping for the iOS wire contract. ### Breaking Changes - MethodChannel, EventChannel, and platform-view identifiers now use the `io.github.umbrella22`[...]

Android federated implementation for Vesper Player Flutter plugin. Changelog excerpt: ### Added - Added MethodChannel mapping for external subtitle configurations and `setSubtitleStyle`, backed by the Android host-kit cue overlay. - Added complete RTMP, RTSP, and HTTP-FLV protocol wire mapping. - Added track support, catalog revision, playback-path, and structured fixed-track error mapping for the Android wire contract. ### Breaking Changes - The Android plugin package moved to `io.github.umbrella22.vesper.player.flutter.android`; its channels moved to `io.github.umbrella22.ve[...]

macOS platform implementation of flutter_barcode_sdk. Changelog excerpt: - Initial release. - macOS implementation of `flutter_barcode_sdk`using the Dynamsoft Barcode Reader C++ SDK (11.6.1000, universal-2 dylibs bundled). - Implements all methods of `BarcodeSdkPlatform`over the `flutter_barcode_sdk`MethodChannel.

A production-ready Flutter plugin for native communication push notifications with user avatars on iOS (INSendMessageIntent) and Android (MessagingStyle). Changelog excerpt: - Added **Inline Quick Reply**: - Android `RemoteInput`with `BroadcastReceiver`/ MethodChannel handling for banner text replies. - iOS `UNTextInputNotificationAction`+ `UNNotificationCategory`for direct notification replies. - Exposed `onReplyReceived((String text, int notificationId, String conversationId) => ...)`listener and `replyPlaceholder`, `replyButtonTitle`on `CommunicationNotification`. - Added **Smart Disk Avatar Cache (0ms)**: - Persistent disk-based avatar image caching by[...]

A Flutter text widget that stays invisible in iOS screenshots, screen recordings, AirPlay mirroring and the App Switcher, while looking like a normal Text. Changelog excerpt: - Initial release. - `SecureText`widget that renders text excluded from iOS screenshots, screen recordings, AirPlay mirroring and the App Switcher preview. - API mirrors `Text`: `data`, `style`, `textAlign`, `maxLines`, `textDirection`, `softWrap`. - Live style/data updates flow through a per-view `MethodChannel`with no native view recreation (no flicker). - Graceful fallback to a plain `Text`on Android, web and desktop.

The most complete Flutter plugin for Home Screen Widgets. Create, configure, and manage widgets entirely from Flutter. Changelog excerpt: ### Added - **Core API**— `NativeHomeWidgets`facade with data, lifecycle, query, deep link, and accessibility methods - **Models**— `WidgetInfo`, `WidgetSize`, `WidgetTheme`, `WidgetAction`, `WidgetData`, `WidgetConfiguration`, `NativeWidgetState` - **Platform Interface**— Abstract contract with MethodChannel implementation - **Event Streams**— `onWidgetClicked`, `onWidgetAdded`, `onWidgetRemoved`, `onWidgetUpdated` - **Exceptions**— 7 typed exceptions with PlatformException mapping - **Android[...]

Discover (Epson/Sunmi/Zebra/Star/SNMP/USB) and print ESC/POS receipts to network, USB, Star and Sunmi/iMin printers. Full on Android; network + Star on iOS. Changelog excerpt: - Initial Android implementation: a federated Flutter plugin wrapping the Universal Printer Kotlin SDK over a `MethodChannel`. - **Discovery:**Epson (ENPC), Sunmi (mDNS), Zebra, SNMP (Bixolon/Citizen/Brother/Seiko), generic network (TCP-9100), USB — plus `discoverAll`and `ping`. - **Printing:**ESC/POS network & USB, Star (StarXpand), Sunmi/iMin built-in; centralized `PrintDocument`builder with `PrintType.text`(native ESC/POS) and `PrintType.image`(HTML → WebView → bitmap); `receiptHtml`for previ[...]

Argo Flutter plugin. Supports Android, iOS, and OpenHarmony (ohos). Changelog excerpt: 1. 新增 OpenHarmony（ohos）平台支持（OpenHarmony 社区 Flutter） 2. ohos 侧通过 MethodChannel `argo_flutter_plugin`桥接方舟鸿蒙 SDK `asd_hm_sdk` 3. SDK 约束调整为 `>=2.12.0 <4.0.0`，支持 Dart 3.x（同时兼容 Dart 2.12+ 空安全） 4. Android `build.gradle`补充 `namespace`，修复新版 AGP（8+）下 `Namespace not specified`编译失败 5. Android / iOS / Dart API **无 breaking change**；仅使用 Android/iOS 的工程升级到 4.5.0 无需改代码 6. 鸿蒙侧初始化仍在宿主 `AbilityStage`完成（与 Android `Application`/ iOS `AppDelegate`一致） 7. 说明：鸿蒙 SDK 公开文档覆盖的 API（track / pageView / alias / profileSet / 通用[...]

A headless Flutter plugin providing a universal card-reading engine for Fintech apps — NFC (EMV/ISO 7816), OCR, and manual entry. Native NFC hardware bridge via MethodChannel; all APDU/EMV logic in Dart. Changelog excerpt: - `CardScannerOverlay`: English default coaching hints, with `enableCoachingHints`, `sideLightHint`, and `torchHint`overrides.

A Flutter plugin for BLE scan and connect on Android and iOS. Changelog excerpt: - 初始版本：支持 Android / iOS BLE 扫描、连接、断开 - MethodChannel + EventChannel - 扫描结果流、连接状态流

Flutter plugin for integrating the Timekettle translation SDK on Android and iOS. Changelog excerpt: - Initial public release for Android and iOS. - Wraps Timekettle Translation SDK 1.2.0 through MethodChannel and EventChannel APIs. - Android resolves the native SDK from Maven Central and its public transitive dependencies from the public Jiagouyun Maven repository. - Supports online and offline translation sessions, language discovery, session events, diagnostics, and offline model management. - Requires Android minSdk 28 and iOS 17.0.

Flutter bridge to the Tight mileage tracking SDKs (iOS and Android) via platform channels: permissions, detection modes, semi-auto drives and a stream of native drive events. Changelog excerpt: - Initial POC, verified against the public Tight SDK **v6.0.0**on both platforms. - Dart API over `MethodChannel`+ `EventChannel`: initialize, isSetup, teardown, permissions, detection mode, semi-auto drive control, getCurrentDrive, Bluetooth devices (Android only), and a `Stream`. - iOS bridge (Swift, SPM, `SDK.manager`) guarded for iOS 17 with graceful `unsupported_os`fallback below it. Builds and runs on the iOS simulator. - Android bridge (Kotlin, coroutines, `ActivityAware`permi[...]