StateFlow drops what you needed and keeps what you didn't
Conflation turns two identical emissions into one, so a repeated event vanishes.
architecture
98 posts
One failed child cancelled the whole screen, and the scope was the reason
Structured concurrency propagates failure upward by design. SupervisorJob is how you declare independence.
Your dependency graph has six entry points and one of them runs twice
Application.onCreate, a Swift app init, a main function and a page load each start the graph. Two inits on one platform is a duplicate-definition crash at the worst moment.
appleMain exists only if your targets justify it
The hierarchy template inserts nodes based on declared targets. A directory for a node that does not exist compiles nowhere and warns about nothing.
Dispatchers.Main throws on a target you forgot to configure
Main is supplied by a platform integration, so it exists on Android and iOS and fails at runtime on desktop tests — a crash whose message names a module, not a mistake.
We shared 60% of the code and one platform used all of it
Measured per target rather than per line: the iOS app reached a third of the shared surface because the API was shaped around Android's lifecycle.
The transaction that was atomic on Android and not on the web
Nested transactions, savepoints and write locking vary per driver. Code written against one driver's guarantees loses them silently on another.
commonTest runs on every target, which is the point and the cost
One test, five executions. That is how you find platform bugs — and how one flaky test fails five jobs.
kotlinx-datetime has no Calendar, and the timezone database ships per platform
Instant is unambiguous. LocalDateTime is not. The same arithmetic can disagree across targets.
expect/actual is not an interface, and the difference shows up at link time
An interface is resolved at runtime by an instance. expect/actual is resolved at compile time by the source set.
The iOS framework you export is an API, and nobody reviews it
Every public declaration in the shared module becomes Swift API. internal is the design tool.
Your shared database needs a driver per platform, and that is the easy half
The driver is a one-line expect/actual. Threading, file location, and the OS deleting your file are the rest of it.