Kotlin
A concise multiplatform language developed by JetBrains
Kotlin Multiplatform Development Roadmap for 2025
As Kotlin Multiplatform is now firmly established, development teams across the globe – including major companies like Shopify, Forbes, Haier, and Zürcher Kantonalbank – can harness its power in production environments. During Google I/O 2024 in May, Google announced their official support for Kotlin Multiplatform for sharing business logic across Android and iOS. This and other remarkable advancements set a strong foundation for further stabilizing and refining the technology.
For 2025, JetBrains is focused on enhancing the Kotlin Multiplatform ecosystem, including upgrading Compose Multiplatform for iOS to Stable, the first public releases of Kotlin-to-Swift export and the all-in-one KMP IDE, as well as other significant improvements to the core technology, tooling, and libraries. Read on to explore our key priorities and goals for the upcoming year.
Additionally, we recently updated our Kotlin roadmap to reflect our evolving vision. Be sure to check it out for more insights into our plans.
Compose Multiplatform
We are committed to making Compose Multiplatform a framework that enables developers to create beautiful and performant applications, ensuring a consistent look across all supported platforms. Our primary focus is driving the iOS target to a Stable release, which will also enhance the experience for other targets.
Currently, we are concentrating on several key areas:
- Jetpack Compose feature parity. We are working to ensure that all core APIs and components are multiplatform. Significant progress has been made, but we still have some remaining elements to address before the Stable release. Our focus is on infrastructural changes that will streamline this process.
- iOS rendering performance. We have delivered significant improvements in rendering performance for iOS. Our next steps include implementing benchmarking infrastructure to catch regressions and to ensure that the performance of the framework is transparent to users.
- Feature completeness for core components. We are prioritizing the completion of essential features, including navigation, resource management, accessibility, and internationalization.
- Stabilizing the interoperability between Compose and native views is also a key objective.
- General stabilization of the framework. We are committed to improving the overall stability of the framework and enhancing the user experience through Compose Multiplatform Previews.
- Documentation. Our goal is to provide users with all the resources they need to learn and use Compose Multiplatform in a single place.
In addition, for the web target, we are focusing on achieving feature parity with other platforms. This includes implementing drag-and-drop support, improving text input and rendering, and ensuring interoperability with HTML page contents. Compose Multiplatform for Desktop, already used in Android Studio and IntelliJ IDEA codebase, will also benefit from adopting newer APIs from Jetpack Compose, along with continuous performance improvements.
Through these initiatives, we aim to make Compose Multiplatform the best choice for building applications, allowing you to support any platform with just a single line of configuration.
Tooling
We remain committed to delivering an excellent development experience for Kotlin Multiplatform. Our goal is to reduce the need for developers to switch between different IDEs, offering a seamless and integrated workflow across platforms.
We aim to ensure that Kotlin Multiplatform integrates seamlessly with the IDEs commonly used for KMP development, such as IntelliJ IDEA and Android Studio, making it more straightforward to share business logic or UIs.
While we continue to prioritize strong KMP support for all existing platforms, we also believe there’s a place for a dedicated IDE. With this in mind, we are working towards the public release of a standalone KMP IDE. This IDE, based on JetBrains Fleet, will be tailored specifically for Kotlin Multiplatform development, offering an optimized, all-in-one environment. With this release, we focus on mobile scenarios and aim to:
- Ensure that developers no longer need to switch between different IDEs.
- Provide enhanced language support, delivering an equally great experience in both Kotlin and Swift, with a focus on seamless interoperability between the two.
- Create a unified and simplified workflow that helps developers with experience in either iOS or Android to feel confident and productive when working with both platforms, offering clarity and consistency.
Looking ahead, we are also exploring new areas to enhance the development experience:
- Investigating the possibility of building apps for iOS platforms using cloud machines, which could help developers who don’t have access to Apple devices.
- Exploring deeper integration with AI tools to assist not only in code generation but also in solving more complex development tasks, improving efficiency across the board.
Kotlin-to-Swift export
We are progressing rapidly with the direct Kotlin-to-Swift export. In 2024, we laid the foundation of the architecture and are now iterating to support more Kotlin features. Our current goal for 2025 is to release the first public version. This initial release aims to provide a user experience comparable to the existing Objective-C export, while overcoming the constraints of Objective-C. This will enable broader Swift language support and facilitate more seamless API exporting, paving the way for future improvements that will fully leverage the advantages of exporting to Swift.
You can track our progress on YouTrack or join the discussions in the #swift-export channel in our public Slack.
Library ecosystem
As the Kotlin Multiplatform ecosystem rapidly expands, ensuring the backward compatibility of libraries becomes crucial. To achieve this, the JetBrains team and library creators must collaborate closely. Here’s what we plan to do:
- Improve the klib format to allow library creators to leverage their knowledge of building JVM libraries.
- Implement the same code-inlining behavior in Kotlin Multiplatform libraries as for the JVM.
- Provide a tool that ensures your multiplatform library public API remains compatible.
We’re also looking to improve the publishing process for Kotlin Multiplatform libraries, which includes:
- Providing templates and comprehensive guidelines for creating and publishing KMP libraries.
- Stabilizing klib cross-compilation on different platforms.
- Launching a fully re-designed KMP library publication process.
- Significantly improving the libraries documentation process.
Even though Kotlin Multiplatform is now Stable, we’re still planning significant updates. But don’t worry: Libraries built with the current format will still work with newer Kotlin versions.
Search for multiplatform libraries on the web
We are currently working on simplifying the search process for multiplatform libraries on the web. The library ecosystem is rapidly growing; there are now around 2,500 Kotlin Multiplatform libraries available. However, despite the extensive selection, it can often be challenging for developers to find libraries that meet their specific needs and support their chosen platforms.
Our goal is to introduce a solution that facilitates the discovery of these libraries and allows developers to try them out easily, enhancing their overall experience within the Kotlin Multiplatform ecosystem. We’ll share more details about this initiative throughout the year, so stay tuned!
Amper
Amper, an experimental project configuration and build tool by JetBrains, has received positive feedback from early adopters, along with valuable bug reports, blockers, use cases, and feature requests. We appreciate this input, as it really helps us refine the scope and improve the product.
In 2025, we’ll be focusing on making Amper fully suitable for multiplatform mobile app development for Android and iOS, complete with shared Compose Multiplatform UI. This includes:
- Running and testing applications (locally, on physical devices, and on CI).
- Signing applications and publishing them on Google Play and App Store.
- Numerous IDE features to ensure a smooth and enjoyable experience.
We’ll also explore scenarios around server-side development, such as projects that include a backend for the mobile application with shared business logic.
You can follow the posts on the Amper blog to keep up-to-date with our latest releases and join the discussion in the #amper channel on the Kotlinlang Slack.
Gradle and other build tools
As we look ahead to 2025, our work on Gradle enhancements is outlined in the Kotlin roadmap. Here are some key areas we will be working on:
- Support for declaring Kotlin Multiplatform dependencies at the project level. This will make it easier for developers to manage their project dependencies effectively.
- Improving integration of the Kotlin/Native toolchain into Gradle.
- Implementing the next-generation distribution format for multiplatform libraries. This initiative can simplify the dependencies model and publication layout for multiplatform libraries, making them easier to use with third-party build tools and reducing complexity for library authors.
- Providing full support for Kotlin Multiplatform in Declarative Gradle. Our work on the Experimental Kotlin Ecosystem Plugin, which supports Declarative Gradle, aims to help developers explore a declarative approach to their Gradle builds.
We’re also working on support for Gradle project isolation, publicly available API references for the Kotlin Gradle Plugin, and other initiatives. You can read about our other projects in the detailed Kotlin roadmap document.
Further reading
Subscribe to Kotlin Blog updates
