Description of developer theme
+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.
Description of feature
+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. +
-Sample implementation of feature
+This delivery method is planned to change; 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. +
Description of feature
+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. +
+ +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:
+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. +
-Sample implementation of feature
Description of feature
+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.
-Sample implementation of feature
+For Android-paired watches (only), the phone will securely transfer authentication + data to a watch app via the + + Wearable Data Layer API. The data 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 following sections of + + Sending and Receiving Messages: +
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. + +
Description of developer theme
+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. +
+
Figure 1.An expanded notification
-Description of feature
+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. +
-Sample implementation of feature
-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}. +
-Description of feature
+
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. +
-Sample implementation of feature
-Description of feature
++ Figure 5. Remote Input. +
-Sample implementation of feature
+ +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. +
+ +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.
Description of feature
- -Sample implementation of feature
+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. +
Description of developer theme
+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. +
-Description of feature
+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.
-Sample implementation of feature
+
-+ Figure 5. Watch face Complications. +
+ -Description of feature
+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.
-Sample implementation of feature
+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. + +
-Description of feature
-Sample implementation of feature
diff --git a/docs/html/wear/preview/images/remoteinput.png b/docs/html/wear/preview/images/remoteinput.png new file mode 100644 index 0000000000000..9d8049800d630 Binary files /dev/null and b/docs/html/wear/preview/images/remoteinput.png differ