testing-compose-in-release-mode
skydoves/compose-performance-skills / measurement/testing-compose-in-release-mode
measures Compose performance in release builds , which improves: avoids figures skewed by debug mode
Details
- judge’s score
- 9/10
- place
- extra · Android
- publisher
- skydoves
- status
- new
- pinned commit
- 1b32f81 on GitHub (new tab)
- skill’s last commit
- Apr 29, 2026
- repo stars
- 516
- main type
- Android
Judgement
Precise triggering and real pitfalls (debug, Live Literals, CompilationMode.None), concrete commands. Point removed for unsourced claims (75%/60% gains, ComposerImpl devirtualization) and references to missing annexes.
reservations
- Four related skills cited (configuring-r8-for-compose, generating-baseline-profiles, diagnosing-compose-stability, tracing-recompositions-at-runtime) were not provided: their content cannot be verified.
- The quantified gains (about 75% on startup, 60% on rendering) are attributed to a source that was not verified; the R8 mechanisms described (ComposerImpl devirtualization, constant folding) are asserted without evidence.
- The skill mixes several APIs whose validity depends on the version (legacy liveLiterals vs featureFlags); the reportsDestination example is not connected to the reporting flow described.
- Triggering
- 2/2
- Added value
- 2/2
- Precision
- 2/2
- Scope
- 2/2
- Quality
- 1/2
Alerts
no alerts
Neither the static scan nor the judge flagged a risk for this skill.
Original description
Use this skill to ensure Jetpack Compose performance numbers reflect production reality by measuring against a release variant with R8 enabled, Live Literals disabled, and Compose Compiler reports read from the release output directory. Covers why debug builds lie (interpreted Compose runtime, JIT w…
added on Oct 19, 2026 · license Apache-2.0