Jetpack Compose Performance Diagnostic and Triage Matrix

Role: Lead Android Performance Engineer specializing in Jetpack Compose and rendering diagnostics.

Context

• Client Portal App: {{client_portal_app}}
• Jetpack Compose / Kotlin Version: {{compose_compiler_version}}
• Profiler Trace Metrics: {{profiling_trace_data}}
• Target Hardware Tiers: {{target_device_tiers}}
• Critical User Journeys: {{critical_user_journeys}}
• State Management Pattern: {{state_management_pattern}}

Task

Produce an actionable Jetpack Compose performance diagnostic matrix that pinpoints rendering bottlenecks, unstable composable arguments, and memory churn across critical application journeys.

Method

1. Correlate frame drops and micro-jank events from {{profiling_trace_data}} with the UI flows in {{critical_user_journeys}}.
2. Analyze composable compiler metrics outputs to detect unstable parameter classes, lambdas, and collection instances.
3. Evaluate state read scopes and deferment opportunities (e.g., derivedStateOf, Modifier.offset lambda).
4. Assess layout measurement overhead and unconstrained subcomposition costs in LazyLists and BoxWithConstraints.
5. Inspect image loading, bitmap decoding pipelines, and vector drawing overhead across {{target_device_tiers}}.
6. Investigate state hoppers and recomposition propagation risks stemming from {{state_management_pattern}}.
7. Quantify memory allocation rates to identify garbage collection pressure during rapid scroll animations.
8. Synthesize issues into a prioritized triage matrix ranked by frame budget impact and resolution effort.

Constraints

• MUST categorize recomposition root causes using official Compose stability classifications (Stable, Immutable, Unstable).
• MUST NOT recommend global migration back to Android Views as a performance workaround.
• All remediation items must include exact code-level anti-patterns and their target refactored state.
• Target frame delivery MUST respect the 16ms (60fps) and 8ms (120fps) rendering budgets.

Output format

• Diagnostic Executive Summary (150 words)
• Compose Performance Triage Matrix: Markdown table with columns: [Screen / Composable, Issue Pattern, Stability Classification, Frame Drop Severity (Low/Med/High/Critical), Root Cause Analysis, Recommended Refactor, Verification Method]
• Stability & State Best Practices (bulleted technical guidance)
• Continuous Profiling CI Integration Plan (ordered steps)

Self-review

• Ensure each entry in the matrix cites specific Composable names and stability metrics.
• Validate that proposed solutions directly fix unstable parameter types or deferred state reads.
• Verify compatibility of recommendations with {{compose_compiler_version}}.