1page.title=Style for Android Wear 2@jd:body 3 4 5<p>Here are a number of design considerations to bear in mind that are particular to Android Wear.</p> 6 7 8 9<img src="{@docRoot}design/media/wear/circle_message2.png" height="200" 10 style="float:right;margin:32px 0 50px 40px;"> 11 12<img src="{@docRoot}design/media/wear/fitness.png" height="200" 13 style="float:right;margin:32px 0 50px 40px;"> 14 15<h2 id="ScreenSize">Screen Size</h2> 16 17<p>Be mindful of different device sizes and shapes. Wearable devices are a form of fashion and expression for their owners, and so Android Wear supports a variety of forms. Most of the complexities of supporting these different devices is taken care of at a system level, but bear in mind different screen types when designing custom full screen apps.</p> 18 19<p>Use the Android Wear emulator to test both square and round devices, and note that <a 20href="{@docRoot}training/wearables/apps/layouts.html#UiLibrary"><code>WatchViewStub</code></a> is available to activities to detect whether a square or round device is being used.</p> 21 22 23 24<div class="cols"> 25 <div class="col-6"> 26 27 <img src="{@docRoot}design/media/wear/assets_specifics.png" width="300" 28 style="margin:32px 0 20px;"> 29 </div> 30 <div class="col-7"> 31 <h2 id="Assets" style="clear:both">Specific Assets Required</h2> 32 33 <p>A core set of standard assets may need to be provided depending on your card design: app icon, background image or images, action icons, and action confirmation animations. Of course, your specific design may necessitate other assets. Background images should be provided in landscape format at least 600px width for notifications that include pages of cards, since the system automatically adds a parallaxing effect.</p> 34 </div> 35</div> 36 37<div class="cols"> 38 <div class="col-6"> 39 <h2 id="PeekCard" style="clear:both">Peek Card Readability</h2> 40 41 <p>Test your card layout to ensure that useful information is conveyed in the peek state on the Home screen. The main message of the card should be readable in the peek state, particularly for contextual cards. Content that requires an interaction to be read, for example a long message, should be cropped appropriately to provide an affordance to the user to swipe the card to read more.</p> 42 </div> 43 <div class="col-6"> 44 45 <img src="{@docRoot}design/media/wear/peek-card.png" width="300" 46 style="margin:12px 0 0 20px"> 47 </div> 48</div> 49 50 51<h2 id="InfoDensity" style="margin-top:0" >Low Information Density</h2> 52 53<img src="{@docRoot}design/media/wear/low_info_card.png" width="147" height="147" 54style="float:left;margin:5px 20px 20px 0"> 55 56<p>Cards should be designed to be glanceable in a split second, just like reading the time on a traditional watch. In most cases a pairing of an icon and value, or a title and short caption should be enough to convey a meaningful message. Note that the background photo should also be used to convey information; backgrounds that change to reflect and support the primary message in the card work great. For example, in the case illustrated to the right, a suitable background image is chosen to reflect the severity of current traffic conditions. This is not just a nice piece of attention to detail; the background actually reinforces the message and makes the content more glanceable.</p> 57 58 59 60<h2 id="Chunks">Separate Information into Chunks</h2> 61<img src="{@docRoot}design/media/wear/separate_info_cards.jpg" height="147" 62 style="float:right;margin:5px 0 20px 20px"> 63 64<p>In cases where additional information is absolutely necessary, don’t crowd out a card layout to the point where glanceability is affected. Instead, add an additional <a href="{@docRoot}design/wear/patterns.html#Pages">page</a> (or multiple pages, if needed) to the right of the main card in the stream to which the user can swipe for more information. See also <a 65href="{@docRoot}design/wear/patterns.html#Continuing">Continuing activities on phone</a>.</p> 66 67 68<h2 id="KeepMinimum" style="clear:both">Keep Notifications to a Minimum</h2> 69 70<p>Don’t abuse the user’s attention. Active notifications (that is, those that cause the device to vibrate) should only be used in cases that are both timely and involve a contact, for example receiving a message from a friend. Non-urgent notifications should be silently added to the Context Stream. See also the general <a href="{@docRoot}design/patterns/notifications.html">Android Notifications Guidelines</a>.</p> 71 72 73 74 75<h2 id="Typography" >Use Clear, Bold Typography</h2> 76<img src="{@docRoot}design/media/wear/clear_bold_type.jpg" height="147" 77 style="float:left;margin:5px 20px 20px 0"> 78 79<p>The system font is Roboto Condensed, with Regular and Light variants. Text should adhere to the size and color recommendations (see the UI Toolkit in the <a href="{@docRoot}design/downloads/index.html#Wear">Downloads</a> page). In general, text should be displayed as large as possible. Your goal should be to convey maximum information with minimum fuss.</p> 80 81 82<h2 id="Branding" style="clear:both" >Use Consistent Branding and Color</h2> 83 84<img src="{@docRoot}design/media/wear/copywrite.png" height="147" 85 style="float:right;margin:0 20px 0 20px"> 86 87<p style="margin-bottom: 60px">The app icon is used to identify and brand your application. The icon is optional but when present always appears in the same location, overhanging the top right edge of the card. Note that app icons or branding should not be displayed in the background photo, which is reserved to display an image relevant to the information on the card.</p> 88 89<h2 id="Copywrite" >Copywrite Sparingly</h2> 90 91<p>Omit needless text. Design for glanceability and not for reading. Use words and phrases, not sentences. Use icons paired with values instead of text wherever possible. Text strings should be as concise as possible, and long pieces of text will be truncated to fit on a single card.</p> 92 93 94<h2 id="BeDiscreet" style="clear:both" >Be Discreet if Necessary</h2> 95 96<p>Wearables are personal devices by nature, but they are not completely private. If your notification serves content that may be particularly sensitive or embarrassing (such as notifications from a dating app or a medical status report), consider not displaying all of the information in a peek card. A notification could place the sensitive information on a second page that must be swiped to, or an application could show different amounts of detail in peek and focused card positions.</p> 97 98<h2 id="ConfirmAnim">Confirmation Animations</h2> 99 100<img src="{@docRoot}design/media/wear/confirmation.png" height="147" 101 style="float:left;margin:5px 20px 20px 0"> 102 103<p>If your app allows the user to perform an action, it is necessary to provide positive feedback. Show a generic confirmation animation or create your own. A confirmation animation is an opportunity to express your app’s character and insert a moment of delight for your user. Keep animations short (less than 1000ms) and simple. Animating the confirmation icon is an effective way of transitioning the user to a new state after completing an action.</p> 104 105<p style="clear:both;height:0"> </p>
