Compatibility and versions

Supported platforms

Compose Multiplatform 1.6.11 supports the following platforms:

• Android

• iOS

• macOS (x86-64, arm64)

• Windows (x86-64)

• Linux (x86-64, arm64)

• Web browsers

Limitations of Compose Multiplatform for desktop releases

Compose Multiplatform for desktop has the following limitations:

• Only JDK 11 or later is supported due to the memory management scheme used in Skia bindings.

• Only JDK 17 or later is supported for packaging native distributions due to jpackage limitations.

• There is a known issue with OpenJDK 11.0.12 when switching keyboard layouts on macOS. This issue isn't reproducible in OpenJDK 11.0.15.

Kotlin compatibility

As long as you are using Compose Multiplatform 1.6.10 or higher and Kotlin 2.0.0 or higher, Compose Multiplatform is compatible with Kotlin. There is no need to manually align their versions. Remember that using an EAP version of either product is still potentially unstable.

Compose Multiplatform requires Compose Compiler Gradle plugin applied with the same version as the Kotlin one. See Migrating a Compose Multiplatform project for details.

Jetpack Compose and Compose Multiplatform release cycles

Compose Multiplatform shares a lot of code with Jetpack Compose for Android, a framework developed by Google. We align our Compose Multiplatform release cycle with the release cycle of Jetpack Compose so that the common code is properly tested and stabilized.

When a new version of Jetpack Compose is released, we:

• Use the release commit as a base for the next Compose Multiplatform version.

• Add support for new platform features.

• Stabilize all platforms.

• Release a new version of Compose Multiplatform.

The gap between a Compose Multiplatform release and a Jetpack Compose release is usually 1–3 months.

When you build your application for Android, the artifacts published by Google are used. For example, if you apply the Compose Multiplatform 1.5.0 Gradle plugin and add implementation(compose.material3) to your dependencies , then your project will use the androidx.compose.material3:material3:1.1.1 artifact in the Android target ( but org.jetbrains.compose.material3:material3:1.5.0 in other targets). See the following table to find out exactly which version of Jetpack Compose artifact is used: