Kotlin Multiplatform vs Flutter: choosing shared logic or shared UI
Flutter can build the whole app from one Dart codebase and can still drop to platform-specific code; with Kotlin Multiplatform, teams commonly share business logic and keep native UI, with shared UI via Compose Multiplatform as an option. Neither guarantees 100% sharing - adoption paths, interop models, ecosystems and version status, from JetBrains' and Google's own documentation, read 21 November 2026.
Per the vendors' own pages, read 21 November 2026: Flutter's current release is 3.50, announced on the Flutter blog on 11 November 2026, and Kotlin's current release is 2.4.21 per the kotlinlang.org releases page. Both are healthy, both build apps for Android and iOS (and beyond), and both are called "cross-platform" - but they default to sharing different layers. Flutter's common path shares the UI through its own engine; Kotlin Multiplatform's (KMP) common path shares the logic while UI stays native. And neither guarantees 100% sharing: Flutter apps can drop to platform-specific code or embed native views, and KMP apps can share UI too, via Compose Multiplatform. This article compares the two from JetBrains' and Google's own documentation and names no default winner. (For the rendering-engine axis against another contender, see our React Native vs Flutter comparison.)
The core difference: how much you share
JetBrains' own comparison page puts the split plainly: with KMP you can "share whichever part of your codebase you want to, including business logic and/or UI, from 1% to 100%", while Flutter aims at "100% code sharing across all platforms" with control over every pixel. KMP is a code-sharing technology that compiles shared Kotlin for each target while your UI stays native - SwiftUI or UIKit on iOS, Jetpack Compose on Android - unless you opt into shared UI through Compose Multiplatform. Flutter is a full app framework: one Dart codebase, one widget tree, one rendering pass everywhere.
UI: commonly native vs shared by design
On rendering, Flutter's own documentation says Impeller is the default rendering engine on iOS and on Android API 29+ as of the 3.27 release (a support matrix covers the rest), precompiling shaders at engine-build time for predictable performance; and native platform views remain embeddable when a Flutter screen needs one. Compose Multiplatform, per JetBrains' comparison table, draws through Skia-compatible backends. The practical consequence is about fidelity and familiarity. A KMP app with native UI looks and behaves exactly like a platform app because it is one - navigation, accessibility and platform widgets come free. A Flutter app renders its Flutter widgets with Flutter's own engine rather than the platform's stock widgets; the renderer implementation varies by platform and API level (Impeller default on iOS and Android API 29+, support matrix for the rest), and native views can still be embedded when needed - a feature for brand-heavy design, and a trade-off when platform purists review it. KMP's shared-UI option, Compose Multiplatform, is stable on iOS, Android and desktop and in Beta on web, per JetBrains' docs - note that Compose's status per UI target is a separate question from KMP's overall stability, and the two should not be read as one label.
Interop, tooling and ecosystem
KMP reaches native APIs directly from Kotlin via expect/actual declarations, per JetBrains' table. Flutter's own documentation describes platform channels passing messages between Flutter and the host platform (Android, iOS, macOS, Windows, Linux), with Pigeon, FFIgen and JNIgen recommended for new projects and channels remaining for low-level message passing and existing codebases. KMP libraries come from Maven Central and klibs.io (JetBrains' KMP library index); Flutter packages live on Pub.dev. KMP builds with Gradle plus Xcode for Apple targets; Flutter wraps both in its CLI. Neither interop model is "free" - platform channels mean writing a bridge per API; expect/actual means knowing each platform's API surface - but they weight the cost differently: Flutter centralizes it in packages, KMP keeps it in your code.
Maturity and backing
Kotlin Multiplatform became stable in November 2023, and Google announced its support for KMP for sharing business logic across Android and iOS at Google I/O 2024, per JetBrains' documentation. Flutter 1.0 was announced in December 2018 and is supported and used by Google. Both vendors publish customer lists - JetBrains names Forbes, Todoist, McDonald's and Google Workspace among KMP case studies; Flutter's showcase lists Xiaomi, Wolt, Alibaba Group and Google Pay - treat both as vendor-curated examples, not independent endorsement.
How the choice usually plays out
You already have native apps or a native team: KMP's incremental path is the draw - share one module (networking, validation, analytics) this quarter, not the whole app this year. You are starting fresh with a small team and want one codebase for everything, UI included: Flutter's single-pipeline model is the draw. Your app's polish bar is "indistinguishable from a first-party iOS app": native UI under KMP keeps SwiftUI in play; Flutter would approximate it. Your team knows Dart or wants one language for app and UI everywhere: Flutter. Your team is an Android/Kotlin shop eyeing iOS: KMP has the shorter learning curve. And if the deciding factor is instead how the UI gets drawn, our React Native vs Flutter piece covers that axis. Whichever framework wins, if the next step is hiring for the build, our guide to choosing a software development partner covers the evaluation.
Sources, all read 21 November 2026: kotlinlang.org, Kotlin Multiplatform and Flutter (JetBrains' comparison: share 1-100%, stability Nov 2023, Google I/O 2024 support, Compose Multiplatform stability status, tooling/interop/rendering table, vendor-listed case studies); kotlinlang.org, What is Kotlin Multiplatform; Flutter blog, What's new in Flutter 3.50 (11 November 2026); flutter.dev (multi-platform apps from a single codebase, Dart); Flutter docs, Impeller (default on iOS and Android API 29+ as of 3.27; support matrix for the rest) and Flutter docs, platform channels (message passing to host platforms; Pigeon/FFIgen/JNIgen recommended for new projects); kotlinlang.org, Kotlin releases (2.4.21).
Choosing a cross-platform stack for a real app? Omnistu's Mobile Engineering practice works on iOS and Android apps, including the publishing process for both stores - write to team@omnistu.com with what you are deciding.
Frequently asked questions
What are the current versions?
Read 21 November 2026: Flutter 3.50, announced on the Flutter blog on 11 November 2026; Kotlin 2.4.21 per the kotlinlang.org releases page. Kotlin Multiplatform has been stable since November 2023 per JetBrains' documentation.
Is Kotlin Multiplatform production-ready?
Per JetBrains' documentation: KMP itself has been stable since November 2023, Compose Multiplatform (the optional shared-UI layer) is stable on iOS, Android and desktop and in Beta on web, and Google announced support for KMP for sharing business logic across Android and iOS at Google I/O 2024. JetBrains also publishes case studies including Forbes, Todoist, McDonald's and Google Workspace - vendor-curated, but production-scale.
Can Kotlin Multiplatform share UI too?
Yes - that is what Compose Multiplatform is for: shared declarative UI built on Kotlin Multiplatform and Google's Jetpack Compose. The difference is that shared UI is an option in KMP (with native UI as the default), while in Flutter shared UI is the design.
Can Flutter call native iOS/Android APIs?
Yes, through platform channels - a bridge you write (or a Pub.dev package wrote) between Dart and the host platform. KMP's model is more direct: expect/actual declarations let shared Kotlin call native APIs without a hand-written bridge, at the cost of knowing each platform's API surface yourself.
Is this the same decision as React Native vs Flutter?
No. React Native and Flutter are both full app frameworks that own the UI; their axis is how the UI gets drawn. KMP's axis is how much of the app you share at all - logic only, logic plus UI, or a single module this quarter. Our React Native vs Flutter comparison covers the rendering question; this article covers the sharing question.
Does Flutter or KMP give better performance?
There is no honest universal answer from the vendors' docs: both compile to platform-native code for release builds, and real-world speed depends on your app, your UI complexity and your team's familiarity with each toolchain. Prototype your riskiest screen in both before letting benchmarks decide.