The talk dives into why recomposition occurs, how to identify it, and when to optimize and when not to. Knowing when your composable doesn't need optimization is equally important.
The topic will cover how to use annotations like @Stable @Immutable, @NonRestartableComposable, and @ReadOnlyComposable, and other practices like state hoisting, remembered lambda, and delayed lambda calls. Once the developers generate the compose report based on it, they can decide which composable needs optimization and where it's not required. Talk will also include a demo, including incorporating all the practices, and a result matrix


Developers takeaways :

Compose Stability and Recomposition rules.

A checklist that will help you decide when to optimize.

How to generate a composable report, how to read and make use of it.

Measure the result using the recomposition counter and macrobenchmarking.

Sample code with before/after version.