Last year, only one Apple phone had a notch in its screen—the iPhone X. With that, Apple introduced a whole new paradigm for end users and app designers. Since only one phone featured this design, many applications simply used letterboxing, instead of embracing the notch and taking advantage of the increased screen size. Now, all of Apple’s flagship phones are shipping with a “notch” similar to the one introduced last year on the iPhone X. If you haven’t already embraced the notch, now is the time to do so. This year’s Apple Watch has been completely redesigned. It’s thinner and has a larger screen, one that almost completely eliminates the bezels. It can even perform an ECG! The problem is, these new screen sizes create fragmentation for developers in the same way a million different Android phones do.
As with iPhone and iPad apps, Apple Watch apps need to be designed with adaptive layouts in mind. WatchKit’s layout system is simpler than Autolayout’s. Sometimes this tempts developers to use fixed sizes when implementing the layout for watch apps. This was a reasonable implementation when only handling two screen sizes—as at most, there were two values to worry about. But this new announcement throws a wrench in that plan by introducing two additional sizes. Developers may be tempted to simply add constants to adapt to the new screen sizes, but I caution against that. The best way to build applications to handle the future—including screen sizes that haven’t been revealed yet—is to build your layouts to be as adaptive as possible.
This announcement suggests Apple isn’t afraid to mix things up as far as their new hardware screens are concerned. So from now on, designers and developers need to create iOS and WatchKit applications not only for current phones and watches, but also with adaptive layouts for future models in mind. If your organization needs help designing, developing or updating its mobile applications for the new devices (or for the new iOS), please don’t hesitate to contact the mobile development team at Anexinet today.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
|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".|
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.