validating-compose-stability

You can catch Jetpack Compose stability regressions by comparing current compilation output against a committed stability baseline file. This setup fails CI builds when composables become unskippable or parameters lose stability before merging.

Unnecessary Jetpack Compose recompositions occur when composable parameters lose stability, like modifying a previously stable data class. Validating stability against a committed baseline catches these accidental regressions before code is merged.

To generate a Compose stability baseline file, you run the stability dump command after compiling your Android project. This creates a reviewable baseline to track the stability contract of your UI components for future CI comparisons.

Yes, the Compose Stability Analyzer Gradle plugin integrates with existing CI/CD pipelines for Android projects. It enforces build-time quality gates by validating current compilation output against your configured stability baseline file.

A Compose stability baseline is used to maintain a reviewable contract of your UI components' stability. By comparing current compilation output against this file, CI pipelines automatically detect when composables become unskippable or parameters lose stability.

You should enforce Compose stability checks in CI/CD pipelines before merging code. This prevents performance regressions by catching accidental changes where stable data class parameters are modified to become unstable, avoiding unnecessary recompositions in production.