using-strong-skipping-correctly

Strong Skipping Mode in Jetpack Compose modifies how restartable composables are memoized and how capturing lambdas are remembered, changing when composables skip or recompose. It requires auditing lambda captures to ensure they are stable or hoisted with remember.

To verify Strong Skipping is active, check your Kotlin and Compose plugin versions and inspect the project configuration for any opt-out flags or legacy settings. Perform an initial audit on a sample composable to confirm the expected skipping behavior.

Strong Skipping does not memoize lambdas in gaps such as LazyListScope.items, Modifier.pointerInput, object expressions, and non-@Composable scopes. Engineers must identify these sites and apply escape hatches or hoist state to ensure correct recomposition behavior.

You can apply escape hatches like @DontMemoize, @NonSkippableComposable, @NonRestartableComposable, and @ReadOnlyComposable to control composable memoization. Use these annotations with proper rationale to prevent unwanted skipping or enforce recomposition where needed.

Validate recomposition behavior at runtime using @TraceRecomposition to observe when composables skip or restart. Establish CI stability checks to guard against regressions, ensuring any unintended changes to memoization or lambda captures are caught by CI.