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 gradients take pixel coordinates, so a hardcoded end point produces a different result on every screen size. Float.POSITIVE_INFINITY and DrawScope.size are the two ways to make a brush relative.
A metric answers a question you already had. The difference is cardinality.
An alert that fires daily has trained everyone to ignore it, which is worse than no alert.
Painter draws content and declares an intrinsic size, which is what lets it participate in layout the way a resource does. Writing one is the right answer when drawing needs to be reusable across Image, Icon and modifiers.
Somebody is grepping your log line, matching on your message, or alerting on its text.
A test coupled to call order and internal structure fails when nothing is broken.
ImageVector is drawing commands executed at render time; ImageBitmap is pixels held in memory. The choice is about scaling fidelity versus per-frame cost, and the common mistakes run in both directions.
A column drop is irreversible the moment it runs. Expand-contract exists because deploys and migrations do not move together.
Synchronised retries from every client are a self-inflicted thundering herd. Jitter is the mechanism, not a detail.
One measurement pass means a child cannot ask its parent how big it is.
Image sizing depends on the modifier constraints and contentScale together. Understanding which one crops, which one fits, and where the aspect ratio comes from resolves most image layout bugs in one pass.
It is scoped to a composition and keyed by its arguments. A missing key gives stale state; a wrong one recomputes every frame.
