Kotlin Multiplatform 2024 roadmap released


  • Share on Pinterest

UIBuzz Podcast

In this episode, I will dive into the recently released Kotlin multiplatform roadmap for 2024 by JetBrains.

This roadmap outlines their plans to enhance the stability, performance, and accessibility of Kotlin's multiplatform capabilities. So, let's jump right in and explore what's in store for this exciting development platform.

Stability and Adoption

The JetBrains team emphasizes the stability of the Kotlin multiplatform, making it an ideal choice for development teams worldwide. Now, teams can seamlessly and confidently adopt Kotlin for production. If you've been waiting for the perfect time to dive into Kotlin, now is the time!

Compose Multiplatform

One key focus for the JetBrains team is the Compose multiplatform framework. With its stability achieved, the next step is to ensure optimal performance. Currently, a new beta version of Compose for iOS is available for testing. JetBrains plans to make all Jetpack Compose core APIs and components multiplatform, streamlining the development process for cross-platform projects.

Creating Native-Like Experiences

To ensure a seamless user experience, JetBrains aims to make scrolling and text editing in Compose for iOS apps behave similarly to iOS native apps. By implementing common APIs, developers can easily share all types of resources across platforms. Accessibility features for iOS and desktop platforms will also be prioritized to ensure inclusivity for all users.

Navigation and Orientation Handling

Multiplatform navigation is another area of focus for JetBrains. They aim to provide a consistent and natural navigation experience across different platforms. Additionally, the roadmap mentions simplifying the porting of existing apps to new platforms, such as WebAssembly. This will enable developers to reuse common code and avoid repetitive tasks.

Input Handling and Tooling

JetBrains acknowledges the importance of touch screens, keyboards, and mice in modern development. They aim to ensure that input handling works seamlessly across platforms, making it effortless for developers to create user-friendly interfaces. As for tooling, JetBrains' extensive suite of IDEs and tools, including Kotlin support and the Fleet tool, will continue to be compatible with Kotlin multiplatform projects. Live previews in tools will also be a focus, allowing developers to see real-time updates within their preferred development environment.

Kotlin to Swift Export

A notable initiative on the roadmap is the Kotlin to Swift export feature. This will streamline collaboration between Swift and Kotlin developers, allowing them to work seamlessly together on cross-platform projects. JetBrains is committed to improving compilation speed, an ongoing concern for developers of all platforms.

CocoaPods Integration and Swift Package Manager

To enhance the integration of Kotlin multiplatform projects with iOS ecosystems, JetBrains plans to enhance CocoaPods integration. This will enable developers to integrate third-party libraries and dependencies into their projects efficiently.

Swift Package Manager support will also be improved, facilitating smoother collaboration between Kotlin and Swift developers.

KLIB Format and Cross-Platform Libraries

JetBrains recognizes the importance of libraries in software development and aims to improve support for the KLIB format. Leveraging libraries helps reduce code repetition and promotes productivity. Moreover, building and publishing KMP libraries without a Mac will ensure accessibility to developers on Windows and Linux machines.

The Kotlin multiplatform is rapidly maturing, gaining support from numerous communities. JetBrains' 2024 roadmap outlines its plans to enhance stability, performance, and accessibility across platforms.

The Compose multiplatform framework, expanded core APIs, and consistent user experiences are just some exciting changes coming to Kotlin next year.

Thank you for reading, and don't forget to share this blog post with your developer friends.

Note: This blog post is based on a script from the UIBuzz Podcast.

The original script has been edited and expanded for a comprehensive blog post.