Streaming a response changes your UI contract, not just your latency
Partial output means every intermediate state is user-visible, including the wrong ones.
All posts
clickable does six things, and detectTapGestures does one
Modifier.clickable adds accessibility semantics, focus, keyboard activation, ripple and a minimum touch target on top of tap detection. Reaching for detectTapGestures instead silently drops all of it.
Two agents, one working directory, and a merge nobody asked for
Parallel agents editing one checkout interleave their changes. Isolation costs disk, not correctness.
Every gesture in Compose is a coroutine reading a stream of events
pointerInput gives you a coroutine scope over raw pointer events. Understanding that gestures are suspending loops rather than callbacks explains the whole API, including why the key parameter matters more than it looks.
Your prompt is a config file, and it needs the same discipline
Untracked prompt edits are untracked behaviour changes.
Automated checks find the missing labels. They can't tell you the label is wrong.
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.
The interface with one implementation, and the three years it cost
An abstraction written for a second implementation that never arrived is pure indirection.
The architecture decision nobody wrote down, re-litigated four times
Without the rejected options and the reason, every new engineer re-opens the question.
We shipped it, measured it, and deleted it eleven weeks later
Deciding the success metric before building is what makes deletion possible afterwards.
Engagement went up, and it was because the app got slower
Time-in-app rose because loading took longer. A metric that improves under a regression is measuring the wrong thing.
Reading order is layout order, until your layout stops matching your meaning
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.
One card, four announcements — merging is the fix
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.