actual typealias looks like a shortcut and changes what you promised
Aliasing to a platform type exports that type's whole surface to every caller.
kmp
103 posts
The shared module cost 400KB on Android and 11MB on iOS
Android shrinks against a runtime already on the device. iOS links yours in.
Kotlin/Native's memory model changed, and your atomics did not
Freezing is gone, so the bugs it prevented at compile time are runtime bugs now.
There is no shared background work, because three platforms disagree about when
WorkManager schedules under constraints, iOS grants windows, the browser has none.
The biometric prompt belongs to the OS, and it can disappear mid-call
You suspend across a UI the system presents and may destroy without telling you.
Why the build cache helps the JVM target and almost never the native ones
Cache keys for native compilation include the toolchain, so they rarely hit.
Certificate pinning has no shared implementation, and should not
Each engine pins through its own trust machinery, and one cannot pin at all.
A Flow does not cross to Swift. A callback does.
Exporting a Flow hands Swift something it has no way to collect.
Copy and share: two features that are entirely platform code
A gesture requirement, a presenting view controller, and neither on desktop.
CocoaPods or Swift Package Manager: the choice belongs to the iOS team
Each channel constrains your publishing pipeline differently.
Every list you hand to Swift is copied, and the cost is per call
A Kotlin List becomes an NSArray by conversion, not by reference.
commonMain cannot ask which Android version it is running on
A capability check belongs behind an expect, phrased as a capability.