Android 15 is supposed to force apps to go edge-to-edge, but Google quietly added a way to opt out

Though Android has lengthy supplied apps the flexibility to make use of your telephone’s total display by letting them draw content material beneath the standing and navigation bars, many apps don’t reap the benefits of this. There are numerous explanation why builders have shied away from making their apps go edge-to-edge, however within the upcoming Android 15 replace, they’ll don’t have any alternative however to take action — or a minimum of, that’s what we thought.

For a little bit of context, apps have lengthy been capable of go edge-to-edge by implementing a number of APIs that tells the OS to attract the app beneath the 2 “system bars” (ie. the standing and navigation bars). The rationale that Google didn’t instantly implement this conduct is that many apps might need UI points in the event that they have been pressured to go edge-to-edge. For instance, an app might need an interactive ingredient like a floating motion button that might overlap with the navigation bar if it went edge-to-edge.

To resolve this, Google gave builders a strategy to deal with overlaps through the use of insets, which specify which components of the app’s display intersect with the system UI. Nevertheless, as a result of edge-to-edge was by no means enforced on apps, many builders didn’t have to trouble with dealing with these UI conflicts. That’s supposed to alter with Android 15, although.

When Google introduced Android 15 Beta 1 earlier this yr, they revealed that apps concentrating on Android 15 shall be displayed edge-to-edge by default. To help builders with this transition, Google revealed new developer docs, tutorials, and codelabs that exhibit how you can deal with edge-to-edge enforcements in Android 15.

What none of those guides point out, although, is that there’s truly an API that apps can use to decide out of edge-to-edge mode.

On the left: App targets SDK 34 (Android 14) and isn’t edge-to-edge on an Android 15 machine.
On the correct: App targets SDK 35 (Android 15) and is edge-to-edge on an Android 15 machine. Supply: Google

The API in query is an attribute referred to as windowOptOutEdgeToEdgeEnforcement that apps can set to true of their theme information. The attribute is fake by default, which signifies that edge-to-edge enforcement shall be utilized to the window if it’s a part of an app that targets Android 15. If the attribute is about to true, although, then edge-to-edge enforcement received’t be utilized to the window in query.

Nevertheless, the outline for the API warns that “this attribute shall be deprecated and disabled in a future SDK degree,” which suggests this workaround received’t exist without end. On the very least, it offers builders a minimum of two further years to optimize their apps for edge-to-edge mode for the reason that Google Play Retailer received’t drive apps to focus on Android 15 till August 31, 2026. Even then, we don’t know precisely which model of Android will truly deprecate and disable this attribute as Google warns, that means it could possibly be used to keep away from supporting edge-to-edge mode for longer than two years.

Regardless, we hope most builders will replace their apps to assist edge-to-edge mode somewhat than decide out. If not, we hope that this attribute is just used to quickly and selectively decide sure home windows out of edge-to-edge enforcement. A number of of Google’s personal apps could also be doing simply this, as the oldsters over on the GN Points group on Telegram have identified that apps like Telephone by Google and Google Play Companies aren’t drawing edge-to-edge regardless of concentrating on Android 15.

Then there’s Google Chrome for Android, which can additionally use this API to decide out of edge-to-edge mode. Some builders are additionally pushing Google to offer an opt-out mechanism in future variations of Android, and in the event that they oblige, then Android’s edge-to-edge enforcement may return to being only a suggestion.