Google publishes guidelines on supporting phones with notches on Android P
The year 2017 gave birth to the notch trend, for better or for worse. The Essential Phone is widely regarded as the phone that kickstarted the display notch trend, with Apple shortly following up on that trend with the iPhone X—and making it the norm on 2018 flagship phones in the process. Since then, we’ve had our fair share of notched devices, including the LG G7 ThinQ, the Huawei P20, and the OnePlus 6. OEMs can’t hide the front camera and other sensors under the display yet, and we’re yet to see whether moving sensors (like the ones in the Oppo Find X and the Vivo Nex) are a reliable alternative. Notches/display cutouts and extended aspect ratios (18:9, 19:9, 19.5:9) are the next logical step as the screen-to-body ratio keeps growing bigger and bigger. Google is making sure Android P will properly support them.
Mixed feelings aside, Google has published a guide to properly support phones with display cutouts on your Android app. The final version of Android P will include full support for display notches in all shapes and forms, including regular notches, double notches (top + bottom notch), and corner cutouts—which makes sense, since the Pixel 3 XL is touted to be the first Pixel device to rock a display notch. So it makes complete sense for Google to give developers a heads up on how to properly support a notch in their apps.
With that in mind, for the most part, your app should still function just as well with the display notch, since the Android system already takes care of UI elements so that they don’t get in the way of the notch. But you can tweak your app to actually take advantage of that space properly. Since we’re expecting to see a lot more notched devices in 2018 and 2019, which will launch with Android P, it’s a smart move to prepare for it beforehand. You can have a look at Google’s guidelines below. While you’re at it, if you haven’t done so yet, it’d be a good idea to adapt your application to taller aspect ratios as well.
Source: Android Developers Blog