when running kmm, where the targets are android and ios, is the output of shared library on android jvm bytecode, or do both platforms get native code?
05/30/2021, 5:44 PM
On Android it's jvm bytecode
05/30/2021, 8:13 PM
so the freeze functions are a no-op there?
interesting, so all those exceptions which come with misuse of freezing, will only manifest in ios at runtime?
05/31/2021, 8:35 AM
Yeah, so what I do is instead of developing for Android and hoping it to work in iOS, I now develop for iOS and hope it works in Android. This has resulted in fewer surprises when running kmm code on iOS.
05/31/2021, 8:22 PM
Oh so I'm gonna force new paradigm on ios team & only let them feel all the bugs 😀 theyre gonna love that (they protested even to install java 😀)
06/01/2021, 8:34 AM
Instead of forcing something, try to come up with common ground. Fortunately in my company, iOS devs were open to the idea of using KMM. The key is to understand the benefits and compromises and decide whats best for your team. It is difficult to get started with KMM as an iOS dev as they have to learn not only a new language but also the IDE and tooling. Sympathise with them.
I’m an Android developer but I always think about iOS devs experience first while writing KMM code so that they can also enjoy working on it. We often get on a call to understand the dev expectations and write code accordingly.
Having said that, as much as I believe in KMP, its much more important to work towards developer happiness and choose tech stack accordingly. 🙂