@ianlake.bsky.social
Android Toolkit Developer and Runner Also at: - https://androiddev.social/@ianlake - https://twitter.com/ianhlake
Good catch! That means it has been even longer since the last stable release, wow.
I guess you get 2 releases worth of fixes in one 😅
There were a lot of other releases this week including Compose 1.10.0-beta02 (with a lot of retain API changes), DataStore 1.2.0-rc01, and Wear Compose 1.5.5 so definitely check out all of release notes for the details!
developer.android.com/jetpack/andr...
In other Navigation news, Navigation3 hits its 1.0.0-rc01 this week, which means we're almost to the first stable release!
This is the perfect time to test it out one more time and make sure everything is working for what you need!
developer.android.com/jetpack/andr...
Navigation 2.9.6 expands some of the work done in the last bug fix release in modernizing our AGP support. That includes no longer needing to set useAndroidX to true on AGP 9.0.0-alpha04 and higher.
developer.android.com/jetpack/andr...
The Core SplashScreen 1.2.0 release improves the support for day/night themes and includes better support for cutouts and navigation bar constrast, which should help it mesh better with your regular theme.
developer.android.com/jetpack/andr...
The first #JetpackReleaseNotes of November include SplashScreen 1.2.0, SavedState 1.4.0, Navigation 2.9.6, RC releases in Navigation3, NavigationEvent, Activity, and Lifecycle and Compose 1.10.0-beta02.
developer.android.com/jetpack/andr...
That was fast! @donaldturner.bsky.social's really nice talk about Navigation 3 at #dcldn25 available now www.youtube.com/watch?v=j1Oi...
31.10.2025 23:59 — 👍 17 🔁 2 💬 0 📌 0But I would suggest filing an issue against Navigation3: issuetracker.google.com/issues/new?c...
Maybe this would be a lot easier if there was a more structured API between an OverlayScene and NavDisplay to support overlay windows that don't know how to animate themselves out.
So the 'correct' solution is to have Popup support exit animations (which, unlike Dialog, could actually be driven by Compose animations).
As a workaround though? You do have another location to hoist composables that need to live longer than the Scene - at your rememberPopupSceneStrategy() level.
If you look at what Compose's Dialog does, it respects the window animations and animates the Dialog out when it is removed from composition. So the Scene leaves composition, but the Dialog still animates.
Compose's Popup though? Just removes the window immediately: cs.android.com/androidx/pla...
There were a lot of other releases this week including Camera 1.6.0-alpha01 (new infrastructure, CameraPresenceListener), Media3 1.9.0-alpha01 (CompositionPlayer, media3-inspector), and PDF 1.0.0-alpha11 (custom selection menu items) and more.
Get the details:
developer.android.com/jetpack/andr...
Activity 1.12.0-beta01 is out with a behavior change on how system back is handled - the Lifecycle aware OnBackPressed APIs now enable/disable callbacks rather than register/unregister them, ensuring a more consistent ordering.
Let us know if you are impacted!
developer.android.com/jetpack/andr...
DataStore 1.2.0-beta01 is out, bringing API stability to DataStore's support for Direct Boot mode and GuavaDataStore.
Note that this release also includes an important fix to DataStore's proguard rules if you aren't using the android-proguard-optimize.txt file!
developer.android.com/jetpack/andr...
Navigation3 reaches API stability this week with the 1.0.0-beta01 release! There's a few important bug fixes in this release as well, but this beta means we're only a few weeks away from rc01 and then stable!
If you run into any issues, please let us know ASAP
developer.android.com/jetpack/andr...
Compose Material3 Adaptive reached their 1.2.0 stable release this week with two new layout strategies - reflow and levitate.
Check out their blog post from their beta release for more details!
android-developers.googleblog.com/2025/09/unfo...
WorkManager 2.11.0 raises the minSdk from 21 to 23. That change meant that the team could remove 3,739 lines of code and the AlarmManager based scheduler used to support older versions of Android. Welcome to a leaner WorkManager!
developer.android.com/jetpack/andr...
This week's #JetpackReleaseNotes include Work manager 2.11.0, Compose Material3 Adaptive 1.2.0, Graphics 1.1.0, bug fixes in Compose 1.9.4, Wear Compose 1.5.4, and Room 2.8.3 plus beta01 releases of Navigation3 (🎉), Lifecycle, Activity, DataStore, and Compose.
developer.android.com/jetpack/andr...
Are you talking about the import statements themselves? Because no one looks at those - in fact, many developers use 'star imports' which collapse them down to just one line for an entire package
If instead you mean, it is unclear what to import when looking at the list of suggestions, that's valid
There's a lot more building blocks in Compose vs canned pre-built components (although quite a few of the Material3 components are close to that).
Was there particular things you felt like had a lot of boiler plate?
Take a look at how we do metadata in NavDisplay, etc. - that title { } example is exactly the kind of type safe API you write for your specific use case.
15.10.2025 18:36 — 👍 1 🔁 0 💬 0 📌 0But I think your example is putting information at the wrong level - titles shouldn't be a property on keys in your back stack at all. Scenes don't even have access to the key classes!
Instead, you should be looking at NavEntry metadata, which lets you write metadata = title { stringResource(..) }
The generics on your Scene need to match the generics on your NavDisplay, which I assume would be AppNav (although I'm not sure why you'd want an empty interface when NavKey already exists), so doing Scene<SubsettingNav> doesn't make much sense.
15.10.2025 16:40 — 👍 2 🔁 0 💬 1 📌 0
There's also a Compose Multiplatform version of the nav3-recipes repository: github.com/terrakok/nav...
14.10.2025 23:34 — 👍 6 🔁 1 💬 0 📌 0
There were a lot of other releases this week including NavigationEvent 1.0.0-beta01 (API stability!), SavedState 1.4.0-beta01, and Ink 1.0.0-alpha07 so make sure to read through all of the release notes for the details!
developer.android.com/jetpack/andr...
Navigation3 1.0.0-alpha11 makes a significant number of API changes: onBack no longer takes a count, Scene's have their own metadata to allow their own defaults/overrides of the NavEntry metadata, plus changes to the Scene and Decorator APIs.
developer.android.com/jetpack/andr...
Compose Material3 Adaptive 1.3.0-alpha01 is out with improvements around edge-to-edge. This release is also the first main release to include the adaptive-navigation3 artifact (which previously only had separate 1.0.0 alpha releases).
developer.android.com/jetpack/andr...
Compose 1.10.0-alpha05 is out with two very welcome changes:
- The Shared Element APIs are now stable! developer.android.com/jetpack/andr...
- PaddingValues now support addition and subtraction! developer.android.com/jetpack/andr...
Metrics 1.0.0 is now stable! Its JankStats APIs are all about measuring UI 'jank' and allowing you to add context to what is going on in your app, making it possible to correlate jank with specific problems areas in your app.
developer.android.com/jetpack/andr...
This week's #JetpackReleaseNotes include Metrics (aka 'JankStats') 1.0.0, Heifwriter 1.1.0, Health Connect 1.1.0, bug fixes in Camera 1.5.1, Compose 1.9.3, Room 2.8.2, and Wear Compose 1.5.3 plus lots of changes in Navigation3 1.0.0-alpha11.
developer.android.com/jetpack/andr...
That, along with synthetic back stacks and different handling whether you are on your own task stack or another apps' task stack (which is the only time when back and up differ), is going to be the next PR after this first one.
10.10.2025 21:25 — 👍 4 🔁 1 💬 0 📌 0
