Jetpack Compose 1.13 lands with computedStateOf, recomposition tracing, and captured exit animations
These additions remove two common sources of wasted composition and memory in real apps, and the new tracing gives teams the exact state write behind any recomposition head-scratcher. None of it changes your architecture or build setup, so upgrading is low-risk and pays off where lists, dialogs, and condition-driven UI get messy.
Jetpack Compose 1.13 ships with BOM 2026.11.01, requires Kotlin 2.2+ and compileSdk 37.1, and brings Material 3 to 1.5.0 stable. The release focuses on practical tooling rather than headline features: a new computedStateOf API avoids result caching for cheap boolean conditions, an official runtime-tracing module links Perfetto records to specific state writes, LazyLayoutCacheWindow unifies list prefetch and off-screen retention, and CapturedAnimatedVisibility captures a frame so content can exit after its state is cleared.
A worked music-list example shows the new APIs cooperating: scrolling determines when the back-to-top button appears, opening and closing a track detail clears the selected song, and the exit animation no longer blocks on stale data. The post also covers progressive blur, PolygonShape and MorphPolygonShape for clips and shape animation, deprecation of Compose ConstraintLayout and MotionLayout in favor of stable FlexBox and Grid, and the removal of Modifier.onFocusedBoundsChanged.
Google's own Pokedex benchmarks on Pixel 6 show Compose 1.13 is roughly flat versus 1.12.1: TTID 147.65 ms (3.4% faster than Views), TTFD 202.79 ms (12.5% slower than Views), and zero dropped frames in scrolling. The release is a practical convergence that developers can adopt without major rewrites.
Google's performance numbers show the framework's runtime cost is not dropping much, but the workflow payoff is real: recomposition tracing and computedStateOf attack the most common cause of UI jank modeling mistakes on Android, not just frame rates.
CapturedAnimatedVisibility changes a core Compose contract, accepting a static exit frame. That trade is sensible for most exit animations, but it quietly caps what an exit transition can do, so teams with animated content in their leaving views need to test before adopting.
The deliberate split between computedStateOf and derivedStateOf pushes more design onto the developer; choosing correctly depends on knowing whether the computation is cheap enough to redo on every read. That kind of decision is now a documented API choice rather than an implementation detail.
The recommendation to deprecate ConstraintLayout and MotionLayout in Compose while pushing FlexBox and Grid signals Google is shrinking Compose's layout surface toward modern web-like primitives; teams with heavy ConstraintLayout usage should plan a migration path now.