Limiting risk
Because Kotlin multiplatform projects don't share both logic and UI across build targets, it becomes easier to integrate Kotlin multiplatform modules within an existing project. The shared code can simply be consumed as if it were any other dependency. It also means that a new Kotlin multiplatform application is still going to rely on familiar native tools and tech stacks in at least the UI layer.
All of these things together lead to lower the risk of adopting Kotlin multiplatform when compared to a more heavy-handed cross-platform approach such as React Native or Flutter. In a Kotlin multiplatform code base, if a shared component is not performant enough, it can't wrap a native API properly, or if it has any other issue, it ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access