compose-performance

What problem does it solve?

Compose performance issues in Android UIs, including frequent recompositions, heavy work in the composition phase, and inefficient list rendering, which degrade smoothness and energy efficiency.

Core Features & Use Cases

• Remember vs rememberSaveable: Guidance on state survival across configuration changes and process death, and best practices for transient vs persistent state.
• derivedStateOf and correct recomposition minimization: Use cases to derive values without triggering frequent recomposition.
• LaunchedEffect keys and lifecycle: Proper key usage to restart effects only when dependencies change.
• Modifier stability and hoisting: Hoist stable modifiers and avoid per-composition allocations.
• LazyColumn optimization: Use keys and contentType to enable slot reuse and efficient rendering.
• Offload heavy work to ViewModels: Move expensive computations away from composables.
• AnimatedVisibility and transitions: Prefer AnimatedVisibility for enter/exit animations to reduce manual animation work.
• Anti-patterns and refactors: Common mistakes and recommended fixes.

Quick Start

Analyze a composable screen for recomposition hotspots and apply the above patterns to improve frame stability and responsiveness.