What's New in Android 16 for Developers

Android 16 is as much a schedule change as a feature release. Google pulled the major, API-level-bumping release forward into the first half of the year, with a smaller update following later that doesn't ship a new SDK level. The developer-facing headline: large-screen adaptivity stopped being optional.

#A new release rhythm

Starting with Android 16, the annual platform release that bumps targetSdkVersion lands around mid-year instead of the previous autumn timing. A second, minor update arrives later in the year without a new API level.

If your release planning assumed a September/October Android drop, move that expectation. Play's targetSdkVersion deadlines are now anchored to a summer release.

#Orientation and resizability restrictions go away on large screens

Apps targeting API 36 can no longer lock orientation (android:screenOrientation="portrait") or declare themselves non-resizable on large-screen devices — tablets, foldables, ChromeOS. On large screens the OS overrides those manifest restrictions regardless of what the app declares.

An app that assumed portrait-only and never tested layout at other aspect ratios will now actually be shown that way. Real breakage, not a Play Console warning.

@Composable
fun AppRoot(windowSizeClass: WindowSizeClass) {
    when (windowSizeClass.widthSizeClass) {
        WindowWidthSizeClass.Compact -> CompactLayout()
        WindowWidthSizeClass.Medium -> MediumLayout()
        WindowWidthSizeClass.Expanded -> ExpandedLayout()
    }
}

Use it when: your manifest carries an orientation lock or a non-resizable declaration. Once you target API 36 this is no longer a "nice to have later" item — it's the difference between a usable tablet experience and a broken one.

#16 KB page sizes move from optional to required

Android 15 introduced the ability to test against 16 KB memory pages. Android 16 turns that testing curiosity into an enforced requirement for new app submissions with native code.

Rebuild any bundled .so libraries with a current NDK and verify page-size alignment before you ship an update.

#Predictive back is on by default

For apps targeting API 36, the system back gesture uses the predictive back animation by default rather than requiring explicit opt-in. Migrated off onBackPressed() to OnBackInvokedCallback when Android 14 shipped? You get this for free. If you didn't, this is the release where the old behavior visibly diverges from every system surface around your app.

#Progress-centric notifications

Android 16 introduces a notification style aimed at ongoing, glanceable progress — ride-sharing ETAs, food delivery, downloads — surfaced more prominently than a regular progress notification. Treat it as a targeted replacement for a custom progress notification layout, not a general-purpose notification redesign. This surface is newer and still settling, so check the current Notification builder APIs for the exact style class before committing UI work.

#What to adopt first

• Large-screen adaptivity is the priority. Orientation locks and non-resizable declarations stop working the moment you target API 36 — test on a tablet or foldable emulator before you ship, not after.
• 16 KB page alignment is mandatory groundwork if you ship any native libraries, directly or via an SDK. Verify your dependencies have updated; don't assume they have.
• Predictive back is free if you did the Android 14 migration. Still on onBackPressed()? This is the release that makes the gap visible to users.
• Don't rebuild your release calendar around the old autumn cadence — confirm the current targetSdkVersion deadline against Play's published schedule rather than last year's dates.