Peng Jiang

Jetpack Compose’s reactive model relies on composition scopes, state reads, and the ability to skip recomposition when inputs remain stable. In large-scale apps, common pitfalls-like unstable parameters types, misused annotations, mutable domain models and captured lambdas can break this optimization, which causes your UI unnecessarily recomposed, even when nothing has changed. In this 40-minute session, you’ll learn: 1. How the composer's core model of composition -> snapshot read -> scope invalidation drives reactive rendering. 2. How Kotlin’s compiler and compose’s runtime collaborate to track state access, parameter stability, and when to skip recomposistion–including the roles of annotations, data model structures, and compiler flags. 3. How to identify instability faster using the new compose API in 1.9 and proactivity prevent recomposition leaks in your codebase. 4. A practical checklist of stability traps and fixes, drawn from real-world patterns observed at scales.