Certificate pinning has no shared implementation, and should not
Each engine pins through its own trust machinery, and one cannot pin at all.
Engineering
Compose, Kotlin, and multiplatform work — the mechanism under the symptom.
296 posts
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.
The Compose compiler version is not independent of your Kotlin version
A Kotlin bump without the matching plugin fails at a position no trace explains.
composeResources qualifiers are not Android's, and the fallback differs
A qualifier Android resolves may have no equivalent on iOS or the web.
A Compose UI test in commonTest runs five times and fails on one
The clock, the input source and the available fonts differ per target.
Compose for web loads a runtime before it draws anything
First paint waits on a wasm binary and a font, which no mobile profile shows.
Four crash reporters, one shared module, and the traces nobody could read
The reporting SDK is platform code and the crash is in shared code.
A deep link is four platform integrations wearing one URL
Verified, registered and delivered differently; parsing is the easy part.