What’s New in Compose Multiplatform 1.11.0: Key Features and Improvements

Welcome to our Q&A overview of Compose Multiplatform 1.11.0. This release brings meaningful enhancements to iOS and web platforms, along with a revamped approach to UI testing. Below we answer the most common questions about the update, covering native text input, performance gains, and testing changes. For a complete list of modifications, refer to the official changelog.

1. What is the new native text input feature on iOS and why is it important?

Compose Multiplatform 1.11.0 introduces an experimental native text input implementation for iOS, built on top of UIView. This gives text fields a more authentic Apple feel by offering precise caret movement, native gestures, selection handles, and the full system context menu—including Autofill, Translate, and Search. While the existing cross-platform text input remains the stable default, developers can now opt in to a more native experience on iOS devices. This is a significant step for making Compose iOS apps feel at home on Apple platforms, especially for apps heavily reliant on text entry. To enable it, simply update your dependencies and follow the migration guide in the release notes.

2. How has concurrent rendering been improved in 1.11.0?

Concurrent rendering, which was first introduced as an opt-in feature in version 1.8.0, is now enabled by default in Compose Multiplatform 1.11.0. Rendering tasks are automatically offloaded to a dedicated render thread, so your applications get performance benefits without any extra configuration. This results in smoother animations and more responsive UIs, especially on iOS devices. Developers no longer need to manually opt in, and can expect a noticeable improvement in rendering efficiency out of the box. For those who previously enabled it, no changes are required; for new projects, the default behavior just got faster.

3. What changes have been made to UI testing in this release?

Version 1.11.0 upgrades UI testing for non-Android targets with support for the v2 ComposeUiTest APIs. The default dispatcher is now StandardTestDispatcher, making coroutines run in the order they are queued—resulting in more predictable tests that mirror production behavior. The v2 APIs also accept an effectContext parameter, allowing you to pass a custom coroutine context—for instance, to override motion duration scale or supply your own test dispatcher. The previous APIs (runComposeUiTest, runSkikoComposeUiTest, and runDesktopComposeUiTest) are deprecated in favor of these new versions. Developers are encouraged to migrate to ensure long-term compatibility and take advantage of better test reliability.

4. How does scrolling performance on the web improve in 1.11.0?

Scrolling on Compose for web has lagged behind native targets, but 1.11.0 substantially reworks touch processing to bring it much closer to parity. The result is smoother, more responsive scrolling experiences in Compose web applications. You can see this improvement in action in the latest web version of the KotlinConf App. The team has also fixed several bugs and provided demos in the issue tracker (see CMP-9727). This upgrade makes Compose Multiplatform a more viable option for building full-featured web UIs that feel native. No extra configuration is needed—just update your dependencies to benefit from the enhanced scrolling behavior.

5. Are there any deprecated APIs I should be aware of?

Yes, the previous UI testing APIs—runComposeUiTest, runSkikoComposeUiTest, and runDesktopComposeUiTest—are now deprecated. Their v2 counterparts (with the same names but updated signatures) should be used instead. The v2 APIs provide better test predictability through StandardTestDispatcher and offer the new effectContext parameter for custom coroutine contexts. To migrate, update your imports and replace old function calls with the new ones; the code structure remains largely similar. Also note that the native text input for iOS is experimental, so its API may change in future releases. Check the migration guide or release notes for step-by-step instructions.

6. How do I get started with Compose Multiplatform 1.11.0?

To start using Compose Multiplatform 1.11.0, update your project dependencies to the latest version from the official repository. The team provides a Getting Started guide on the JetBrains website with step-by-step instructions for setting up a new project or upgrading an existing one. For iOS-specific features like native text input, follow the opt-in instructions in the release notes. Web users can simply update and enjoy smoother scrolling. As always, test your app thoroughly and report any issues. The full changelog and “What’s New” document cover all changes not mentioned here. Happy coding!