Professional Documents
Culture Documents
iOS is a popular platform for creating apps that are touch first, fun, and engaging. With the introduction of Windows 8 Consumer
Preview, designers and developers have a new platform to unleash their creativity.
In this case study we want to help designers and developers who are familiar with iOS to reimagine their apps using Metro style
design principles. We show you how to translate common user interface and experience patterns found in iPad apps to Windows 8
Metro style apps. We draw on our experience building the same app for the iPad and for Windows 8. We use common design and
development scenarios to show how to leverage the Windows 8 platform and incorporate Metro style design principles.
To learn more about the business opportunity of Windows 8, see Selling apps. For more info about the features used to build Metro
style apps, see the Windows 8 Product Guide for Developers.
Contents
The app ................................................................................................................................................................................................................. 2
Layout and navigation ........................................................................................................................................................................................ 4
Commands and actions .................................................................................................................................................................................... 13
Contracts ............................................................................................................................................................................................................. 17
Touch ................................................................................................................................................................................................................... 26
Orientation and views ....................................................................................................................................................................................... 30
Notifications ....................................................................................................................................................................................................... 33
About the authors ............................................................................................................................................................................................. 37
The app
The app we are developing is a connected photo journal where users can view and manage their photos and videos online using a
timeline view.
The app was first created for the iPad. The next figure shows the anatomy of the iPad app. Let's now see how each component
translates to Metro style design.
iPad app
A. Top navigation bar
B. App content
C. Pagination UI
D. Bottom tab bar
iPad: each month is represented by stacked photos with only one photo visible.
Metro style app: each month is represented by multiple photos, their titles, and the number of comments associated with the
photos. Users can see more highlighted content for a month on the home screen.
iPad app
A. Photos view
B. Comments view
The bottom tab bar with two pivots (photos and comments) is always on screen. Users can see one view or the other.
We combined the comment and photos in one view to eliminate the need for a tabbed user interface.
The hub design for the home screen reveals the most relevant content for each section.
To see the entire list of comments, users can tap on the group header labeled Recent comments.
iPad app
On the home screen, tap on the Years button on the top navigation bar to bring up a popover and select a year.
iPad app
App commands are on the top of the screen when a user enters the selection mode.
B. When a user selects objects on the page, contextual actions for the selected items appear on the bar. The actions change
depending on whether there are objects selected and where the user is in the app. Global commands are usually placed on the right
side of the app bar. Commands that come and go should be placed on the left side of the app bar.
Contracts
Use Search contract to centralize the search experience
Instead of creating a search input interface that is permanently part of the app canvas, we implemented the search contract. Users
can consistently invoke Search through the charms, and the results can be presented in the app in a way that is natural for the
content. By using the Search contract, users can invoke the Search charm from anywhere in the system to look for content from apps
that support the contract.
Example: searching a photo within the Photo journal app
iPad app
The user opens the charm bar and accesses the Search charm. The Photo journal app is selected by default because the user is
currently inside the app.
When the user starts typing, the app supplies search suggestions to the pane. This way users can quickly see which terms will
generate search results. After the user submits their query, they see a search results view and select the result they want.
Example: searching for a photo outside of the Photo journal app (available only in Metro style app)
This example shows how to search for a term across different apps by choosing a new app via the search pane. This functionality
allows users to search for any piece of content, in any app, at any time.
Use the Share contract to reach more destinations and people you care about
Social media integration is a key component of most apps. When designing iPad apps, designers and developers generally choose
which social media channels the app supports (such as Twitter or Facebook) and then the developers must integrate each of these
services individually, or use one of the available frameworks. When there are API changes to these sharing services, developers must
update their code for the sharing services to continue to work.
When translating the sharing capability into the Metro style app, we used the system's Share contract. This contract simplifies design
and development because there is no need to connect with every service that a user might want to use. In addition to social
networks, users can also save content to other services, such as a note taking app like Notespace or EverNote. Using just a small
amount of code, our app becomes connected with every Metro style app that has implemented the Share contract. There's no need
to deal with API changes to external social networking sites or web services. From the user's perspective, they can always share from a
consistent location by accessing the charms bar and opening the Share pane.
Example: sharing a photo in Photo journal with another app
iPad
To share a photo from the iPad Photo journal app, a user first taps the action button from the top navigation bar and then chooses to
share on Facebook. The developer needs to do additional work and add more share buttons if they want to integrate with other
social networking services later.
Users can always find share options in a consistent location, regardless of which app they're using.
Any installed app that has been designated a share target appears in the app list in the Share pane. For example, Socialite,
Tweet@Rama, Notespace, PaintPlay, are all share targets.
Users can share a variety of content types. For example, users can share links, photos, or save info to a note-taking app.
The most frequently used share targets are displayed at the top of the list to help users complete tasks quickly.
In addition to being a share source, we designed our Photo journal app to be a share target too. Users can easily share photos from
another app to their photo streams in Photo journal. This connection is also enabled by the Share contract. See Guidelines and
checklist for sharing content for more info about which apps make great share targets.
Example: sharing photos from another app with Photo journal share target (available only in Metro style apps)
In this example, a user in another photo app looks at photos from a trip to Mexico. They want to share the photos from the album
with their own Photo journal app collection so that it is easier for them to view these photos in a timeline view. As the user opens the
Share pane, they see that the Photo journal app is listed as one of the Share targets and then invokes the Share workflow.
iPad app
The iPad app supports accessing photos in the local photo library and a couple of social networking services.
Touch
Edge swiping for app and system commands
Using Windows 8, a user can swipe from edges to access commands and navigate between apps.
App commands are revealed by swiping from the bottom or top edge of the screen. The app bar should always be used to
display app commands.
Swiping from the right edge of the screen reveals the charms bar that contains system commands.
Swiping from the left edge switches to previously used apps.
Swiping from the top edge toward the bottom edge of the screen lets you dock or close apps.
Example: accessing the app bar and the charms bar in a Metro style app
Swipe from the right edge of the screen to reveal the charms bar that
contains system commands - Search, Share, Start, Devices, and Settings.
iPad app
Users enter a specific edit mode to perform the selection action and other edit actions. This is because tap is reserved for
primary actions such as launch.
Users exit the edit mode when they are done.
Users swipe down on the object to select and the app bar shows up automatically with contextually relevant commands.
Users can perform both tap and selection on an object without entering and exiting another mode.
This gesture is reversible, which makes selection a lot more efficient in Windows 8 apps.
iPad app
The same content is shown in both landscape and portrait layout. The content reflows in portrait orientation.
The snap view of the home screen is just a different view of the home page where a user can still access the same content.
In snap view, a user pans vertically to get to more content because it is more comfortable to pan along the long edge. This is
different than the horizontal panning in full view, which is also optimized to pan along the long edge.
Notifications
Use tiles for persistent and dynamic updates
iOS 5 introduced a notification center where new notifications appear quickly on the top of the screen and users can swipe from the
top to view all messages in the center. In addition, app icons in the iOS Springboard can have number badges attached to them to
indicate that there are new messages. The tiles on the Windows 8 Start screen combine the functionality of both numeric badges on
app icons and the Notification Center on an iPad. Users can launch apps and read notifications all from one place. In addition, unlike
the notifications in iOS which have a fixed format, Metro style appMetro style app tiles have a rich collection of templates for
designers to choose from.
iPad
A. App icon with numeric badge on iPad Springboard.
B. Notification center with Photo journal notification.
Windows 8
C. Tile on the Start screen with both numeric badge and notifications that users. Many tile templates are available.
Example: Photo journal notifies users when they receive a comment from a family member
User is set up to receive toast notifications when a family member has commented on photos in the app.
Qixing Zheng is a User Experience Program Manager at Microsoft. She is part of the team that created the
Windows 8 user interface and has been helping designers to learn about Metro style design. Her passion is
deeply rooted in helping people improve their user experience with the technology they rely on every day.
Before joining the Windows team, Qixing worked as the first UX advisor at Microsoft Canada where she
spoke at universities, design communities, and companies about Microsofts investment in UX. She also
worked at identifying design heroes and collecting design stories from the community.