:rocket: <https://blog.jetbrains.com/kotlin/2025/0...

# announcements

[Alina Dolgikh [JB]]

🚀 What’s Next for Kotlin Multiplatform and Compose Multiplatform 🚀

We’ve recently published a new blog post outlining our priorities and the direction for Kotlin Multiplatform and Compose Multiplatform.

Explore our plans for the next six to twelve months and see where the journey is headed.

👉 Read the full blog post 👈

[Stefan Oltmann]

Great to see that iOS build speeds made it into the roadmap. 🙂
JetBrains is really listening to its community. 💪

[Stephane Robin]

Would love to see Kotlin for serverless, is there plan on that ?

[Stefan Oltmann]

There is a great third party library for Kotlin/Native AWS Lambdas and AWS is transforming their tools to Kotlin/Native right now, too. On that front things are already moving.

But Cloudflare could need support. They don’t have a Kotlin strategy and it’s painful to write Cloudflare Workers with Kotlin.

[Stefan Oltmann]

Maybe look in #C01AAJSG3V4 for questions and discussions about the roadmap & priorities.

[Emiel Bon]

@Stefan Oltmann What's the library?

[Stefan Oltmann]

https://github.com/trueangle/kotlin-native-aws-lambda-runtime

[Emiel Bon]

Thanks!

[Stefan Oltmann]

You are welcome. 🙂
If you need a sample: https://github.com/StefanOltmann/steam-login-helper

[Joel Denke]

So much great stuff! I did notice swift export on the roadmap, I wonder is there also support for spm or swift library import improvements as well?

[Emil Flach]

We are definitely considering SPM support, but do not have a specific plan yet. By the next update I'd hope to have more clarity here. Please upvote and leave a comment for your use case on the related ticket.

Swift Import is a more complex topic that we do not have any plans for at the moment. However, we are always interested in knowing how you would use it and again I would ask for your comments on the related ticket.

[Joel Denke]

Yeah getting SPM or true Apple package system support is whats killing me try do iOS support in CMP. That including Apples own swift libraries, some included but a lot isnt. Its these kind of things would make Gradle/CMP a killer machine I think. Ofc also important in same topic for library owners export.
Stuff being painful today is Firebase and Google play services. But also more pure iOS swift integrations. This also make it hard for library owners integrate iOS targets into KMP not being able get the best from iOS.

[Stefan Oltmann]

I just stick to good old XCFrameworks for the the being; that works best for me.

[Emil Flach]

Thank you, I made an internal note on your perspective.

[Steyn Geldenhuys]

Awesome points on the roadmap, but curious to read the section on Compose Web going to beta and reading "we expect to see pioneers starting to ship small- to medium-sized apps to production".
We've been shipping Kotlin WasmJs apps to production for a couple of months already. 😉

[Stefan Oltmann]

I like how cautious JetBrains is here. Most alphas are already stable enough to be used with confidence in production.
Compare that with Apple, where a "Beta" is more like JetBrains "experimental" stage. 😬

[Steyn Geldenhuys]

Yeah, we often use alpha stage libraries from Jetbrains in production. Typically hold off on Kotlin and Compose libraries and plugins releases until RC, but usually by the time we ship to production they are already stable.

[Stefan Oltmann]

I got lucky, too, with libs going stable (or beta) in the mean time. For my pet projects I don't care that much - if it works, it works. 😉

[Liliia]

Yeah, we often use alpha stage libraries from Jetbrains in production.

How do you cope with the risk that a breaking change may arrive at any release? 🙂

[Stephane Robin]

@Stefan Oltmann when i'm talking about Kotlin for serverless, it's more cloud provider agnostic, i don't plan to use AWS only. Currently i would love to deploy on Digital Ocean for exemple.

[Steyn Geldenhuys]

@Liliia typically we use alpha libraries for good reasons, like the lifecyle libraries, navigation and adaptive in compose because we need the features. And now compose 1.9.0-RC and kotlin 2.2.20-RC2 because we want the new web compatibility mode. To answer your question, we have a policy in our dev teams, when you touch a project update everything to latest and deal with the breaking changes now - don't wait for the breaking changes to add up.

[Anton Yalyshev [JB]]

@Stephane Robin for the upcoming months we don’t plan to anything specific for serverless. It works, in general, and people share their different solution for this platform, e.g.

https://www.youtube.com/watch?v=6jZa4B-If-I▾

But please, share what you would like us to do there 🙂

[Stephane Robin]

Will look at ti thanks @Anton Yalyshev [JB]