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
animate*AsState animates toward a target that can change at any moment. Understanding it as declarative rather than imperative explains interruption, redirection, and why spring is the right default.
A List parameter is unstable because the compiler cannot prove it will not change.
Layout measures text to resolve constraints, and a changing style invalidates the cache.
The Compose animation surface looks large because it is organised by what you're animating rather than by how. Three questions pick the right API, and picking wrong is why animation code gets complicated.
A computed value read in composition invalidates on every change of its source. derivedStateOf narrows it to the result.
Hoisting everything to the root means every keystroke recomposes the tree.
A bitmap costs width × height × 4 bytes in memory regardless of its file size. Decoding at display size, choosing the right config and budgeting the cache are what keep an image-heavy app from being reclaimed.
Two weeks means the most likely case. What anyone planning around you needs is the spread.
Forty comments on a pull request is a design disagreement wearing a review costume.
Dead code is not free. It is read, maintained, migrated, and it shapes decisions.
Deciding what counts as the same request is a business question. The key is the easy part.
Drawing custom shapes means Path plus DrawScope. Shadows are separate, and Modifier.shadow takes its own shape parameter — omitting it is why rounded cards get square shadows.
