Compose Multiplatform 1.11.0: Key Updates and Features

Welcome to the latest release of Compose Multiplatform, version 1.11.0. This update brings significant enhancements to iOS and web platforms, along with a revamped approach to UI testing. In this Q&A, we’ll explore the standout features, including native text input on iOS, concurrent rendering now enabled by default, the new Compose UI testing v2 APIs, and smoother scrolling on web targets. Whether you’re a seasoned developer or just getting started, these improvements aim to make your cross-platform apps more performant and intuitive. Let’s dive into the details.

What are the major highlights of Compose Multiplatform 1.11.0?

Compose Multiplatform 1.11.0 focuses on refining the user experience on iOS and web, while also modernizing UI testing. Key highlights include an experimental native text input implementation for iOS that leverages UIView for more precise caret movement, native gestures, and system context menus (autofill, translate, search). Concurrent rendering, previously opt-in, is now the default, offloading rendering tasks to a dedicated thread for better performance. The Compose UI testing framework gets a v2 update with StandardTestDispatcher as the default, making tests more predictable. Additionally, web scrolling performance has been substantially improved through reworked touch processing, bringing it closer to native-level smoothness.

Compose Multiplatform 1.11.0: Key Updates and Features — Source: blog.jetbrains.com

How does the new native text input work on iOS?

For developers aiming to provide a more authentic iOS experience in their Compose apps, version 1.11.0 introduces an experimental native text input built on top of UIView. This implementation enhances caret movement precision, supports native gestures and selection handles, and delivers the familiar system context menu—including Autofill, Translate, and Search. While the existing cross-platform text input remains stable and the default, you can opt into this native variant by enabling the experimental API. It’s ideal for applications where iOS-native feel is critical, but be aware it’s still in experimental stages. No additional configuration is needed beyond opting in, and you can switch back to the default anytime.

What is concurrent rendering and how is it now configured?

Concurrent rendering, first introduced as an opt-in feature in Compose Multiplatform 1.8.0, is now enabled by default in 1.11.0. This means rendering tasks are automatically offloaded to a dedicated render thread without any extra configuration. Out of the box, your apps benefit from improved performance, particularly in scenarios with heavy UI updates or animations. The change reduces the load on the main thread, leading to smoother interactions and faster frame rates. If you were previously using the opt-in flag, you can remove it; if you prefer the old behavior (not recommended), you can disable it manually. This update is especially beneficial for iOS apps where performance is crucial.

What changes come with the Compose UI testing v2 APIs?

The Compose UI testing framework receives a major upgrade with v2 APIs, now available for non-Android targets. The default dispatcher has switched to StandardTestDispatcher, ensuring that coroutines execute in the order they are queued. This makes tests more predictable and closely mirrors production behavior. Additionally, the v2 APIs introduce an effectContext parameter, allowing you to pass a custom coroutine context into your compositions. For example, you can override the motion duration scale or supply your own test dispatcher:

@OptIn(ExperimentalTestApi::class)
@Test
fun myTest() = runComposeUiTest(
    effectContext = motionDurationScale + StandardTestDispatcher()
) {
    setContent {
        MyComposable()
    }
    // assertions
}

The previous functions—runComposeUiTest, runSkikoComposeUiTest, and runDesktopComposeUiTest—are now deprecated. Migrate to the v2 counterparts for ongoing support and better consistency.

How has scrolling performance improved on web targets?

Scrolling on Compose web has historically lagged behind native platforms, but version 1.11.0 addresses this with a substantial rework of touch processing. The result is a much smoother scrolling experience that feels nearly identical to what you’d expect on Android or iOS. You can see the improvement in action with the latest web version of the KotlinConf app. For technical details, fix lists, and demos, refer to issue CMP-9727. This update makes Compose for web more viable for content-rich applications where fluid scrolling is essential.

How can developers start using Compose Multiplatform 1.11.0?

To take advantage of the new features, simply update your project dependencies to version 1.11.0. The official what’s new page provides a complete list of changes. Once updated, you can experiment with the native iOS text input (opt-in), enjoy default concurrent rendering, adopt the v2 UI testing APIs, and experience improved web scrolling. For any issues or feedback, the community and development team are active on the project’s issue tracker. Start by checking out the getting started guide and integrate these enhancements into your cross-platform apps.