Graphics Reference
In-Depth Information
An early version of the application showing different navigational models. The team tried to com-
bine lists and sliding panels. However, the feeling was they were a little too complex. The team
were keen to have the interface dissolve, to put the content directly under the fingertips, rather
than having separate navigational and content modes.
Approach
The team looked around the app market at what other newspapers and magazines
were doing, as well as other RSS reader and social networking apps. From these they
started to realize what they didn't want to do and began to build a picture of what they
thought was missing and frustrating to use from other print publications' iPad trans-
lations.
The team had to ask how information delivery changes when you deliver content with
a different tool. As the paper was the starting point, they began by breaking down
what they had learned from decades of desktop publishing development in that area.
They wanted to pass on those principles, and the iPad project gave them the oppor-
tunity to do so for the first time in a digital space. They were looking at a more soph-
isticated design language than they had previously used; a lot of this was down to the
space afforded and the screen resolution allowing for more finessed typography (the
first time they had been able to use print typefaces from the newspaper).
In addition, they tried to recreate new, interesting methods of hierarchy through scale,
allowing people to discover and read news through serendipity. They put the emphas-
is back on the editors and asked the user to trust them to deliver a finite package of
broad news that a user could skim through as effortlessly as flicking through the pages
of the newspaper.
The iPad device changes how news content is consumed; with the iPhone app and
website, consumption is brief and top-level, whereas the iPad is much more likely to
be used around the home, in bed or on long journeys with more deliberation. This al-
