State hoisting has a limit, and you have probably passed it
Hoisting everything to the root means every keystroke recomposes the tree.
architecture
70 posts
The most valuable pull request that quarter deleted 4,000 lines
Dead code is not free. It is read, maintained, migrated, and it shapes decisions.
Idempotency is a product decision before it is a technical one
Deciding what counts as the same request is a business question. The key is the easy part.
The test that broke on every refactor was testing the wrong thing
A test coupled to call order and internal structure fails when nothing is broken.
LaunchedEffect(Unit) runs once, and that is usually the wrong once
Keyed to Unit means once per composition entry — not once per screen visit, and not once per user.
Image loading is the least portable thing in your shared UI
Decode, cache and memory pressure are platform concerns, and the composable that hides them decides your scroll performance.
A feature flag read on four platforms needs one source of truth and four caches
Flags that differ per platform at the same moment produce bug reports nobody can reproduce.
There is no File in commonMain, and that is a feature
wasm has no filesystem and iOS has a sandbox with policy. An interface forces you to name what you need.
Hashing a password in shared code is the one thing you should not share
Each platform has a vetted crypto provider. A pure-Kotlin implementation has none of their review.
Throwing across the bridge loses your exception type
Swift sees NSError with a wrapped message, so a typed catch becomes a string match.
There is no UUID in the Kotlin standard library, and the fixes differ per platform
Random is seeded differently per target and is not secure anywhere. An id generator is a security decision.
The desktop target is the cheapest bug oracle you are not using
It builds in seconds, runs real Compose, and needs no device.