A platform bridge is an interface with a lifetime problem
Permissions, biometrics and share sheets all need something shared code does not have: a host that outlives the call.
kmp
103 posts
kotlinx.serialization is compile-time, which is why your polymorphism fails at runtime
No reflection on Native, so the serializer is generated. Sealed hierarchies work; open polymorphism needs a module you register by hand.
Your suspend function becomes a callback in Swift, and cancellation does not survive
Swift cancels its Task. The Kotlin Job never hears about it, so the work keeps running.
Wasm has no threads, and that decides your dispatcher
Dispatchers.Default is a single thread in the browser. Code that was merely slow on Android becomes a frozen tab.
An agent drove a KMP app to the Play Store. The codegen was the easy half.
Autonomous codegen produces an app that compiles; what makes it one that ships is a gate stack refusing any claim that carries no evidence.
Core ML and LiteRT solve the same problem differently
A platform-native runtime and a portable one differ in ways the type system will not catch. What the shared declaration may promise is the whole design.
One inference API, two platform runtimes
Designing an expect/actual seam so platform differences stay on one side. What the shared declaration must not promise, and where the abstraction leaks.