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
Compose's accessibility checks catch touch targets, contrast and missing labels automatically. The failures they cannot detect — wrong labels, bad order, gesture-only actions — need a person, and knowing the split makes both cheaper.
An abstraction written for a second implementation that never arrived is pure indirection.
Without the rejected options and the reason, every new engineer re-opens the question.
Deciding the success metric before building is what makes deletion possible afterwards.
Time-in-app rose because loading took longer. A metric that improves under a regression is measuring the wrong thing.
Screen readers traverse in layout order, which breaks when a floating action button, a sticky header or a two-column layout puts visual priority somewhere else. Traversal groups and indices reorder without moving anything.
A composite component produces one semantics node per child by default, so a card becomes four swipes. mergeDescendants, clearAndSetSemantics and invisibleToUser control the shape of the tree.
A mutex held for microseconds is fine. Held across an unbounded wait, it serialises your service.
A flag that gates the new path but not the data migration is not a kill switch.
Every Compose UI produces a semantics tree alongside the layout tree. It's what screen readers read, what tests query, and what autofill inspects — so getting it right serves three audiences at once.
Config bypasses code review, CI, canaries and rollback. It changes behaviour just as much.
Ten rows locally, ten thousand in production. The query count scales with data.
