← Back to gallery

Compose Compiler Metrics

Stability and skippability reports for every @Composable in Aurum. Regenerated from the Compose compiler on every merge to main, so this page is always in sync with what just shipped.

Aurum library

Stability & skippability of every public composable in the :aurum module.

View report →

Aurum Catalog

Same report for the :aurum-catalog showcase app — catches demo-screen regressions.

View report →
What to look for. A composable marked restartable + skippable can safely avoid recomposition when its inputs haven't changed — that's the efficient state. A composable marked non-skippable recomposes whenever its parent does, even when its parameters are effectively unchanged. The usual cause is an unstable parameter type (e.g. raw List<T> instead of ImmutableList<T>). When a PR regresses a previously-skippable composable, the detekt Compose ruleset typically flags the root cause before these metrics are even needed; if it slips through, the PR's compose-metrics GitHub Actions artifact shows the diff.