“We want the chrome to get out of the way” – Jason Beaver
How do you do this? By giving more relevance to the content.
Improving typography is the best and first way to improve content display. The fact that typography was the firs topic of the “Building User Interfaces for iOS” WWDC session – dedicated on the basics iOS redesign – speaks for itself.
Whether you’re sold on the thinness of Helvetica Neue on iOS 7 or not, Apple introduced a great deal of improvements in how you can handle typesetting into you new iOS 7 apps.
Entering dynamic type: this will seem dumb to people working on web typography, but setting type inside an iOS app has been a pain in the ass up until now – no semantics tags for. Dynamic type allows you to set text styles in a semantic way.
This is a huge step forward because introduces a concept of responsiveness also for native application design, forcing interface designers to think in terms of content first, abandoning rigid chrome conventions.
Entering support to kerning, ligatures, ornaments, etchings and engravings.
Text Kit, built on top of the not-so-friendly-not-so-useful Core Text framework, allows a better and easier management of textual objects and layouts: despite the criticism on iOS 7 system-wise typography, it seems to me that typesetting has been approached in a very focused and careful way by Apple.