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
Multi-touch gestures produce pan, zoom and rotation simultaneously. The centroid — the point between the fingers — is what makes the transform feel anchored, and ignoring it is the most common photo-viewer bug.
Proving the process is running keeps a broken instance in the load balancer.
An unbounded buffer converts a throughput problem into an out-of-memory crash.
Hand-rolled swipe gestures compare a distance threshold and ignore velocity, which is why a fast flick feels wrong. AnchoredDraggableState models discrete positions and settles between them using both distance and speed.
An insert on page 1 shifts every later offset. A keyset cursor is data, not a position.
At-least-once is the contract every provider offers. Your handler is where exactly-once gets built.
Quantisation, mmap and the low-memory killer decide whether your 3B model ships.
Partial output means every intermediate state is user-visible, including the wrong ones.
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.
Parallel agents editing one checkout interleave their changes. Isolation costs disk, not correctness.
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.
Untracked prompt edits are untracked behaviour changes.
