The iPhone X introduced a whole new paradigm to iOS. Between edge to edge display, an absent home button, Face ID, and a whole host of additional features, the iPhone X is like nothing Apple has ever made. There’s a catch though: with a whole new paradigm comes a whole new set of issues for developers.
When Apple announced the iPhone X, they touted it as Bezel-less and having an edge-to-edge display. While technically true, this fundamentally clashes with the reality of using the iPhone X. Simply put, not all pixels are created equal. Think of the “ears” of the notch as part of the phone’s bezel, but one that we can control and use (instead of just letting it sit idle).
When designing for iPhone X, several considerations must be taken. In particular, designers and developers need to be careful with full-screen content. On the iPhone X, full-screen content may be obscured by the corners, the sensor housing, and the home indicator. So, when designing for iPhone X, keep in mind that while full-width buttons still work well, they will need to have rounded corners and reside entirely within the safe area (which has slightly smaller width than the screen). Additionally, the aspect ratio of iPhone X varies from that of other iPhones. This means letterboxing (or cropping) will occur if you reuse full-screen art from other devices. Therefore, in order to fully embrace the notch, you will need to recreate the problematic assets to be suitable for iPhone X
Apple’s API acknowledges that not all iPhone X pixels are created equal and offers tools to determine which areas of the screen are safe to place content on, and which aren’t. Apple’s API provides a method called safeAreaLayoutGuide: a set of constraints used to adjust the content of your layout. Typically, developers use the Safe Area Layout Guide to adjust autolayout constraints. Here’s a basic example, courtesy of UseYourLoaf.com:
When we setup constraints using the Safe Area Layout Guide, we ensure the app won’t be cropped by any portion of the display, including the notch. Thus, fully embracing the notch in iOS development means fully embracing the Safe Area Layout Guide.
Apple has made it as easy as possible to use the Safe Area Layout Guide in your app. They want you to use it! The guide is available in the storyboard editor, so if you create most of your interface constraints in Storyboard (like I do), it’s as easy as creating any other constraint in Interface Builder (IB). The guides are also backwards compatible—meaning you can create your app in the latest version of Xcode, built using the latest version of the SDK, but target an earlier version of iOS, and the layouts will work perfectly—even on the older versions of iOS. In short, there’s no reason NOT to embrace the Safe Area Layout Guide as you develop for iOS, but every reason to embrace the notch itself. It’s here to stay.
Embracing the Notch requires updating your app to take advantage of the latest Apple technologies. At Anexinet, we pride ourselves on being on the bleeding edge of Mobile Development, for both the consumer and enterprise markets. If you need help developing, testing or supporting a mobile application, please reach out to Anexinet. Whether you’re targeting customers or employees, we’d love to help design, build and maintain your next transformative mobile app.
https://developer.apple.com/ios/human-interface-guidelines/overview/iphone-x/
https://useyourloaf.com/blog/safe-area-layout-guide/
https://www.cnet.comhttps://anexinet.com/news//why-google-makes-android-phone-notches-now/
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.