OOmnistu

Blog / Engineering Playbooks

Engineering Playbooks

Android 15's Edge-to-Edge Enforcement, Explained: What Changes When You Target API 35

When edge-to-edge applies (Android 15 devices, apps targeting API 35), what changes in the system bars, and the inset work that follows - per Android's own behavior-change documentation.

OOmnistu
Reviewed 2026-11-19 · 3 min read

If your app targets Android 15 (API level 35), it is edge-to-edge by default on devices running Android 15 or higher - your layout draws behind the status bar, caption bar and navigation bar whether you planned for it or not. Apps that were not already edge-to-edge can find parts of their UI obscured, and the fix is inset handling, not a manifest flag.

What the enforcement actually does

Android's behavior-changes documentation states the condition pair plainly: apps are edge-to-edge by default on devices running Android 15 if the app targets Android 15 (API level 35). Two UI areas change as a result. With gesture navigation, the navigation bar is transparent by default, the bottom offset is disabled so content draws behind it unless insets are applied, and setNavigationBarColor and R.attr#navigationBarColor are deprecated and have no effect on gesture navigation. With 3-button navigation, the bar is set to 80% opacity by default, content likewise draws behind it unless insets are applied, and setNavigationBarContrastEnforced is true by default, which adds a translucent scrim.

The work it creates

Google's own guidance is that portions of a non-edge-to-edge app may be obscured and that you must handle insets - with the caveat that the work may or may not be significant, depending on the app. The Material 3 Scaffold component can reduce the work required to be compatible with the enforcement. For apps that want edge-to-edge on older Android versions too, calling WindowCompat.enableEdgeToEdge() in your Activity's onCreate enables it backward-compatibly; by default it makes the system bars transparent, except in 3-button navigation mode where the navigation bar gets a translucent scrim.

How your bars should behave

Google's layout guidance is explicit about what an edge-to-edge app should look like: a top app bar should stretch to the top edge of the screen and display behind the status bar (optionally shrinking to the height of the status bar when content scrolls), and a bottom app bar or bottom navigation bar should stretch to the bottom edge and display behind the navigation bar - otherwise, apps should show scrolling content behind the navigation bar. Some of your views may end up drawing behind the system bars, which is exactly what the insets APIs exist to correct, and Google suggests considering scrims behind the system bars where legibility suffers.

When transparency is not what you want

The defaults do not fit every layout. To create translucent system bars instead, Google's guide directs you to update your androidx-core dependency to 1.16.0-beta01 or higher, wrap your XML layout in androidx.core.view.insets.ProtectionLayout, and set protections programmatically, specifying the side and a GradientProtection for the status bar. For a transparent status bar with 3-button navigation, set Window.setNavigationBarContrastEnforced to false, otherwise a translucent scrim is applied.

Edge-to-edge moves system-bar styling from a theme concern into a layout responsibility: the bars are part of your canvas once you target API 35 on Android 15 devices, and inset handling is how you keep your content out from under them.

Sources

Prepared with AI assistance and reviewed before publication. The enforcement conditions, system-bar defaults and API deprecations are drawn from the Android documentation pages above, checked on 19 November 2026.