With KMM still in Alpha, how do you convince a tea...

# multiplatform

[chi]

With KMM still in Alpha, how do you convince a team that doesn't use Alpha libraries that KMM's alpha is different from the average alpha framework? (not just pointing them to other big team companies that has KMM in production).

More like, how reliable is KMM's alpha state?

[uli]

Well, it still has lots of rough edges. It is still not performance optimized. And makes it really hard to do any sensible multi threading.

Investing the resources you save through code sharing you might eventually come to a stable app with no more budget then it would take to develop two independent apps and then Jetbrains will have its new memory model ready and you have a terribly outdated codebase with lots of workarounds for wired limitations that no developer of the future will ever (want to) understand.

[uli]

Just for the records 🙂 Don’t get me wrong. I am a big fan of KMM:
https://dev.to/s2engineers/the-future-of-cross-platform-development-kotlin-multiplatform-35n8

[Sam]

Well, it still has lots of rough edges. It is still not performance optimized. And makes it really hard to do any sensible multi threading.

That’s Kotlin Native. KMM is mostly a gradle plugin with some compiler tie-ins. Agreed on K/N being early days still. It works but you has some limitations. I do feel that it is the best way to share code between platforms without having to resort to C++ or Javascript.