This depends on the following CL that makes this all work with template changes: I848f442b3bc66ee2fb87db8200df370d13762d29 Change-Id: I6b17db774de6fa8be0bf944516a44ba73b10cabb
59 lines
2.7 KiB
Plaintext
59 lines
2.7 KiB
Plaintext
page.title=UI Overview
|
|
page.customHeadTag=<link rel="stylesheet" type="text/css" href="/wear/css/wear.css">
|
|
|
|
@jd:body
|
|
|
|
<style>
|
|
h3 {
|
|
padding:30px 0 10px;
|
|
}
|
|
</style>
|
|
|
|
<p>A new form factor deserves a new UI model. At a high level, the Android Wear UI consists of two
|
|
main spaces centered around the core functions of <strong>Suggest</strong> and
|
|
<strong>Demand</strong>. Your application will have an important role to play in both of these
|
|
spaces.</p>
|
|
|
|
|
|
|
|
<h3 id="Stream">Suggest: The Context Stream</h3>
|
|
|
|
<div class="wear-inset-video-container" style="float:right;margin:0 -22px 60px 40px">
|
|
<img class="wear-bezel-only" src="{@docRoot}wear/images/screens/bezel.png" alt="">
|
|
<img class="gif" src="{@docRoot}wear/images/screens/stream.gif">
|
|
</div>
|
|
|
|
<p>The context stream is a vertical list of cards, each showing a useful or timely piece of
|
|
information. Much like Google Now on Android phones and tablets, users swipe vertically to navigate
|
|
from card to card for a brief and comprehensive update about what's important to them. Only one card
|
|
is displayed on screen at a time, and background images are used to provide additional visual
|
|
information. Your application can create cards and inject them into the stream when they are most
|
|
likely to be useful.</p>
|
|
|
|
<p>Cards in the stream are more than simple notifications. They can be swiped horizontally to
|
|
reveal additional pages. Further horizontal swiping may reveal tappable buttons, allowing the user
|
|
to take action on the notification. Cards can also be dismissed by swiping left to right, removing
|
|
them from the stream until the next time they have useful information to display.
|
|
In the emulator, hovering the mouse over the top of the screen illuminates a blue bar at
|
|
the top of the device that takes you home when clicked.</p>
|
|
|
|
|
|
|
|
<h3 id="CueCard">Demand: The Cue Card</h3>
|
|
|
|
<div class="wear-inset-video-container" style="float:right;margin:0 -22px 60px 40px">
|
|
<img class="wear-bezel-only" src="{@docRoot}wear/images/screens/bezel.png" alt="">
|
|
<img class="gif" src="{@docRoot}wear/images/screens/cuecard.gif">
|
|
</div>
|
|
|
|
<p>For cases where the context stream can't anticipate what the user would like to do, the cue card
|
|
allows users to speak to their device. The cue card is opened by saying, "Ok Google" or by tapping
|
|
on the "g" icon on the home screen. Swiping up on the cue card shows a list of actions, which can
|
|
also be tapped.</p>
|
|
|
|
<p>The list of actions includes Android intents for voice actions. The upcoming Android Wear SDK
|
|
will enable developers to match their applications to these intents so users can perform actions
|
|
using these voice commands. Multiple applications may register for a single voice intent, and users
|
|
will have the opportunity to choose which application they prefer to use.</p>
|
|
|