Skip to content

Most visited

Recently visited

navigation

Support and Release Notes

Important: The Wear 2.0 preview is over. Please see the main Android Wear documentation.

General Advisories

The developer preview is for app developers and other early adopters and is available for daily use, development, or compatibility testing. Please be aware of these general notes about the release:

Platform API Version

The Android Platform API version is incremented to 25 to match Android 7.1.1. You can update the following in your Android Wear 2.0 Preview project to 25:

Deprecations

See Deprecated Classes. Additionally, the following fields are deprecated in the preview:

Developer Preview 5

Date: January 2017
Builds: Wearable Support 2.0.0-beta2, NVF41U
Emulator support: x86 & ARM (32-bit)

New in Preview 5

System images for Preview 5 are the same images as those for Preview 4; see Download and Test with a Device.

Companion app for iPhones

An iOS companion app is available for Preview 5. The phone on which the app is installed must be running iOS 10 or higher and cannot be running iOS 10.0.1. The companion app may omit some watch face preview images. To test Preview 5 with the iOS companion app:

  1. Set up a watch with the Android Wear 2.0 preview image.
  2. On your iPhone, visit the App Store and download the Android Wear app. Install the app on your iPhone.
  3. Follow the instructions on the watch and on the phone to begin the pairing process. For additional information, see the related Help page.

Updates to the Wear Support Library

As part of Preview 5, the Wear Support Library is updated. Before submitting your Wear app to the Play Store, complete the following steps:

  1. In Android Studio, confirm that the Google Repository is the latest version.
  2. In the dependencies section of your build.gradle file, update the compile line with a reference to: 'com.google.android.support:wearable:2.0.0-beta2'
  3. Recompile your project in Android Studio.

Near Field Communication (NFC)

NFC is supported in Wear 2.0. For example, you can use it for Android Pay. On Android Wear, only HCE mode is supported (not Reader/writer mode or P2P mode). Additionally, Wear devices do not support the system feature FEATURE_NFC, but do support FEATURE_NFC_HOST_CARD_EMULATION. To use NFC, see Near Field Communication.

Additions for the Complications API

Preview 5 contains a ProGuard configuration that prevents complication classes from being obfuscated. This fixes an issue where a ClassNotFoundException was thrown for classes that otherwise were stripped from a build.

Known Issues

Also review the Preview 4 Known Issues because the system images for Preview 5 are the same as those for Preview 4.

iPhone issues

Developer Preview 4

Date: December 2016
Builds: Wearable Support 2.0.0-beta1, NVF41U
Emulator support: x86 & ARM (32-bit)

New in Preview 4

For access to system images and the companion app for Preview 4, see Download and Test with a Device.

General additions for standalone apps

For information about planning your Wear 2.0 app, see the latest updates to Standalone Apps.

As stated in earlier preview releases, Wear 2.0 apps can directly use Firebase Cloud Messaging (FCM), which replaces Google Cloud Messaging (GCM). Please also note that FCM is supported on Wear 2.0, but GCM is not supported on Wear 2.0.

Additions for the Play Store on Wear

For information about distributing your Wear 2.0 app, see the latest updates to App Distribution.

Note that starting with Developer Preview 4, when a user installs a phone APK that has an embedded watch APK, the user is notified on the watch that the watch APK can be installed.

Authentication in Wear 2.0

For information about Authentication methods supported in Wear 2.0, see Authentication in Wear.

Additions and changes for notification bridging

For additions and changes related to the bridging of notifications from a companion app to a watch, see Bridging Mode for Notifications.

Reintroduction of swipe-to-dismiss

Starting with Developer Preview 4, Android Wear 2.0 is reintroducing swipe-to-dismiss. For more information, see Reintroduction of Swipe-to-Dismiss.

Power button behavior is changed

Starting with Developer Preview 4, the power (hardware) button is not a back button, nor is it usable for general navigation. For more information, see Power Button Returns to the Watch Face.

Deprecated classes

For information about deprecated classes, see Behavior Changes.

Updates to navigation and action drawers

For more updates related to navigation and action drawers, see Navigation and Actions.

Additions for curved layouts

For updates related to curved layouts for round devices, see Curved Layout.

In-app Billing

In-app Billing is available for Wear apps, including watch faces. Your users can authorize a purchase quickly and easily on a watch using a 4-digit Google Account PIN. However, support for setting up subscriptions is not available at this time.

Additions to the Complications API

For Preview 4, additions and changes have been made to the Complications API. Please see the documentation for more information about the following:

Known Issues

Notifications

Play Console

Smart Reply

Wearable Navigation and Action Drawers

Play Store app

Other known issues

Developer Preview 3

Date: September 2016
Builds: Wearable Support 2.0.0-alpha3, NVE68J
Emulator support: x86 & ARM (32-bit)

New in Preview 3

For access to system images and the companion app for Preview 3, see Download and Test with a Device.

Additions for standalone apps and the Play Store on Wear

For information about planning your Wear 2.0 app, see Standalone Apps.

Generally, the minimum and target SDK level for Wear 2.0, and for a standalone APK, is level 24. The minimum SDK level can be 23 only if you are using the same APK for Wear 1.0 and 2.0 (and thus have an embedded Wear 1.0 APK).

Run-time permissions are required.

For information about distributing your Wear 2.0 app, see App Distribution.

Complications API additions

For Preview 3, additions and changes have been made to the Complications API. The documentation includes information about the following additions and changes:

For changes related to the ComplicationData object, see Behavior Changes.

Curved Layout

For information about creating a curved layout using the WearableRecyclerView API in your Wear 2.0 app, see Curved Layout.

Notifications features

To learn about adding an inline action to a notification, see Inline Action.

To learn about adding images to a notification, see Adding images to a notification.

For additions related to the bridging of notifications from a companion app to a watch, see Bridging Mode for Notifications.

Smart Reply additions

Smart Reply responses are generated by an entirely on-watch, machine-learning model using the context provided by MessagingStyle notifications. Use the setAllowGeneratedReplies(boolean) method to enable Smart Reply for your MessagingStyle notification.

Known Issues

Notifications

Companion app

Play Console

System user interface and apps

Account sync

Devices

Smart Reply

Developer Preview 2

Date: July 2016
Builds: Wearable Support 2.0.0-alpha2, NVD83H
Emulator support: x86 & ARM (32-bit)

New in Preview 2

Wearable drawers

The following are feature additions for wearable drawers:

Wrist gestures

Wrist gestures can enable quick, one-handed interactions with your app. For example, a user can scroll through notifications with one hand while holding a cup of water with the other. For more information, see Wrist Gestures.

Known Issues

Notifications

Complications

System User Interface

Companion App

Devices

Developer Preview 1

Date: May 2016
Builds: Wearable Support 2.0.0-alpha1, NVD36I
Emulator support: x86 & ARM (32-bit)

Known Issues

Notifications

Complications

System User Interface

Companion App

Devices

This site uses cookies to store your preferences for site-specific language and display options.

Hooray!

This class requires API level or higher

This doc is hidden because your selected API level for the documentation is . You can change the documentation API level with the selector above the left navigation.

For more information about specifying the API level your app requires, read Supporting Different Platform Versions.

Take a one-minute survey?
Help us improve Android tools and documentation.