Google Releases Jetpack Compose 1.13 Stable
Compose 1.13 adds stable FlexBox and Grid layouts, new shape APIs, and progressive blur as part of the November 2026 Compose Bill of Materials.
Updated on Nov. 19, 2026 in Software

Google released Jetpack Compose 1.13 on November 18, 2026, alongside stable Material 3 version 1.5.0. The release makes FlexBox and Grid stable, which were previously experimental.
Why it matters
Developers building Android apps can adopt the stable release by updating their Compose BOM to 2026.11.01. Google's move to deprecate Material 2 and the value-based BasicTextField signals that codebases will need migration work.
Benchmarks on a Pixel 6 show Compose cold start reaching initial display in 147.65 ms versus 152.87 ms for Views, while Compose's median scrolling frame measured 3.51 ms against 3.06 ms for Views. Results on other hardware were not reported in the source data.
The players
Google is the technology company that develops Android and the Jetpack libraries, including Jetpack Compose, its modern declarative UI toolkit for Android.
The details
Compose 1.13 adds progressive blur, PolygonShape and MorphPolygonShape APIs, and stable FlexBox and Grid layouts, with Google recommending FlexBox over FlowRow and FlowColumn for new development. CapturedAnimatedVisibility captures the last visible frame when content is hidden, and exit-animation frame times improved by 7-8%.
Timeline
November 18, 2026: Jetpack Compose 1.13 and Material 3 1.5.0 released as stable.
November 2026: Compose Bill of Materials 2026.11.01 published.
The Tech Race
Compose 1.13 extends the multi-year transition from the legacy View-based Android UI toolkit to declarative Compose, now benchmarked directly against Views on cold start and scrolling. Google's deprecation of Material 2 and the Material 2 TextField API continues that shift toward a single modern design system.
Developers who update to the 2026.11.01 Compose BOM gain stable FlexBox and Grid layouts, but existing apps will not automatically migrate from Material 2 to Material 3. Teams should plan migration work for deprecated TextField and BasicTextField APIs.
The takeaway
Developers should audit their Compose code for deprecated Material 2 and BasicTextField usage before upgrading. Adopting the stable FlexBox and Grid APIs can reduce reliance on experimental layouts in new projects.
Further reading
Explore more Software coverage for context on developer tools and frameworks.
Source note: This article includes information reported by Techgenyz.



