Skip to content
Theme
OnDevice Tools

AndroidAndroid OS

Jetpack Compose 1.13 adds blur, polygons and text field changes

The stable Jetpack Compose 1.13 release adds progressive blur, polygon shapes, Material 3 updates and state-based text fields. It also deprecates older text field APIs and Material 2.

Illustration of Jetpack Compose 1.13 showing blur, polygon shapes and text field changes

Key takeaways

  • Jetpack Compose 1.13 is stable and uses Compose BOM 2026.11.01.
  • The release adds progressive blur, polygon shapes and dialog or popup blur controls.
  • Compose Material 3 1.5.0 is stable, while Material 2 is deprecated and receives no active maintenance.
  • Value-based BasicTextField and Material 2 TextField are deprecated in favour of state-based text fields.
In this article
  1. Release details and graphics
  2. Material 3 and text fields
  3. Performance and text layout
  4. What developers should do next

Release details and graphics

According to the Android Developers Blog, Jetpack Compose 1.13 is stable in a post dated 18 November 2026. The release covers core Compose modules and updates text, graphics, layouts and performance. It also includes deprecations and behaviour changes.

The post says projects should use Compose BOM version 2026.11.01, the version bundle. The upgrade needs Kotlin 2.2 or later, plus the build requirement compileSdk 37.1.

One graphics addition is progressive blur, which lets an element move from sharp to blurred. It uses Modifier.blur and BlurRadiusSpec. Developers can choose linear gradients, radial gradients or custom AGSL RuntimeShaders. The blog says this can blend a header image into a background or create a touch spotlight.

Compose 1.13 also adds PolygonShape and MorphPolygonShape to androidx.compose.foundation:foundation. PolygonShape works with Modifier.clip and component shape parameters. It matches the layout size automatically. MorphPolygonShape changes between two polygon shapes using a progress lambda during drawing, and foundation already includes graphics-shapes.

Dialog and popup blur controls are expanded. DialogProperties now accepts blurBehindRadius, backgroundBlurRadius, scrimAlpha and windowShape. PopupProperties accepts blurBehindRadius and scrimAlpha. WindowInfo.isCrossWindowBlurEnabled can query system cross-window blur state.

Material 3 and text fields

Compose Material 3 version 1.5.0 is also stable, with Slider and RangeSlider moving to a stateful model using SliderState. New components include ToggleButtons, WavyProgressIndicators and TimePickers. BottomAppBar, TopAppBar variants and BasicAlertDialog have moved to stable. The release adds a material3-ripple artefact with inset focus rings.

The blog says experimental annotations fell by 52 percent, from 120 to 58. It says Material 2 is deprecated and receives no active maintenance. The post recommends moving to Material 3 for bug fixes and the current Android design language.

Text fields are a major change: the post deprecates value-based BasicTextField and Material 2 TextField. It directs developers to state-based BasicTextField and TextFieldState APIs, where TextFieldState holds the text state. Material 3 value-based TextField overloads are not deprecated yet in 1.5.0. The blog still recommends state-based TextField and OutlinedTextField overloads.

TextFieldState can save and restore formatted styles. The release removes experimental annotations from undo/redo history and change tracking buffers. VisualTransformation is deprecated. The post points to OutputTransformation and InputTransformation as alternatives, including built-in length-limit filters.

Performance and text layout

Compose 1.13 makes static icon rendering more efficient. VectorPainter can share and reuse rasterised draw caches for the same static ImageVector size and configuration. This reduces repeated bitmap allocation and rasterisation. The behaviour is enabled by default through ComposeUiFlags.isVectorDrawCacheSharingEnabled, and developers can improve caching by reusing ImageVector instances.

Modifier.border has a faster implementation. It supports runtime shaders through ShaderBrush with a RuntimeShader across all shape types. It also uses the outline size consistently when drawing borders.

For multilingual text, LineHeightStyle.Mode.PerLine calculates line height for each line. This helps tall scripts such as Burmese, Khmer or Thai avoid collisions with adjacent lines. FontVariation.Settings gains merge overloads for base variable font settings. Developers can override axes such as weight, slant or width without rebuilding the list.

The post also describes a Jetpack Compose performance static analysis skill. It provides code auditing and generation across seven areas. These include state stability, lazy layouts, layout code, graphics, animation, effects and threading, and Modifier.Node migrations. The blog says checks can run on a pull request, file or screen through the Android CLI.

What developers should do next

Illustration: code, star, performance, Jetpack Compose logo and the labels Android, Jetpack Compose, Kotlin

Teams using Compose should review the BOM and toolchain requirements before upgrading. The move to Compose BOM 2026.11.01 needs Kotlin 2.2 or later, plus the build requirement compileSdk 37.1.

Teams still using Material 2 should plan a migration to Material 3. The blog says Material 2 is deprecated and receives no active maintenance. Material 3 is the path for current bug fixes and design updates.

Apps that use value-based text fields should inspect the state-based APIs. The post says TextFieldState offers synchronous state, improved performance and support for saving formatted styles. Teams that rely on VisualTransformation should review OutputTransformation and InputTransformation.

Developers using custom drawing, dialogs or popups should review the new blur and shape options. The blog points to Android Dev Summit 2026 talks for more detail on graphics, text fields, performance and behaviour changes.

Sources

  1. What's new in the Jetpack Compose November '26 releaseAndroid Developers Blog

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.