deferring-state-reads

Move the state read out of the composable body into a lambda modifier such as Modifier.graphicsLayer { alpha = value } or Modifier.offset { IntOffset(x, 0) }. The lambda reads state during Layout or Draw, so Composition is never invalidated per frame.

Modifier.offset(x: Dp) reads its value in the Composition phase, invalidating the whole subtree when the value changes. Modifier.offset { IntOffset } reads in the Layout phase, so only re-placement occurs and Composition is skipped.

No, Modifier.padding ships only value-based overloads, so it always reads in Composition. For animated insets driven by hot state, use a custom Modifier.layout { measurable, constraints -> ... } block instead.

Use Modifier.drawBehind for simple per-frame drawing like a solid animated color. Use Modifier.drawWithCache when the work involves rebuildable resources such as paths, brushes, or gradients, since it caches the build step and only re-runs onDraw on state change.

Avoid them when state changes only once per user interaction, or when the state decides which composable to emit, since lambda modifiers cannot change the emitted tree. Also diagnose stability issues first if the parent is non-skippable due to unstable parameters.

A wrong-phase read likely survived elsewhere in the file; re-grep for .value and by state in composable bodies. Also confirm measurements on a release build with R8 on a real device, since debug builds run interpreted and misrepresent cost.