One of my biggest takeaways of WWDC 2014 was Adaptive Apps. If you haven’t yet, you can check the video for session 216, Building Adaptive Apps with UIKit.
In the past days, there have been a few articles about it (I got to them via Brent Simmons):
- Developers, The iOS Line and Reactive Design
- Thinking In Terms Of iOS 8 Size Classes
- Device Sizes (updated to include a Tweet I sent Brent in reply).
Over the last three years (as I think is usual with Apple), we’ve seen a succession of technologies that we were “suggested to adopt”:
- iOS 6 brought us Auto Layout, as a declarative way of creating constraints between our views.
- iOS 7 introduced Dynamic Text, allowing users to easily tune the sizes of all the fonts in their devices.
- iOS 8 is adding Adaptive Apps in UIKit and Presentation Controllers.
Adaptive apps are sold to us for two main reasons: supporting both iPhone and iPad with the same codebase with less specific cases, and supporting the new rotation. New device form factors are -of course- never mentioned in any WWDC session, nor is the ability to resize apps on an iPad, as apparently will be the case.
If the next iPhone indeed ships with a bigger screen, the main reason would be to have more content on screen at the same time, not to have something akin to an
@3x. So, if we assume the screen will be bigger (to fit more content), we only have one question: will the screen have the same DPI as the existing iPhone?
Let’s explore the ramifications of each option.
Same DPI as iPhone 5s
Ever since the original iPhone, objects on screen have had the same physical size. The move to retina only increased the pixel count, but the actual size remained the same.
Keeping the same DPI will be an impact similar to when the iPhone 5 shipped: our apps will need to adapt and show more content. If the phone is wide enough, there’s a chance the Horizontal Size Class in Portrait of this new device changes to Regular as opposed to Compact, and our apps will need to adapt to it (
UISplitViewControllers will became more common, for one). With the same logic, the Vertical Size Class in Landscape might change to Regular.
All in all, this change will probably be the easier to deal with, as typography and images will look the same.1
Higher DPI than the iPhone 5s
As I tweeted to Brent Simmons, here’s where I think it gets interesting.
If Apple wants to have the text look the same size, they might tune the Dynamic Text default sizes on the new device to compensate for the higher DPI2.
On session 226, What’s new in Table and Collection Views you can see how they use the multiplier in Auto Layout constraints so that
UITableViewCells change in height as the Dynamic Text size changes, and look better when bigger fonts are in use.
I can see this approach being the recommended way forward, basing the layout around the text sizes, so Apple can tweak them based on the hardware they ship.
My notes from session 216 were that
UIUserInterfaceIdiom was deprecated. What they actually said is:
In the past you’ve used UIInterfaceOrientation and UIUserInterfaceIdiom to differentiate between portrait and landscape and iPhone and iPad, but in iOS 8, we’re recommending against using these two concepts, and instead we’re advocating this > new concept that we call size classes.
UITraitCollection contains a
userInterfaceIdiom trait. Why was this kept, if Apple is suggesting against basing the UI based on the device? My understanding is that it’s there because we’ll still need it to determine the intent of the user. Our apps need to know if the user has launched our app on his iPhone, probably on the move or doing something else, or on an iPad, where we can assume he’s more comfortable and about to have a longer use session.3
I don’t think there’s a huge business implication for this right away. If you want to ship to separate apps for iPhone and iPad, I don’t expect Apple to prevent you from doing it.
However, since you’ll have to support iPhones with multiple screen sizes, it’s very possible that going from a multi-sized iPhone app to a Universal app will be a simpler transition. This, I’m confident, might have the nice outcome of combating what Marco Arment called App Rot and provide more quality universal apps for the users.
Implications for font heavy apps
There are some apps that rely a lot on custom fonts, such as Vesper. Since Dynamic Text does not allow you to use custom fonts, I wonder how those apps will work around a different Dynamic Text default size. There are tons of valid workarounds, like fetching the system font size and base your custom font size on it, but an Apple blessed solution would do a lot to help in this direction.4
Any given text, at the same Dynamic Text setting will look the same on the iPhone 5s and on the new iPhone. ↩
I’m assuming the new device still runs with a display scale of 2.0, as the retina screens we currently have. ↩
I first thought this had to do with device capabilities, such as to tell if the app needs to highlight phone numbers or not. I think that’s a blurrier line, as we don’t know what capabilities future devices will have, and well behaved apps need to check for specific capabilities instead, not make assumptions based on the
While I’m not sure what the best solution is, I’ll be happy to have something similar to a very simple CSS file, where you can specify for each Text Style the font name, size and weight you want it to take. ↩