Android Wear 2.0, the significant upgrade for Google’s wearable OS that was revealed at Google I/O this past May, formally got pushed back to “mid-2017” at the beginning of today. At the point when initially declared, Google guaranteed that Android Wear 2.0 would dispatch this fall, yet since Google I/O, we truly haven’t heard much for when we ought to hope to see it rollout. While the news of it being pushed back is unquestionably a killjoy, there is a silver covering.
Reported early today, Android Wear 2.0 will include access to a select segment of Google Play, cooked particularly to smartwatch applications. With this, clients can peruse and download applications straightforwardly from their smartwatch, without browsing from a desktop or cellular telephone.
Google took, this time, to detail the “coolest” component of Google Play on Android Wear.
If users want an app on their watch but not on their phone, they can install only the watch app. In fact, in Android Wear 2.0, phone apps are no longer necessary. You can now build and publish watch-only apps for users to discover on Google Play.
Close by the deferral, Google has distributed the third Developer Preview for Android Wear 2.0, downloadable right now for any invested individuals.
Designer Preview 3 includes the accompanying changes.
Complications improvements: Starting with Developer Preview 3, watch face developers will need to request RECEIVE_COMPLICATION_DATA permission before the watch face can receive complication data. We have added
ComplicationHelperActivityto make this easier. In addition, watch face developers can now set default complications, including a selection of system data complications which do not require special permission (e.g. battery level and step count), as well as data providers that have whitelisted the watch face.
- New WearableRecyclerView: This new UI component helps developers display and manipulate vertical lists of items while optimizing for round displays.
Inline Action for Notifications: A new API makes it easy to take action on a notification right from the stream. Developers can specify which action is displayed inline at the bottom of the notification by calling
Smart Reply: Android Wear now generates Smart Reply responses for
MessagingStylenotifications. Smart Reply responses are generated by an entirely on-watch machine learning model using the context provided by the
MessagingStylenotification, and no data is uploaded to the cloud to generate the responses.
- And much more: Read about the complete list of changes in the Android Wear developer preview release notes.