-
-
- Expanded Notification -
- Messaging Style Notification +
- Expanded Notifications +
- Messaging Style Notifications +
- Inline Action
- Smart Reply -
- Notification Content Action
- Remote Input
- Bridging Mode
- Input Method Framework @@ -40,308 +41,447 @@ page.image=images/cards/card-n-apis_2x.png +
- A curved layout on round devices + -
- A circular scrolling gesture, which can be toggled on and off + +
- 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. -
- Dictation + -
- Emoji + -
- Canned responses + -
- Smart Reply + -
- 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. -
- Default IME + +
- Flick wrist out -
- Flick wrist in -
- 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. + +
- -JobScheduler for asynchronous jobs, including polling at regular intervals - -
- Multi-networking APIs if you need to connect to specific network types; see -the -Multiple Network Connections - -
- Flick wrist out + -
- Flick wrist in + +
- Advertise Capabilities -
- Retrieve the Nodes with the Required Capabilities -
- + JobScheduler + for asynchronous jobs, including polling at regular intervals + + +
- Multi-networking APIs, to connect to specific network + types; see Multiple Network + Connections + +
- Advertise Capabilities + + +
- Retrieve the Nodes with the Required Capabilities + +
- Set Up a Watch - +
- + Set Up a Phone +
- Set Up an Emulator @@ -180,7 +182,7 @@ This is the Android Wear SDK Preview License Agreement (the “License Agreement
+ Wear 2.0 is still in active development, but you can try it as part of + the Wear 2.0 Developer Preview. The sections below highlight some of the + new features for developers. +
++ User Interface Improvements +
-- The Android Wear Preview API is still in active development, but you can try - it now as part of the Wear 2.0 Developer Preview. The sections below - highlight some of the new features for Android Wear developers. -
++ The preview introduces powerful additions to the user interface, opening + up exciting possibilities to developers. +
++ Complications +
-User Interface Improvements
+
+ + 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 thus + helps watch face developers create visual features and the data + connections they require. +
-- 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. -
++ 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 information about this API, see Watch Face + Complications. +
-Complications
-
+ + Navigation and Action Drawers +
-- 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 thus helps watch face - developers create visual features and the data connections they - require. -
++ 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. +
-- 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. -
+ -Navigation and Action drawers
++ To learn how to add these widgets to your app, see Wear Navigation and + Actions. +
-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. -
++ Curved Layout +
-
- 
-
+ Wear 2.0 introduces the WearableRecyclerView class for
+ displaying and manipulating a vertical list of items,
+ optimized for round displays.
+
- To learn how to add these widgets to your app, see - - Wear Navigation and Actions. -
++ The key features include the following: +
+-
+
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. +
+ To learn how to create a curved layout optimized for round devices, see + + Curved Layout. +
++ Notifications and Input +
-
-Expanded notifications
+
+ 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.
+
- 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. -
++ 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. -
++ Messaging Style Notifications +
++ 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
++ Inline Action +
-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}. -
++ Wear 2.0 enables you to add an inline action within the notification + stream so that users can quickly take an action on a notification. + Examples of good use cases for an inline action within a notification stream + include replying to a text message, stopping a fitness activity, or + archiving an email message. +
-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. -
++ To learn how to add an inline action to your notification stream, see + + Inline Action. +
++ 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}. +
-Remote Input
++ 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. +
-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. -
++ Remote Input +
-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: -
++ Wear 2.0 users can choose between various input options from Remote Input. + These options include: +
--
-
-
+
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. -
++ 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. +
-Wrist Gestures
++ Bridging Mode +
-- Wrist gestures can enable quick, one-handed interactions with your app - when use of a touch screen is inconvenient. The following - wrist gestures - are available for use by apps: -
++ 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. +
--
-
+ For information about this feature, see Bridging Mode for + Notifications. +
-For more information, see - - Wrist Gestures. -
++ Input Method Framework +
-Standalone Devices
++ 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. +
-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 - paired phone is far away or turned off.
++ Wear provides user settings on the watch that let the user: +
-Wear-Specific APKs
+-
+
For delivery to a watch, an Android Wear app is currently embedded in its corresponding -phone app. This delivery method can result in an increased download size for users, - regardless of whether they have an Android Wear device. -
+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 - more information about this change. -
+Network Access
++ To learn how to create an IME for Wear, see Input Method Framework. +
-Since Android Wear apps will work independently of phone apps, Android Wear's - network access will no longer require the - - Wearable Data Layer API. Android Wear apps will have the ability to make - their own network requests. Additionally, they will be able to directly use - Google Cloud Messaging. -
++ Wrist Gestures +
-No APIs for network access or GCM are specific to Android Wear; refer to the -existing documentation about - -Connecting to the Network and -Cloud Messaging. -
++ Wrist gestures can enable quick, one-handed interactions with your app + when use of a touch screen is inconvenient. The following wrist + gestures are available for use by apps: +
-We recommend using the following libraries:
--
-
-
+
You will still be able to use the - - Wearable Data Layer API to communicate with a phone app. - However, use of this API to connect to a network will be discouraged. -
++ For more information, see Wrist Gestures. +
-Authentication
++ Standalone Devices +
-Since Android Wear apps will work independently of phone apps, Android Wear's - authentication capabilities will be more powerful; apps will have new ways to - authenticate.
++ Standalone watches enable Android Wear apps to work independently of + phone apps. This means your app can continue to offer full functionality + even if the paired phone is far away or turned off. +
-Users can enter a username and password on a watch
++ Wear-Specific APKs +
-Google Keyboard will be standard on Android Wear, allowing for direct text -entry. This feature will work as expected with standard -EditText widgets. -For passwords, the {@code textPassword} attribute will be used.
++ For delivery to a watch, an Android Wear app is currently embedded in its + corresponding phone app. This delivery method can result in an increased + download size for users, regardless of whether they have an Android Wear + device. +
-Utilizing Account Manager
++ For information about planning and building your standalone app + for Wear 2.0, see + Standalone Apps. +
-Android Wear will include the - -AccountManager, which will be accessible for syncing and storing account -data, as it is on an Android phone.
++ For information about distributing your app, see + App Distribution. +
-Authentication tokens can be passed over the Wearable Data Layer
++ Network Access +
-For Android-paired watches (only), a phone securely -transfers authentication credentials to a watch app via the - -Wearable Data Layer API. The credentials can be transferred as -messages or data items.
++ Since Android Wear apps will work independently of phone apps, Android + Wear's network access will no longer require the Wearable Data Layer + API. Android Wear apps will have the ability to make their own + network requests. Additionally, they will be able to directly use Google + Cloud Messaging. For more information, see + + Network Access and Cloud Messaging. +
-If your watch app needs to determine if your phone app is installed, you can -advertise a capability on the phone app and retrieve the capability on the -watch. For more information, see the following sections of - -Sending and Receiving Messages:
++ No APIs for network access or GCM are specific to Android Wear; refer to + the existing documentation about Connecting to the + Network and Cloud Messaging. +
--
-
+ We recommend using the following libraries: +
+ +-
+
+ The Wearable Data Layer + API is available to communicate with a phone app. + However, use of this API to connect to a network will be discouraged. +
+ ++ Authentication +
+ ++ Since Android Wear apps will work independently of phone apps, Android + Wear's authentication capabilities will be more powerful; apps will have + new ways to authenticate. +
+ ++ Users can enter a username and password on a watch +
+ ++ Google Keyboard will be standard on Android Wear, allowing for direct + text entry. This feature will work as expected with standard EditText widgets. + For passwords, the {@code textPassword} attribute will be used. +
+ ++ Utilizing Account Manager +
+ ++ Android Wear will include the AccountManager, + which will be accessible for syncing and storing account data, as it is + on an Android phone. +
+ ++ Authentication tokens can be passed over the Wearable Data Layer +
+ ++ For Android-paired watches (only), a phone securely transfers + authentication credentials to a watch app via the Wearable Data Layer + API. The credentials can be transferred as messages or data items. +
+ ++ If your watch app needs to determine if your phone app is installed, you + can advertise a capability on the phone app and retrieve the capability + on the watch. For more information, see the following sections of + Sending + and Receiving Messages: +
+ +-
+
Invalid Fields for a Complication Type
+ +
+ When a watch face uses the
+ Complications API, the watch face requests data from a chosen provider.
+ A ComplicationData object, which contains
+ complication types, is returned.
+
+ A complication type determines the
+ kinds of data that a watch face can render. This section describes
+ a behavior change related to the ComplicationData object.
+
+ Starting with
+
+ Developer Preview 3, when a watch face requests a field that is invalid
+ for a complication type, a default value for the field is returned.
+ For example, if a watch face tries to access a Long text
+ field in a SHORT_TEXT type, the default value for the
+ Long text field is returned.
+ In previous releases, such a request for an invalid field
+ (for a type) resulted in an exception.
+
Complication Types for Empty Data
+ +
+ Starting with
+
+ Developer Preview 3, the complication types used for "empty" data are
+ changed. Apps that use the Complications API
+ may need to be updated to use
+ TYPE_NO_DATA. See the information
+ about TYPE_NO_DATA in the
+
+ Types and fields section.
+
- You can run and test your app with the Android Wear 2.0 Developer Preview + You can run and test your app with the Android Wear 2.0 Preview in either of these ways:
@@ -237,6 +239,13 @@ This is the Android Wear SDK Preview License Agreement (the “License Agreement following tables and flash it to the corresponding device. +Caution: + After you flash an image to a watch, follow the steps for + setting up a phone with the beta version of + the Android Wear companion app. To use a Wear 2.0 image on a watch, + you must have the beta companion app on a paired phone. +
+To restore your device to its original state during the preview, you can flash the appropriate retail system image, below, to the device. @@ -266,9 +275,9 @@ This is the Android Wear SDK Preview License Agreement (the “License Agreement
- MD5: dd351884cce9fb5bf1bdec0a8e5f56e3
- SHA-1: 48ac950c48faef96a7770e3c1acb56d23a28d859 +
+ MD5: ddfccc3e050c7e2db8d657c82f7d6291
+ SHA-1: 302a33eac348c401fcb165bad4b9aaa40c7beb2b
- MD5: 0b8ba3653d5a93cb854f4d7409d7b6c9
- SHA-1: fa528bec8aba3bf6c7d901ba63cd6ea0a08dbeb0 +
+ MD5: f3a0090c0e99da82ad095b5d2a9acc6d
+ SHA-1: 3faf6f2d7f422a17a5f6c54cf5e1d2c5622689b0
- MD5: 38c1047992b1d28f6833d9f6c8470cdc
- SHA-1: cb5a11ab0260ea3ca7da5894e73e41f70357da6b +
+ MD5: f78ac6ba8bb84038d163cc2d7ca85040
+ SHA-1: 6607cd31858af1bfd50b905c68f7cf1f0b6e570e
- MD5: 417b5cbddb29a2262bce133e283d2732
- SHA-1: 4800307843580f818557dd7c43d8ba2161e289b2 +
+ MD5: 12ce6cb0b0e43b67ea46a886eae052ae
+ SHA-1: e659286aa9004f4555a476ede4e8b690f56cfefd
- Set up the watch and begin testing + Set up the watch
After the flash-all script finishes, your watch reboots.
- Pair the watch with a phone or tablet. The preview now is available
- for testing on the watch. Before installing an app, perform the
+ Only pair the watch with a phone (so you can begin testing the preview)
+ by using the instructions in Set Up a Phone.
+ Additionally, before installing an app, perform the
following steps on the watch to re-secure the watch's bootloader:
- Your watch is ready for you to Set Up a Phone, + your watch will be ready for you to install and run your app:
@@ -539,6 +551,97 @@ This is the Android Wear SDK Preview License Agreement (the “License Agreement device reset and removes all user data on the device. ++ Set Up a Phone +
+ ++ On a phone, follow the instructions in this section to install the beta + version of the Android Wear companion app. The beta version cannot be run + on a phone at the same time as the non-beta version. Additionally, the + beta version is English-only. +
+ ++
Caution: If you have an existing + pairing of the phone to a Wear 1.x + watch, installation of the beta companion app will cause a loss of that + pairing. +
+ ++ Join the Wear 2.0 preview group +
+ ++ To access the beta companion app, you must join + the preview group in Google Groups. +
+ ++ Opt in for beta testing +
+ ++ On the Testing + Opt-in page, select Become a Tester. +
+ ++ Download and install the beta version of the companion app +
+ ++ On the Play Store on your phone, go to the + Android Wear app listing. Tap Update to download and + install the beta version of the app. After installation, confirm that + Auto-update is selected for the app (see + the "Set up automatic updates for specific apps" section of Update downloaded + apps). Tap Open to start the app. +
+ ++ Pair the phone to the watch +
+ ++ After you install the beta version of the companion app on a phone, + you can pair the phone to the watch: +
+ +-
+
- On the phone, select your device name from the list of devices. + A pairing code is displayed on the phone and on the watch. + Ensure that the codes match. + + +
- Tap Pair to + continue the pairing process. When the watch is connected to + the phone, a confirmation message is displayed. + On the phone, a screen is displayed that lists + the accounts on the phone. + + +
- Choose a Google account to add and sync to your watch. + + +
- Confirm the screen lock and enter the password to start the copying of + the account from the phone to the watch. + + +
- Follow the instructions in the wizard to finish the + pairing process. + +
+ You can begin testing your app with the preview. +
+