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.
architecture
98 posts
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.
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.
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.
shareIn's replay count is a product decision, not a tuning knob
replay = 1 re-delivers the last value to every new collector.
Source sets are a graph, and iosMain is not where you think it is
The default hierarchy creates intermediate source sets you never declared.
A SQLDelight migration is a contract with every installed version
Migrations run forward from whatever version the device holds.