Shared navigation state and the one platform that kills your process
A back stack in memory is correct on desktop and loses the user's place on Android.
Engineering
Compose, Kotlin, and multiplatform work — the mechanism under the symptom.
296 posts
Compose is growing a styles API, and it's for the gap theming never covered
MaterialTheme scopes values to a subtree, which is the wrong shape for reusable per-component configuration. Compose's styles direction addresses that gap; wrapper composables are the pattern to use today.
One notification API, four delivery systems that behave differently
Channels, categories, a service worker and a tray have different rules.
One shared call, five targets, three different strings
Locale-aware formatting is implemented per platform, and the outputs differ.
Two Kotlin classes, one Objective-C name, and a header that will not compile
Objective-C has no namespaces, so two same-named classes export as one.
The shared analytics event that meant something different on each platform
Each SDK truncates names, coerces types and limits parameters differently.
Two feature modules that needed each other, and the type that fixed it
A direct dependency between siblings is a cycle waiting for the third one.
There is no shared permission API, and the lifecycles disagree
Android can be asked twice; iOS once; the browser needs a gesture.
Preferences on five targets: what each one actually persists to
Four stores with different durability, size limits and clearing behaviour.
R8 stripped a reflective call that only the shared module made
Shrinking runs on one target, so a reflection path ships broken there.
Remote config defaults that disagreed, and the feature that shipped twice
The fetched value is shared and the fallback is per platform.
Room compiles for KMP and still needs a driver per target
The DAO is shared and the connection is not.