compose-modifier-system

Prevent unnecessary Jetpack Compose recomposition by deferring state reads to the Layout or Drawing phase using lambda overloads like Modifier.offset { ... } and Modifier.graphicsLayer { ... }, ensuring frequently changing values do not force Composition restarts.

Choose drawWithCache when your drawing requires cached expensive objects, drawBehind for simple drawing, and drawWithContent when ordering-sensitive drawing is needed, ensuring correct drawing tier selection for optimal Compose modifier performance.

Migrate from deprecated Modifier.composed by implementing ModifierNodeElement with Modifier.Node, using correct equality semantics and fine-grained invalidation like invalidatePlacement or invalidateDraw to control which phase updates.

Your custom Compose layout measures children twice due to incorrect layout modifier implementation. Prevent this by properly structuring custom layout logic and ensuring pixel-vs-dp correctness in drawing to avoid redundant measurement passes.

Yes, you can control invalidation scope in Compose Modifier.Node by using invalidatePlacement for layout changes and invalidateDraw for drawing updates, ensuring only the necessary frame phase restarts instead of triggering full recomposition.

The best way to handle scroll and animation state in Compose modifiers is to read the state within the Layout or Drawing phase using lambda overloads, and ensure the modifier node invalidates only placement or drawing when its inputs change.