Publishing a KMP library commits you to every target you listed
Dropping a target in a minor release breaks consumers at resolution time.
All posts
Strong skipping made most of yesterday's advice unnecessary
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.
The compiler decides your types are unstable, and it writes down why
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.
The dependency with one maintainer, and the week it went away
Bus factor is a property of your supply chain, not just your team.
It was not a timezone bug, it was a day-boundary bug
Storing UTC is necessary and not sufficient. Any report bucketed by day needs a declared zone.
The index I added made the query slower, and the planner was right
Low selectivity plus random access beats a sequential scan only sometimes.
Rotating the key was the easy part
A committed secret is public the moment it is pushed. Deleting the line changes nothing.
Compose performance is one question asked in four places
Compose performance work reduces to knowing which of composition, layout and draw is being invalidated, and why. The diagnostic order matters more than any individual optimisation.
Drag-and-drop crosses app boundaries, which is why it isn't just a drag gesture
Compose's drag-and-drop moves ClipData between sources and targets, including across apps. Reordering a list is a different problem with a different solution, and conflating them is why reorder implementations get complicated.
Adding a parameter with a default broke the ABI
Source compatibility and binary compatibility are different guarantees, and a default argument preserves only the first.
Seven modules, seven copies of the same Gradle block
Copy-pasted build config drifts silently per module. A convention plugin makes the shared part shared.
An animation is state, and that is why it restarts
animate*AsState holds its value in the composition. A key change starts it over.