Compose Multiplatform for iOS Is Stable: Kotlin Apps on iPhone

If your Android app is written in Kotlin with Jetpack Compose, the question of an iPhone version usually arrives sooner or later. Until recently the answers were to build a second app from scratch or to rewrite everything in Flutter or React Native. Compose Multiplatform adds a third answer: reuse the Kotlin code and the screen designs you already have. This post explains what became stable, what is still moving, and when it makes sense.

What was announced, and when

Compose Multiplatform is a toolkit from JetBrains, the company behind the Kotlin language, that lets one set of Compose screens run on Android, iPhone, desktop and, in a still-developing form, the web. The GitHub release record shows version 1.8.0 was published on 6 May, and JetBrains' announcement the same month states that Compose Multiplatform for iOS is stable and production-ready. In plain terms, JetBrains now promises that the main building blocks will not change in ways that break your app.

As of November 2026 the current version listed in the Kotlin documentation is 1.12.2, which requires at least Kotlin 2.1.0. The same documentation sets the minimum iPhone software at iOS 14 and describes iOS and web among the platforms with "rapidly evolving support". Treat that as a reminder to check the version notes before each upgrade, not as a warning against using it.

What works on iPhone

According to the JetBrains announcement, the stable release covers the following:

• Screens that behave like their Android versions for common needs, including type-safe navigation with deep links.
• Accessibility support for VoiceOver, AssistiveTouch and Full Keyboard Access on iPhone.
• Native-feeling scrolling and text selection, and respect for the phone's font-size and contrast settings.
• Two-way mixing with SwiftUI and UIKit, Apple's own screen systems, so you can add Compose screens to an existing iPhone app or drop a native Apple component into a Compose screen.

That last point matters for budgets. You can adopt it one screen at a time instead of committing the whole app. JetBrains names Markaz, Wrike, Feres and Physics Wallah as companies doing exactly that, and says the Respawn iPhone app shares about 96 percent of its code with Android. These are the company's own examples, and your result will depend on how much of your app is screens versus phone-specific features.

The costs and limits to know about

JetBrains states that a Compose app adds about 9 MB to the iPhone app size compared with a fully native SwiftUI app having the same logic and assets. For most business apps that is irrelevant, but it matters if your customers are on low-storage phones. The company also reports launch time close to native and scrolling that matches SwiftUI, based on its own benchmark project, so ask for a demo build on a real iPhone rather than relying on claims.

Web support is the part to be careful with. It is moving fast and some of its features are still marked experimental in the announcement. If a website is part of your plan, build it as a normal website and keep the Compose work for the app itself.

Finally, the iPhone side still needs an Apple developer account, a Mac for builds, App Store review and testing on real devices. Sharing code reduces the work; it does not remove the platform.

How it compares with Flutter and React Native

All three let one team serve two phone platforms. The difference is where your existing investment sits.

• Compose Multiplatform is the natural continuation if your Android app is already Kotlin and Compose. Your developers keep one language and one way of building screens.
• Flutter uses a different language, Dart, and its own widget system. It is a fine choice for a new app on both platforms, but it means a rewrite of an existing Kotlin app. See our post on the latest Flutter releases.
• React Native suits teams who think in JavaScript and React, and can share some code with a web app. See React Native and Expo.

For a broader decision framework, our guide Flutter vs React Native vs Native Android remains the best starting point.

When an Android-first business should consider it

It is worth a serious look when three things are true. Your app is already built in Kotlin with Compose. A meaningful number of customers or staff use iPhones. And the iPhone screens would look and behave much like the Android ones. A field-sales app, a booking app and a school-parent app often fit this pattern.

It is not the right call when you have no iPhone users, when the iPhone version needs a very different design, or when the app leans heavily on phone-specific features. In India, where Android usage is very high among many customer groups, plenty of businesses are better served by shipping a polished Android app first. Our post on whether your business needs an app covers that question.

Questions to ask before you commit

1. Which screens would be shared, and which would be written natively for iPhone?
2. Which Compose Multiplatform and Kotlin versions will the project start on, and who handles upgrades?
3. Can we see a working demo on an actual iPhone before the full build is approved?
4. What happens to the Apple account, certificates and source code at handover?

VS Tech Builders builds native Kotlin and Jetpack Compose apps, as described on our Jetpack Compose app development page. If you already have an Android app and want an honest view on adding iPhone, tell us about it and we will say whether sharing the code is worth it or whether a separate approach is cleaner.

Sources

Checked on 3 November 2026. Technology changes quickly; always confirm details with the official source before you act on them.

• Compose Multiplatform 1.8.0 Released: Compose Multiplatform for iOS Is Stable and Production-Ready — The Kotlin Blog (JetBrains)
• Compose Multiplatform 1.8.0 release — JetBrains on GitHub
• Compatibility and versions — Kotlin Multiplatform documentation (kotlinlang.org)

Frequently asked questions

Is Compose Multiplatform for iOS ready for production?

JetBrains declared the iOS part stable with version 1.8.0 in May 2025, and says several companies already use it in production apps. Stable means the main interfaces should not change in breaking ways. You should still test on real iPhones, check the current version notes, and keep upgrades planned.

Do I need a Mac to publish a Compose Multiplatform app on iPhone?

Yes. Building and submitting an iPhone app requires Apple's tools, which run on a Mac, plus an Apple Developer account. Sharing Kotlin code between Android and iPhone does not remove those requirements. Your developer or studio should handle builds, certificates and App Store review, and give you ownership of the account.

Is Compose Multiplatform better than Flutter?

Neither is better in general. If your Android app is already in Kotlin and Compose, Compose Multiplatform lets you reuse it. If you are starting a new app on both platforms with no existing code, Flutter is equally reasonable and has a larger library ecosystem. Choose based on your existing code and team skills.

Can I use Compose Multiplatform for my website too?

Technically there is web support, but it is still developing and some features are marked experimental. For a business website that must load quickly and rank on Google, a conventional website is the better choice. Use Compose for the app screens and keep the public site separate.