From 4672669ff951cd139904e0eb7593989721a15d1d Mon Sep 17 00:00:00 2001
From: Joe Fernandez Key developer features
@@ -48,6 +50,73 @@ page.image=images/cards/card-n-apis_2x.png
highlight some of the new features for Wear developers.
+
The preview introduces powerful additions to the user interface, opening up +exciting possibilities to developers. +A complication is any feature in a watch face that displays more than hours and +minutes. With the Complications API, + watch faces can display extra information and separate apps can expose complication + data. +The navigation and action drawers provide users with new ways to interact with apps. +
+ + ++ A complication is a + feature of a watch face that displays more than hours and minutes, such as a + battery indicator or a step counter. The Complications API helps watch face + developers create these features visual features and data connections they + require. +
+ ++ Watch faces that use this API can display extra information without needing + code for getting the underlying data. Data providers can supply data to any + watch face using the API. +
+ +For examples of how to use this feature, +see + Watch Face Complications. +
+ + +Wear 2.0 introduces two new widgets, navigation drawer and action drawer. These + widgets give your users new ways to interact with your app. The navigation drawer + appears at the top of the screen and allows users to navigate between app views. + The action drawer appears at the bottom of the screen and allows users to choose + from a list of actions associated with the current usage context. These drawers + are accessible to users when they edge swipe from the top or bottom of the + screen; they peek when users scroll in an opposite direction. +
+ ++ To learn how to add these widgets to your app, see + + Wear Navigation and Actions. +
+ +In Wear 2.0, weâve redesigned the key experiences on the watch to be even more
@@ -56,16 +125,21 @@ page.image=images/cards/card-n-apis_2x.png
Notification Changes in Wear 2.0.
-
+
When a user taps on a notification that is bridged from the phone to -the watch or that lacks a {@code contentIntent}, the user will be -taken to the expanded view of that notification. When you -specify additional - content pages and actions for a notification, those are available to the user - within the expanded notification. Each expanded notification follows Material Design for Android Wear, so the user gets an app-like experience. +
+ When a user taps on a notification that is bridged from the phone to the + watch or that lacks a + + {@code contentIntent}, the user will be taken to the expanded view of + that notification. When you specify additional + content pages and actions for a notification, those are available to the + user within the expanded notification. Each expanded notification follows + Material Design for Android + Wear, so the user gets an app-like experience.
@@ -95,7 +169,8 @@ users a fast (single tap), discreet (no speaking aloud), and reliable way to res -The preview introduces powerful additions to the user interface, opening up -exciting possibilities to developers. -A complication is any feature in a watch face that displays more than hours and -minutes. With the Complications API, - watch faces can display extra information and separate apps can expose complication - data. -The navigation and action drawers provide users with new ways to interact with apps. -
- -A complication is a feature of a watch face -that displays more than hours and minutes. For -example, a battery indicator is a complication. The Complications API is for -both watch faces and data provider apps.
- -Watch faces can display extra information without needing code for getting -the underlying data. Data providers can supply data to any watch face using the -API.
- -For examples of how to use this feature, -see - Watch Face Complications. -
- -Wear 2.0 introduces two new widgets, navigation drawer and action drawer. These - widgets give your users new ways to interact with your app. The navigation drawer - appears at the top of the screen and allows users to navigate between app views. - The action drawer appears at the bottom of the screen and allows users to choose - from a list of actions associated with the current usage context. These drawers - are accessible to users when they edge swipe from the top or bottom of the - screen; they peek when users scroll in an opposite direction. -
- -- Figure 1. Navigation and Action Drawers. -
-To learn how to add these widgets to your app, see -Wear Navigation and Actions. - -
diff --git a/docs/html/wear/preview/downloads.jd b/docs/html/wear/preview/downloads.jd index 47ae39782581..9311494ccb6c 100644 --- a/docs/html/wear/preview/downloads.jd +++ b/docs/html/wear/preview/downloads.jd @@ -1,7 +1,7 @@ page.title=Download and Test with a Device meta.keywords="wear-preview" page.tags="wear-preview" -page.image=images/cards/card-n-sdk_2x.png +page.image=images/cards/card-n-downloads_2x.png @jd:body diff --git a/docs/html/wear/preview/features/bridger.jd b/docs/html/wear/preview/features/bridger.jd index 91b1bedf7260..0597f270108a 100644 --- a/docs/html/wear/preview/features/bridger.jd +++ b/docs/html/wear/preview/features/bridger.jd @@ -25,15 +25,14 @@ page.tags="wear-preview"By default, notifications are bridged - (shared) from an app on a companion phone to the watch. Standalone - Android Wear apps are planned for Android Wear 2.0. Therefore, a phone - app and a standalone watch app may be sources of the same notifications. - The Android Wear 2.0 Preview includes a Bridging mode feature to handle - this problem of duplicate notifications. + (shared) from an app on a companion phone to the watch. If you build + a standalone watch app and have a companion phone app, they may duplicate + notifications. The Android Wear 2.0 Preview includes a Bridging mode + feature to handle this problem of repeated notifications.
- With the Android Wear 2.0 Preview, developers can plan to change the + With the Android Wear 2.0 Preview, developers can change the behavior of notifications with the following:
-- 2.11.0