Diferir las lecturas de estado

Every place you read a Compose state value becomes a subscriber. When that state changes, every reader recomposes.

The nearest enclosing Composable that reads a state is its recomposition scope. Read high up, and a lot redraws together.

If you read state deeper, only that small Composable recomposes. Pushing the read down shrinks how much work happens.

Pass a lambda that returns the value instead of the value itself. The read then happens later, inside a narrower scope.

The lambda offset reads scroll position during layout, not composition, so animating it skips recomposition entirely.

derivedStateOf recomputes only when its result truly changes, so a frequently changing source updates readers far less often.

Without derivedStateOf, a button reading raw scroll redraws on every pixel. With it, the button recomposes only when the boolean flips.

Reading state in a parent just to pass it down forces the parent and all siblings to recompose. Pass the state object instead.

Hand a child the whole State object and let it read inside itself. The parent stays stable while the child updates alone.

In a LazyColumn, deferred reads keep scroll updates from re-running item content, so long lists stay buttery smooth.

The core habit is simple: delay the moment you read state until the smallest possible scope needs it.

Read state in the smallest scope, use lambda modifiers and derivedStateOf, and pass State objects down to keep redraws tiny. ✅