compose-recomposition-optimizer

Fix unnecessary recompositions by making parameter types stable with @Immutable or @Stable annotations, using ImmutableList instead of List, remembering captured lambdas, and deferring state reads with lambda parameters. Measure first with Layout Inspector or compiler metrics before changing code.

Add metricsDestination and reportsDestination to the composeCompiler block in your module's build.gradle.kts, then run assembleRelease. The output includes classes and composables reports showing which classes are unstable and which composables are not skippable.

LazyColumn recomposes all items when items lack stable keys. Provide a unique, stable key parameter for each item so Compose can track identity across list changes and skip unchanged items.

Strong Skipping Mode in Kotlin 2.0+ skips composables based on equality even with unstable types, but only when the composable does not capture unstable lambdas. Verify it is enabled in compiler options and still fix genuinely unstable types.

Use derivedStateOf only when the input state changes more often than the output, such as deriving a boolean from scroll position. For simple one-to-one transforms it adds overhead without reducing recompositions.

Do not optimize without measurement evidence such as frame drops, Layout Inspector recomposition counts, or profiler data. Compose performance intuition is often wrong, and premature optimization wastes effort on screens that already render fine.