On 18 November 2026 stable Jetpack Compose 1.13 shipped (BOM 2026.11.01). It is not only about new effects: the release deprecates several familiar tools and changes how clickable elements behave. Below we go through what to migrate now and what can wait.

All facts below come from the Android Developers Blog post.

Upgrade requirements

Moving to BOM 2026.11.01 requires Kotlin 2.2 or newer and compileSdk 37.1. If a project is still on an older toolchain, start the upgrade there:

implementation(platform("androidx.compose:compose-bom:2026.11.01"))

What is deprecated

WhatWhat changedWhat to move to
Value-based BasicTextField and Material 2 TextFieldOfficially deprecatedState-based BasicTextField with TextFieldState; in Material 3 the value-based overloads are not deprecated yet, but Google recommends migrating
VisualTransformationDeprecatedOutputTransformation and InputTransformation
Compose Material 2Deprecated and no longer actively maintainedMaterial 3 1.5.0
ConstraintLayout and MotionLayout in ComposeDeprecated (the constraintlayout-compose artifact)Modern Compose layout and animation tools, including the Shared Element APIs
Modifier.onFocusedBoundsChangedImplementation removed; the modifier has no effectFocusTargetModifierNode.getFocusedRect(), onFocusChanged, BringIntoViewRequester

Built-in scrolling containers such as LazyColumn and Modifier.verticalScroll already bring focused content into view, so the removed modifier does not affect them.

What was added

  • FlexBox and Grid are stable. FlexBox gained maxItemsInEachLine and, according to Google, supersedes FlowRow and FlowColumn in new code.
  • computedStateOf is a lighter alternative to derivedStateOf for condition checks and filtered state computed from frequently changing values such as scroll position. It does not cache the result, so it has less overhead. Keep derivedStateOf for heavy calculations or where caching is needed.
  • Stable LazyLayoutCacheWindow. Window-based prefetching replaces item-based prefetching in lists, grids and staggered grids; the cache window settings moved from rememberLazyListState into the layout composables themselves.
  • Progressive blur, PolygonShape and MorphPolygonShape. Blur properties can be set directly on DialogProperties.
  • CapturedAnimatedVisibility. It animates a snapshot of the last frame instead of keeping state alive, which helps when data disappears immediately (for example closing a details pane sets the selected item to null). In Google's benchmarks, frame time during exit is 7–8% faster than with AnimatedVisibility.
  • TestFailurePolicy. It automatically saves a screenshot and the semantics tree when a UI test fails, which is handy in CI.
  • Material 3 1.5.0. Experimental annotations dropped from 120 to 58; Slider and RangeSlider moved to SliderState.

Behavior change: click sounds

Elements using Modifier.clickable (and components built on it) now automatically play standard Android interaction sounds, respecting the user's system sound settings. If you previously triggered such sounds manually or deliberately avoided them, check screens with clickable elements after the upgrade.

Performance: what the numbers say

Google states that on a Pixel 6, Compose 1.13 matches version 1.12.1 on baseline startup and scrolling benchmarks with a 0% jank rate. Cold start Time to Initial Display is 147.65 ms for Compose versus 152.87 ms for Views. Views are still faster on Time to Full Display (180.32 ms versus 202.79 ms for Compose), and P50 scrolling frame duration is 3.51 ms for Compose versus 3.06 ms for Views.

On the tooling side there is Perfetto recomposition tracing (recording state reads and writes) and a static analysis performance skill available through Android CLI. Google warns that recomposition tracing adds overhead, so disable it when measuring performance.

Migration plan

  1. Update the toolchain: Kotlin 2.2+ and compileSdk 37.1, then BOM 2026.11.01.
  2. Find deprecated APIs: value-based text fields, ConstraintLayout in Compose, Material 2, onFocusedBoundsChanged.
  3. Start with text fields: moving to TextFieldState changes the state model, so do it as a separate step.
  4. Walk through clickable screens: check the new system sounds.
  5. Measure: compare startup and scrolling before and after on real devices.

Two experimental tracks are worth knowing about: the Styles API remains experimental, and the androidx.web:web:1.0.0-alpha01 library and the A2UI renderer (material3-a2ui:1.0.0-alpha02) are still alpha, so do not plan production work on them.

Conclusion

Compose 1.13 does not break an app out of the box, but it clearly shows what will be removed next: value-based text fields, Material 2 and ConstraintLayout in Compose. It is better to plan the migration across the next sprints than to do it all at once alongside other changes.

Need help migrating a Compose app or an audit of your UI code? Get in touch: we will look at the project and propose a plan.