Can someone explain to me the different use cases for Kotlin Multiplatform and Kotlin Multiplatform mobile? Reading through the KMM website, it seems to me that all the advantages listed also apply to the regular Kotlin Multiplatform.
We are a small company and are looking to be able to re-use as much code as possible. The proposal I’ve set forth for my teammates is such:
1) We will use Kotlin Multiplatform to create a library (and eventually an sdk) to contain all of our shared business logic.
2) We will then create a flutter plugin to wrap the multiplatform library, which could be imported into our flutter projects, so we can again write our UIs with a single code base.
The reason we’re doing this instead of just creating the library in pure Flutter is that we will eventually turn it into an SDK so that other companies can use it to make apps for their platform of choice. And since the core library would be made with Kotlin Multiplatform that would be possible. (we will continue making our UIs in Flutter since we have experience with it already and to again share code)
I’ve successfully created a proof of concept covering the two points above using Kotlin Multiplatform Mobile + Flutter plugin, however, once we start the real work, I’m wondering if it would be better to use the regular Kotlin Multiplatform. After all, if it will generate a JS library for free as we develop, why not?