Hello, everyone. I have an unusual question. What is the disadvantages or restrictions of Kotlin Multiplatform. Maybe you planned to use this approach but during implementation faced some troubles or problems? Or maybe you just know other side ( or sides ) of this technology? I am asking because I used it for three projects, but my experience is positive. I want to present this technique in my company and start using it. But I almost sure that question about disadvantages will be asked, I know that they exist, but I am not aware of them.

The main issue I've run into is the lack of reflection support on all platforms aside from JVM. It can be worked around, though, so long as you start the project with a reflectionless approach in mind.

Hi. technology have interop with native stack so all restrictions is workaround by implement functionality on native side. And our experience is also positive...see at https://blog.usejournal.com/the-dos-and-donts-of-mobile-development-with-kotlin-multiplatform-db7c098545c0 https://blog.usejournal.com/the-dos-and-donts-of-mobile-development-with-kotlin-multiplatform-part-ii-d318dae8475b

The most of the friction is from iOS team. Their concerns are: 1. learning curve (Kotlin + Gradle + IDEA), 2. If a module crashes on iOS only then who's responsible to fix? 3. Kotlin Native is not stable at the moment

Distributing resource files in compiled libraries is not possible. Developers should learn differences of multithreading on every platform.

The biggest concern for me is the lack of Multi-threaded Coroutines on Kotlin/Native. This is a major hole in concurrency/coroutine support for Native targets including iOS, right now: https://github.com/Kotlin/kotlinx.coroutines/issues/462

@alex009 thanks for the articles, really helpful