---
title: "Kotlin Multiplatform in 2027: Is Compose Multiplatform Ready for iOS?"
date: 2026-11-19
author: "Tobias Rast"
featured_image: "https://static.pegotec.net/uploads/2026/10/kotlin-multiplatform-2027-outlook.webp"
categories:
  - name: "Pegotec News"
    url: "/category/news.md"
---

# Kotlin Multiplatform in 2027: Is Compose Multiplatform Ready for iOS?

Kotlin Multiplatform is the quiet riser of cross-platform development. JetBrains reports that its share among cross-platform developers more than doubled, from 7% in 2024 to 18% in 2025, and Google runs it inside Google Docs on iOS. Most teams, however, ask a narrower question: can you share the user interface too, and is that ready for iOS? This outlook covers Kotlin Multiplatform in 2027: what shipped, what slipped, and the iOS deadlines ahead.

We have already looked at [Flutter in 2027](https://pegotec.net/flutter-2027-outlook/) and [React Native in 2027](https://pegotec.net/react-native-2027-outlook/). Kotlin Multiplatform is the third option, and it works differently from both.

## Two ways to use Kotlin Multiplatform

Kotlin Multiplatform lets Android and iOS share Kotlin code. The first decision is how much to share. Some teams share only business logic, such as networking, data, and rules, and keep a native interface on each platform. Others also share the interface through Compose Multiplatform, a UI framework built by JetBrains.

The difference matters for support. Google states that Kotlin Multiplatform “is officially supported by Google for sharing business logic between Android and iOS.” Compose Multiplatform, by contrast, is a JetBrains product, and Google’s own page credits it to JetBrains. Meanwhile, JetBrains’ documentation gives a clear rule: if “UX fidelity is a priority,” share only the data and business logic.

Both routes are common. In JetBrains’ own survey of Kotlin Multiplatform users, 60% of projects shared all or almost all of their business logic, and 81% of respondents used Compose Multiplatform. That is vendor data from existing users, so it says more about direction than about the whole market.

## What shipped in 2025 and 2026

Kotlin follows a fixed rhythm: a language release every six months, with a tooling release three months later. Compose Multiplatform ships on its own schedule. These were the releases that mattered for iOS teams:

| Release | Date | What matters for a business app |
|---|---|---|
| Compose Multiplatform 1.8 | May 6, 2025 | Compose Multiplatform for iOS declared stable, with VoiceOver support and iOS-style scrolling |
| Kotlin 2.3.0 | Dec 16, 2025 | iOS release builds up to 40% faster |
| Compose Multiplatform 1.11 | May 13, 2026 | Native iOS text input arrives as an experimental option |
| Kotlin 2.4.0 | Jun 3, 2026 | Swift export reaches Alpha; Swift package import in Alpha; minimum iOS raised to 15 |
| Kotlin 2.4.20 | Sep 7, 2026 | Swift export adds sealed classes; faster incremental native builds in Beta |
| Compose Multiplatform 1.12.1 | Sep 22, 2026 | Current stable release |

Google kept investing on its side, too. Room, DataStore and Collection became stable with Kotlin Multiplatform support in 2025, and ViewModel, Paging and Navigation followed. JetBrains also reported that native builds on the Google Docs codebase are now 25% faster and use less than half the memory of a year earlier.

## What slipped: Swift interop

By default, Kotlin talks to Swift through Objective-C headers. JetBrains admits this “can make Swift APIs feel less natural.” For example, generics lose detail, Kotlin enums need a default case in Swift switches, and uncaught Kotlin exceptions terminate the app unless you annotate the functions.

Swift export is the fix, and it is behind schedule. In August 2025, JetBrains wrote: “In 2026, we aim for a stable release.” Instead, Swift export reached only Alpha in June 2026, and the current roadmap’s goal is “from Alpha to Beta.” In other words, stable Swift interop is a 2027 question at the earliest.

Until then, most teams use SKIE from Touchlab, which generates friendlier Swift wrappers. It works well, but it trails each Kotlin release by a few weeks. Also note that you cannot mix SKIE and Swift export, so switching later is an all-or-nothing decision.

## iOS 27: wait for Kotlin 2.5

Apple requires uploads built with the iOS 27 SDK from April 2027, with a minimum of iOS 15. Kotlin 2.4 already raised its own minimum to iOS 15, so that part is covered.

Xcode 27 support is not yet. Kotlin’s compatibility table still lists Xcode 26.4 for the current 2.4.20 and 2.4.21 releases. The Xcode 27 update landed in the 2.5 line, and JetBrains plans Kotlin 2.5.0 for December 2026. Similarly, only the 1.13 alpha fixes a Compose Multiplatform crash when a text field loses focus on iOS 27.

The scene lifecycle, which crashes React Native apps on iOS 27, is less of a problem here. The official project templates start the app from SwiftUI and already declare a scene manifest, so new projects are in good shape. Older apps built around a UIKit AppDelegate, however, still need the migration. Even JetBrains’ own iOS test suite hit the error: “UIScene life cycle is required for apps built with this SDK.”

Our [iOS 27 and Android 17](https://pegotec.net/ios-27-and-android-17-what-developers-need-to-know/) article covers the platform changes in full.

## CocoaPods matters less here

The central CocoaPods repository is due to go read-only on December 2, 2026. Unlike React Native, Kotlin Multiplatform does not depend on it by default. New projects from the IDE plugin use direct integration, where an Xcode build step compiles the Kotlin framework.

Projects that still use the CocoaPods plugin keep working, because JetBrains has not deprecated it. Still, JetBrains now publishes a migration guide toward direct integration and Swift packages. Importing Swift packages into Kotlin is in Alpha, though, and it reaches only APIs visible to Objective-C.

## Android: business as usual

On Android, a Kotlin Multiplatform app is simply an Android app. Its shared code compiles to ordinary JVM bytecode, so Google Play’s February 1, 2027, rule on 16 KB memory pages rarely touches it. Only native libraries compiled with Kotlin/Native need attention.

The August 2027 move to Android 17 (API 37) applies to any Android app. Orientation locks stop working on screens at least 600dp wide. Compose Multiplatform supports the adaptive layout APIs needed to handle that.

## Is Compose Multiplatform ready for iOS?

Officially, yes. JetBrains declared it stable for iOS in May 2025 and calls it “production-ready.” It also claims startup “comparable to native apps” and only about 9 MB of extra app size compared with SwiftUI. However, JetBrains has not published the methodology it promised for those figures, and we found no independent 2026 benchmark.

Like Flutter, Compose Multiplatform draws its own interface rather than using native iOS controls. So it does not get Apple’s Liquid Glass design for free. JetBrains says it has no plans “to provide liquid glass components as a core part” of the library. Instead, newer interop APIs let teams place native SwiftUI or UIKit components over Compose screens.

Some gaps remain. Native iOS text input is still experimental, and making it the default is on the current roadmap. An open, major-priority issue reports that secure password fields expose their content to VoiceOver. JetBrains plans to support Apple’s foldable iPhone Duo in version 1.14. Teams that share only business logic avoid all of this, because their iOS interface is plain SwiftUI.

## Tooling: iOS developers stay in Xcode

In October 2026, JetBrains removed Swift editing from its Kotlin Multiplatform plugin, starting with IntelliJ IDEA 2026.3. Its reason was frank: usage “was limited and steadily declining,” because iOS developers prefer Xcode. Running iOS apps and debugging Kotlin code remain supported, but no replacement is planned.

That makes the Xcode side more important. Debugging Kotlin from inside Xcode still relies on a community plugin, although official Xcode debugger integration is now on JetBrains’ roadmap. Builds also need macOS for iOS, and the docs warn that release builds take “an order of magnitude more time” than debug builds. Plan CI capacity accordingly.

## Who uses it in production?

Google’s case is the strongest proof for shared logic. Its Google Docs app on iOS runs Kotlin Multiplatform code in production, with performance “on par or better than before.” Duolingo and McDonald’s have also presented their production use at KotlinConf.

For shared UI, Bitkey by Block is a useful example. Kotlin Multiplatform makes up “about 95%” of its codebase, with Compose Multiplatform on both platforms. Interestingly, the team rejected React Native and Flutter because they “would lead to a larger dependency graph.” JetBrains also names Sony’s Sound Connect app as a shared-UI user.

Growth is real but starts from a small base. Citing Appfigures data, JetBrains says Kotlin Multiplatform’s presence among the top 10,000 App Store apps rose from under 1% in early 2024 to almost 3% by mid-2026. Its library directory, klibs.io, now lists more than 4,600 libraries.

## Should you choose Kotlin Multiplatform in 2027?

It is a strong fit when:

- You already have an Android team working in Kotlin and want to reach iOS.
- Each platform must keep a fully native interface, including Liquid Glass on iOS.
- You want to adopt it step by step inside existing native apps, as Google did with Docs.

On the other hand, think twice when:

- Nobody on the team writes Swift, since even the shared-logic route needs SwiftUI skills.
- You want one shared interface that feels fully native on iOS today.
- The web matters, because Compose Multiplatform for web is still in Beta.

Part 4 of this series compares Kotlin Multiplatform, Flutter, and React Native side by side.

## How to prepare your Kotlin Multiplatform app for 2027

1. **Keep releasing with Xcode 26 until Kotlin 2.5.0 ships.** Then move to Xcode 27 well before April 2027.
2. **Check your iOS entry point.** A SwiftUI app with a scene manifest is fine; a UIKit AppDelegate needs the scene migration.
3. **Move off the CocoaPods plugin.** Follow JetBrains’ guide to direct integration or Swift packages.
4. **Choose your Swift interop path.** SKIE works today, while Swift export is the long-term option, and you cannot mix the two.
5. **Test shared UI on real iPhones.** Focus on text input, VoiceOver, and scrolling, where the gaps are known.
6. **Budget macOS build capacity.** Release builds are far slower than debug builds.

## How Pegotec helps

Choosing how much to share shapes a Kotlin Multiplatform project, so we start there. We map which parts of your app benefit from shared code and which should stay native. Then we plan the 2027 upgrades around Apple’s and Google’s deadlines.

If you are weighing Kotlin Multiplatform for a new or existing app, [talk to us](https://pegotec.net/contact-us/).

## Read next

- [Flutter in 2027](https://pegotec.net/flutter-2027-outlook/) — the outlook for Google’s own UI framework.
- [React Native in 2027](https://pegotec.net/react-native-2027-outlook/) — the iOS 27 crash and the Shopify exit.
- [iOS 27 and Android 17: What Developers Need to Know](https://pegotec.net/ios-27-and-android-17-what-developers-need-to-know/) — the platform changes behind the 2027 deadlines.

## FAQ

**Is Kotlin Multiplatform production-ready in 2027?**For sharing business logic, yes. Kotlin Multiplatform has been stable since late 2023, Google officially supports it for sharing logic between Android and iOS, and Google Docs on iOS runs it in production. The less mature parts are on the iOS side: Swift export is still in Alpha, and full Xcode 27 support arrives with Kotlin 2.5.0, planned for December 2026.

 

**Is Compose Multiplatform ready for iOS?**JetBrains declared Compose Multiplatform for iOS stable in May 2025, and companies such as Bitkey ship shared UI with it. Gaps remain, though: native iOS text input is still experimental, an open issue reports secure password fields exposing content to VoiceOver, and there is no built-in Liquid Glass support. Test text input, accessibility and scrolling on real devices before committing.

 

**Does Google support Compose Multiplatform?**Not officially. Google supports Kotlin Multiplatform for sharing business logic between Android and iOS, and several Jetpack libraries such as Room, DataStore and ViewModel support it. Compose Multiplatform, which shares the user interface, is built and supported by JetBrains, and Google’s own documentation credits it to JetBrains.

 

**Does Kotlin Multiplatform support Xcode 27?**Not in a stable release yet. As of mid-October 2026, Kotlin’s compatibility table lists Xcode 26.4 for Kotlin 2.4.20 and 2.4.21. The Xcode 27 update is part of Kotlin 2.5.0, which JetBrains plans for December 2026. Apple requires the iOS 27 SDK for uploads from April 2027, so plan the switch for early 2027.

 

**Does Compose Multiplatform support Liquid Glass?**Not as built-in components. JetBrains has said it currently has no plans to provide Liquid Glass components as a core part of Compose Multiplatform. Instead, interop APIs let teams place native SwiftUI or UIKit components, which do use Liquid Glass, over Compose screens. Teams that share only business logic get Liquid Glass automatically, because their iOS interface is native SwiftUI.