compose-state-deferred-reads

Excessive Compose recomposition occurs when frame-rate state like scroll offsets or animation progress is read during composition instead of the layout or draw phase. Moving these reads into deferred callbacks prevents unnecessary recompositions and layout thrashing.

To defer state reads in Jetpack Compose, move state reads from the composable body into layout or draw phase callbacks. This approach limits recomposition to only when strictly necessary, improving overall render performance.

Back-writing in Jetpack Compose happens when dependent sizes are measured unsafely, causing layout thrashing. You can prevent it by using measure and decorateMeasureConstraints to coordinate measurements safely without triggering frame-time conflicts.

Yes, you can pass scroll, gesture, or animation values across composable boundaries using provider-based value passing. This limits state reads in the composition phase, restricting heavy read operations to the layout or draw phases.

You should move Compose state reads into the layout or draw phase when handling high-frequency frame-rate state such as scroll offsets, animation progress, or gesture states. This prevents these rapidly changing values from triggering expensive recompositions.