Jetpack Compose 1.12 gives Android teams a broad stable upgrade
Google has made the Jetpack Compose August '26 release stable, bringing version 1.12 across core Compose modules and pointing developers to the Compose BOM version 2026.08.00 as the supported upgrade path. The announcement was published by Nick Butcher, Product Manager for Jetpack Compose, on the Android Developers Blog on August 12, 2026.
This is a practical release rather than a single-feature headline. Google highlights graphics APIs, layout work, platform integration, testing improvements, and performance work in one update. For teams already using Compose, that makes the release important because it touches design systems, text editing, authentication flows, gesture-driven animation, and test stability.
What changed
On the visual side, Compose 1.12 adds MeshGradientPainter for multi-point gradients and enables Wide Color Gamut and HDR rendering support across Compose graphics, paint, and shaders. Google says non-sRGB color spaces such as Display P3 can be preserved through platform rendering, while unsupported color spaces or older Android versions fall back safely.
The release also adds named areas to the experimental Grid component. Instead of placing items only by numeric row and column coordinates, developers can define semantic areas such as header, sidebar, and content. That should make dashboard-style and adaptive layouts easier to read and maintain, especially in larger apps.
For text and input, Compose 1.12 adds rich-text formatting APIs for BasicTextField, programmatic text selection through SelectionState, and a Credential Manager integration path through semantics. Google also notes that BasicSecureTextField now uses the system text obfuscation mode by default.
Animation and runtime work are also part of the release. DeferredTargetAnimation has graduated out of experimental status, while new DeferredAnimatedContent and DeferredAnimatedVisibility composables are aimed at two-stage transitions such as predictive-back gesture tracking. Google also added keyed SideEffect overloads for cases where a one-shot side effect should run when specific keys change, with a caution that migration order matters because SideEffect runs before DisposableEffect and LaunchedEffect.
The migration detail developers should check first
The breaking-change section matters. Compose 1.12 updates compileSdk to API 37 and requires at least Android Gradle Plugin 9.1.1, according to Google's post. Teams planning the upgrade should confirm their build toolchain before treating the new BOM as a routine dependency bump.
Google's Compose BOM documentation explains why the BOM is the recommended way to manage Compose dependencies: it lets developers specify one BOM version while the individual Compose libraries remain compatible with that tested set. The BOM mapping page also shows core Compose artifacts, including animation and foundation, mapped to 1.12.0 for the current stable set.
Why it matters
For app teams, the most useful part of Compose 1.12 may be the spread of smaller operational improvements. Better visual primitives help design teams implement richer interfaces without jumping into lower-level rendering code. Named grid areas make complex layouts more maintainable. Rich text and selection APIs reduce friction for document, messaging, note-taking, and productivity apps. Credential Manager integration can also help sign-in flows feel more native when developers wire it correctly.
Testing changes are another practical area. Compose 1.12 introduces hasPendingWork and runWithoutImplicitWait to reduce wasted synchronization when tests manually sample animation state. That does not remove the need for good test design, but it gives teams more precise control over a class of Compose UI tests that can otherwise become slow or flaky.
Google also says this release continues startup-performance work and reports Time to Initial Display comparable to Views in its own benchmarks. That is a source-specific benchmark claim, not a guarantee for every app. Real results will still depend on an app's architecture, startup path, baseline profiles, rendering load, and device mix.
What to watch next
The upgrade path is clear: review the AGP and compileSdk requirements, move to Compose BOM 2026.08.00, and test UI behavior across graphics, text, animation, and authentication flows that use the changed APIs. Teams using experimental Grid, custom text editors, or predictive-back animations have the most immediate reasons to evaluate the release.
The broader signal is that Compose is still expanding beyond declarative UI basics into more complete application surfaces. The August '26 release gives Android developers more stable building blocks, but the safest adoption path is still deliberate: update the toolchain first, isolate high-risk UI flows, and verify behavior with app-specific tests.