Accueil / Apps & Logiciels / What’s new in the Jetpack Compose November ’26 release

What’s new in the Jetpack Compose November ’26 release

The Jetpack Compose November ‘26 release is stable! This release brings version 1.13 across core Compose modules (see the full BOM mapping), introducing updates to text, graphics, layouts, performance, and more—along with a few important deprecations and behavior changes to be aware of.

To update your project to this release, upgrade your Compose BOM version to 2026.11.01. Note that this upgrade requires Kotlin 2.2 (or newer) and compileSdk 37.1.

We continue to add many new graphics features into Compose. Compose 1.13 introduced polygon shapes, progressive blur, and the ability to configure blur properties directly on Dialogs and Popups.

Jetpack Compose 1.13 introduces progressive blur, letting you transition elements from sharp to blurred seamlessly. Progressive blur is built on a draw-phase lambda using Modifier.blur { … } and BlurRadiusSpec. You can implement linear gradients (such as vertical or horizontal transitions), radial gradients for focal spotlight effects, or even pass custom AGSL RuntimeShaders to drive dynamic, procedural blur maps.

Whether you're blending the bottom edge of a header image into a background using BlurredEdgeTreatment.Unbounded, or tracking touch coordinates with a radial spotlight, progressive blurs make premium, tactile depth-of-field effects incredibly straightforward to implement on Android.

Compose 1.13 adds PolygonShape and MorphPolygonShape to androidx.compose.foundation:foundation. Until now, rounded polygons, stars, and shape morphing in Compose required using androidx.graphics:graphics-shapes directly — adding the dependency, creating a RoundedPolygon at the right pixel size, converting it to a Path, and writing your own Shape to fit it to the layout bounds.

PolygonShape is a regular Compose Shape, so it works with Modifier.clip or any component's shape parameter, and it resolves to the layout size automatically. MorphPolygonShape animates between two polygon shapes by reading a progress lambda at draw time, without recomposition. Use graphics-shapes directly only when you're outside Compose UI or need the raw RoundedPolygon geometry. You don’t need to add graphics-shapes to use PolygonShape, as foundation already depends on it.

You can now configure blurBehindRadius, backgroundBlurRadius, scrimAlpha, and windowShape (to clip dialog background blurs to rounded corners) directly on DialogProperties (and blurBehindRadius/scrimAlpha on PopupProperties). You can also query system cross-window blur state via WindowInfo.isCrossWindowBlurEnabled.

In Compose 1.13, rendering static icons is more efficient. VectorPainter automatically shares and reuses rasterized draw caches across painters rendering the same static ImageVector at the same size and configuration, eliminating redundant bitmap allocations and rasterization. To maximize caching, reuse ImageVector instances across composition instead of recreating them. This optimization is enabled by default via ComposeUiFlags.isVectorDrawCacheSharingEnabled.

Modifier.border now features a faster, more performant implementation, adds support for runtime shaders (ShaderBrush with a RuntimeShader) across all shape types, and consistently uses the outline size when rendering borders.

To learn more about all the new graphics features in Compose and on the Android Platform, check out the talk from Android Dev Summit 2026:

Compose Material 3 version 1.5.0 is now stable and introduces the following:

In this release, we cut experimental annotations by 52 percent—dropping from 120 down to 58. We've also graduated almost every new expressive component to stable. As Material 3 enters its sixth year of availability, the Compose Material 2 library is deprecated and no longer actively maintained. We recommend migrating from Material 2 to Material 3 to get the latest bug fixes and design language for Android. Upgrade your dependencies to Material 3 1.5.0 today to bring these new expressive components to your apps. Learn more about all the new components, performance updates, and behavior changes in the blog post.

The value-based BasicTextField and Material 2 TextField are officially deprecated. This shift directs you to transition to the more robust state-based BasicTextField and TextFieldState APIs.

If you're using Material 3, your existing value-based TextField overloads are not deprecated yet in 1.5.0, but we recommend migrating to the state-based TextField and OutlinedTextField overloads to take full advantage of synchronous state, improved performance, and upcoming features. If you are still on Material 2, migrate directly to Material 3's state-based text fields.

By migrating to TextFieldState, which natively supports saving and restoring formatted styles, you gain improved, out-of-the-box performance and a safer, synchronous state model. This release also removes experimental annotations from undo/redo history and change tracking buffers. Legacy utilities like VisualTransformation are deprecated in this release, making way for streamlined alternatives like OutputTransformation and InputTransformation, including its built-in length-limit filters.

To learn more about how to migrate to state-based text fields, check out this talk from Android Dev Summit 2026:

When displaying multilingual text or mixed font sizes within a single paragraph, uniform line spacing can cause tall scripts (such as Burmese, Khmer, or Thai) to collide with adjacent lines. Compose 1.13 introduces LineHeightStyle.Mode.PerLine, which calculates line height independently for each line. This allows lines with taller glyphs or larger spans to dynamically expand to fit their natural bounds without clipping or disrupting the rest of the paragraph.

Compose 1.13 adds merge overloads to FontVariation.Settings, making it easy to define base variable font configurations and dynamically override specific axes (like weight, slant, or width) without re-allocating or rebuilding the entire settings list.

We’ve added a new Jetpack Compose performance static analysis skill that provides zero-setup code auditing and generation across seven key categories—state and stability, lazy layouts, layouts, graphics, animation, effects and threading, and Modifier.Node migrations—allowing you to run standalone checks on any PR, file, or screen to comply with current best practices. Try it out today through the Android CLI!

A new mechanism for state computation, computedStateOf, has been introduced in 1.13. It provides a lightweight alternative to derivedStateOf, and is intended for condition checks and filtered state calculated from other frequently-changing states (like scroll position and animation thresholds). By not caching calculation results, it has less overhead than derivedStateOf—especially when the calculation is invalidated by one of its referenced states changing.

Both state variations invalidate composition when the result of the calculation changes, not when their input states change. They are commonly applied to convert frequently changing states into infrequently changing states, preventing invalidations in your composition hierarchy for unimpactful state changes. You should reserve derivedStateOf for heavy calculations or where caching is otherwise necessary. In general, we recommend using computedStateOf instead of derivedStateOf for state computation.

Recomposition tracing is a new way to augment existing composition tracing with new information about state reads and state writes, providing you with a full overview of the state changes that caused recompositions. For each read and write affecting composition, it records the state’s string representation and stack trace to pinpoint the exact line of code where the change occurred.

Note that recording additional data for recomposition tracing adds overhead, so make sure to disable it when investigating your app’s performance.

Compose 1.13 matches Compose 1.12.1 across all our baseline startup and scrolling benchmarks with a 0% jank rate on Pixel 6. On cold startups, Compose 1.13 still achieves a faster Time to Initial Display (147.65 ms) than Views (152.87 ms)

Views remain faster on Time to Full Display (180.32 ms versus 202.79 ms for Compose) due to differences in data flow starts and GPU shader work. Scrolling frame duration (P50) sits at 3.51 ms for Compose compared to 3.06 ms for Views, with overall performance remaining stable and consistent across valid test runs. We continue to invest heavily in improving performance across all performance metrics, with a focus on startup metrics. For the full results, check out the documentation.

To learn more about performance, check out the talk from Android Dev Summit 2026:

FlexBox and Grid layouts (announced in Compose 1.11) are officially graduating from experimental to stable. These APIs are production-ready, highly performant alternatives for wrapped grids and responsive designs. FlexBox also gains a new configuration maxItemsInEachLine that lets you limit the number of items in a line when wrapping is enabled.

Origine de l’article : lire l’article original

Traduction