-
-
- Standalone Devices - -
- Notifications and Input
- Expanded Notification @@ -30,6 +23,13 @@ page.image=images/cards/card-n-apis_2x.png
- Input Method Framework
+ - Standalone Devices + +
- User Interface Improvements
- Complications @@ -48,10 +48,124 @@ page.image=images/cards/card-n-apis_2x.png highlight some of the new features for Wear developers. +
- Dictation +
- Emoji +
- Canned responses +
- Smart Reply +
- Default IME +
- Specifying in the standalone app's Android manifest file that notifications from + the corresponding phone app should not be bridged to the watch. +
- Setting a dismissal ID so notification dismissals (by users) are synced across +devices. +
- Enable multiple IMEs from the list of installed IMEs. +
- Set a single default IME from the list of enabled IMEs. +
- Change languages for various IMEs. +
- Dictation -
- Emoji -
- Canned responses -
- Smart Reply -
- Default IME -
- Specifying in the standalone app's Android manifest file that notifications from - the corresponding phone app should not be bridged to the watch. -
- Setting a dismissal ID so notification dismissals (by users) are synced across -devices. -
- Enable multiple IMEs from the list of installed IMEs. -
- Set a single default IME from the list of enabled IMEs. -
- Change languages for various IMEs. -
Notifications and Input
+ +In Wear 2.0, we’ve redesigned the key experiences on the watch to be even more + intuitive and provide users new ways to respond to messages. Some of the highlights + are below; for a complete list of changes, see + Notification Changes in Wear 2.0. + + +
+Expanded notifications
+ +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. +
+ + +Messaging Style notification
+If you have a chat messaging app, your notifications should use +{@code Notification.MessagingStyle}, which is new in Android 6.0. Wear 2.0 uses +the chat messages included in a +{@code MessagingStyle} + notification +(see {@code addMessage()}) to provide a rich chat app-like experience in the +expanded notification. +
+ + +Smart Reply
+ +Android Wear 2.0 introduces support for Smart Reply in +{@code MessagingStyle} + notifications. Smart Reply provides the user with contextually relevant, + touchable choices in the expanded notification and in + {@code RemoteInput}. +
+ +By enabling Smart Reply for your {@code MessagingStyle} notifications, you provide +users a fast (single tap), discreet (no speaking aloud), and reliable way to respond + to chat messages they receive. +
+ + +
+
+Remote Input
+ +Wear 2.0 users can choose between various input options from +Remote Input. + These options include: +
+-
+
+For messaging notifications with Smart Reply, the system-generated Smart Reply + appears within {@code RemoteInput} + above the developer-provided list of canned responses. + You can also use the + setChoices() + method in the {@code RemoteInput} API to enable users to select from a list + of canned responses. +
+ +Bridging Mode
+By default, notifications are + +bridged (shared) from an app on a companion phone +to the watch. Since 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. + Developers can begin planning to change the behavior of notifications with the + following: +
+ +-
+
For an example of how to use this feature, see +Bridging Mode for Notifications.
+ +Input Method Framework
+ +Wear 2.0 extends the Android input method framework (IMF) to Android Wear. +This allows users to enter text on Wear using the system default IME or third party + IMEs. The Wear IME lets the user enter text via gesture typing as well as tapping + individual keys. The IMF APIs used for Wear devices are the same as other form + factors, though usage is slightly different due to limited screen real estate. +
+ +Wear provides user settings on the watch that let the user:
+-
+
To learn how to create an IME for Wear, see +Input Method Framework. +
+ +Standalone Devices
Standalone watches will enable Android Wear apps to work independently of phone - apps. This means your app can continue to offer full functionality even if the + apps. This means your app can continue to offer full functionality even if the paired phone is far away or turned off.
Wear-Specific APKs
@@ -61,7 +175,7 @@ phone app. This delivery method can result in an increased download size for use regardless of whether they have an Android Wear device. -This delivery method is planned to change; the +
With standalone devices, the Multi-APK delivery method will be used. Developers will have the ability to release Android Wear apps independently of the corresponding phone apps. Please stay tuned for @@ -136,142 +250,23 @@ advertise a capability on the phone app and retrieve the capability on the watch
Utilizing Account Manager
Android Wear will include the -AccountManager; it is planned to be accessible for syncing and storing account +AccountManager, which will be accessible for syncing and storing account data, as it is on an Android phone. - - -Notifications and Input
- -In Wear 2.0, we’ve redesigned the key experiences on the watch to be even more - intuitive and provide users new ways to respond to messages. Some of the highlights - are below; for a complete list of changes, see - Notification Changes in Wear 2.0. - -
Expanded notifications
-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. -
-
-Figure 1.An expanded notification
- -Messaging Style notification
-If you have a chat messaging app, your notifications should use -{@code Notification.MessagingStyle}, which is new in Android 6.0. Wear 2.0 uses -the chat messages included in a -{@code MessagingStyle} - notification -(see {@code addMessage()}) to provide a rich chat app-like experience in the -expanded notification. -
- - -Smart Reply
-Android Wear 2.0 introduces support for Smart Reply in -{@code MessagingStyle} - notifications. Smart Reply provides the user with contextually relevant, - touchable choices in the expanded notification and in - {@code RemoteInput}. -
- -
-
Figure 2.Messaging Style notification with smart replies
- -By enabling Smart Reply for your {@code MessagingStyle} notifications, you provide -users a fast (single tap), discreet (no speaking aloud), and reliable way to respond - to chat messages they receive. -
- - -Remote Input
---
-
-- Figure 5. Remote Input. -
- - -Wear 2.0 users can choose between various input options from -Remote Input. - These options include: -
--
-
-For messaging notifications with Smart Reply, the system-generated Smart Reply - appears within {@code RemoteInput} - above the developer-provided list of canned responses. - You can also use the - setChoices() - method in the {@code RemoteInput} API to enable users to select from a list - of canned responses. -
- -Bridging Mode
-By default, notifications are - -bridged (shared) from an app on a companiosubl apin phone -to the watch. Since 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. - Developers can begin planning to change the behavior of notifications with the - following: -
- --
-
For an example of how to use this feature, see -Bridging Mode for Notifications.
- -Input Method Framework
- -Wear 2.0 extends the Android input method framework (IMF) to Android Wear. -This allows users to enter text on Wear using the system default IME or third party - IMEs. The Wear IME lets the user enter text via gesture typing as well as tapping - individual keys. The IMF APIs used for Wear devices are the same as other form - factors, though usage is slightly different due to limited screen real estate. -
- -Wear provides user settings on the watch that let the user:
--
-
To learn how to create an IME for Wear, see -Input Method Framework. -
-User Interface Improvements
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 +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.
+
+
Complications
A complication is a feature of a watch face @@ -279,19 +274,11 @@ 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.
--
-
-- Figure 5. Watch face Complications. -
- -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, +
For examples of how to use this feature, see Watch Face Complications.
@@ -309,13 +296,13 @@ see-
+
Figure 1. Navigation and Action Drawers.
-
+
diff --git a/docs/html/wear/preview/images/expanded_diagram.png b/docs/html/wear/preview/images/expanded_diagram.png index 3d1d00702f6fc..03bca9a281915 100644 Binary files a/docs/html/wear/preview/images/expanded_diagram.png and b/docs/html/wear/preview/images/expanded_diagram.png differ diff --git a/docs/html/wear/preview/images/messaging_style_diagram.png b/docs/html/wear/preview/images/messaging_style_diagram.png new file mode 100644 index 0000000000000..3b21c79730bcc Binary files /dev/null and b/docs/html/wear/preview/images/messaging_style_diagram.png differ