We use Google Analytics to see which pages help people. No ads, no profiles. Privacy Policy
Compose, Kotlin, and multiplatform work — the mechanism under the symptom.
229 posts
Reading a state value later — in a lambda rather than as a parameter — moves the invalidation from composition to layout or draw. It is the single highest-leverage Compose optimisation, and it has one shape.
Window functions replaced a hand-rolled grouping pass. The cost of not learning was paid in code.
If a new engineer cannot get running from the doc in a day, the doc is not the problem.
Baseline Profiles ship a list of hot methods so ART compiles them at install time instead of interpreting them on first run. They typically cut startup and first-scroll jank by 20-30% and are unrelated to Compose recomposition.
Insets, soft-input mode, scroll position and focus order are four systems, and three are configured outside Compose.
Correct code against a wrong spec passes every test.
String routes fail at runtime on a typo or a missing argument. Serializable types move both into the compiler.
Dropping a target in a minor release breaks consumers at resolution time.
Strong skipping lets composables skip even with unstable parameters, using instance comparison, and memoises lambdas automatically. It removes most of the need for @Immutable annotations and changes what the compiler report means.
Compose infers stability per class and per parameter, and can emit a report saying what it concluded. Understanding the inference rules — and why List is unstable — explains most unnecessary recomposition.
Bus factor is a property of your supply chain, not just your team.
Storing UTC is necessary and not sufficient. Any report bucketed by day needs a declared zone.
