Android Dev Summit 2026 brought more than new APIs: it shifted how Google recommends building UI, state and navigation. The upcoming stable Compose 1.13 adds Grid and FlexBox, Navigation 3 1.2 is already stable, and Jetpack AppState in alpha moves Compose's state model into the architecture layer. Here is what to build into a project now and what to simply watch.

What was announced

ComponentStatusWhat it gives you
Jetpack Compose 1.13Upcoming stable releaseGrid and FlexBox, Progressive Blur, Formatted Text, recomposition tracing
BasicTextFieldRewritten (according to Google)Buffer-driven architecture, TextFieldState, no IME race conditions
Navigation 3 1.2StableType-safe deep links, richer Predictive back
Jetpack AppStateAlphaTransform and StateStore: reactive state beyond the UI

Adaptive layouts: Grid and FlexBox

Google calls Compose the standard for all UI on Android and the reasoning is simple: one approach instead of fragmented codebases for phones, foldables, tablets, wearables, cars, XR and Googlebook. In Compose 1.13, built-in adaptive layout support through Grid and FlexBox moves to stable. Together with Navigation 3 and WindowManager, it is the foundation for multi-pane interfaces that rearrange to the window instead of just stretching a phone screen.

If your screens were only ever designed for phones, this is a good moment to revisit them. We covered the practical limits of this approach in our piece on tablet and foldable apps.

Text fields and graphics

Google reports that text editing in Compose is now built on a rewritten BasicTextField with a buffer-driven architecture and TextFieldState. The goal is to remove keyboard (IME) race conditions and support formatted text. For apps with complex forms, chats or editors, it is worth testing separately on real devices and different keyboards, since input bugs are usually the most painful ones.

Compose 1.13 also brings Progressive Blur and Formatted Text, and Google says graphics features such as mesh gradients run without hurting battery or frame rate. Effects are useful, but measure their impact on your own app.

Recomposition tracing: why the UI redraws

Compose 1.13 introduces recomposition tracing. It shows not only which functions recomposed but why, all the way back to the state write that triggered it. Combined with composition tracing in the Android Studio Profiler, it makes unnecessary recompositions easier to find. For coding agents, Google published the jetpack-compose-performance skill, which points them at common performance anti-patterns.

Jetpack AppState: state as part of the architecture

AppState (alpha) brings Compose's snapshot system into the app layer. Transform derives reactive state from State and Flow inputs using automatic read tracking and plain Kotlin control flow. StateStore is a keyed container that shares observable state across activities, background services, widgets and App Functions, optionally persisted through DataStore.

It is an interesting idea for apps where the same state appears on several surfaces: a screen, a widget, a notification, an agent call. But it is alpha, so APIs may change. Our recommendation is to pilot AppState in an isolated module of a non-critical feature rather than rewrite your core with it. For how app layers relate to each other, see our article on MVVM and Clean Architecture.

Navigation 3 works with a back stack that you own. Version 1.2 adds built-in type-safe deep link support: with Kotlin Serialization you can map incoming URIs and intents to strongly typed navigation keys, customize how complex arguments are parsed, and lazily build synthetic back stacks so back navigation feels natural. Google also mentions richer Predictive back handling.

What teams should do

  1. Plan the upgrade to Compose 1.13 once it is stable, and run UI tests and profiling before and after.
  2. Check layouts at different window sizes: folding a foldable, resizing a window or using a tablet must not reset state.
  3. Evaluate Navigation 3 if you are on the previous navigation and plan deep links or multi-pane screens.
  4. Try AppState on an isolated feature and keep alpha APIs off the critical path.
  5. Add Android skills for your agents: Google offers Adaptive, Compose performance, XML to Compose migration and Ink. For choosing between UI approaches, see our comparison of SwiftUI, Compose and classic Views.

Conclusion

The core idea of these updates is that Compose is moving beyond the rendering layer: it becomes the basis for adaptive layouts, text, navigation and state. For new projects, that means designing architecture for multiple form factors from the start instead of adding them at the end.

Sources: Android Developers Blog: Build for every screen with the latest Jetpack Compose updates; Android Developers Blog: Agentic and Flexible: A next era of Android development; Android Developers Blog: What's new in Android developer tools and performance.