Post is pinned.
Update on 18 Jan 2018 Wear Policy Change
Back in August 2017, we announced a policy change for 18 Jan 2018 to encourage developers to build standalone Wear applications and adopt multi-APK delivery. Since then, developers reported unexpected latency between when a user installs a mobile app and when the corresponding Wear app is installed via multi-APK on Wear 1.0 devices. As a result, we are postponing the policy change related to multi-APK for Wear apps, but will go ahead with other policy updates on Jan 18.

Therefore on 18 Jan 2018, as previously announced we will:

1) remove the “Enhanced for Android Wear" badge in the Google Play Store from mobile apps that support Wear notification enhancements but do not have a separate Wear app
2) only feature apps in the Google Play Store on Wear that are standalone, i.e. Wear apps that do not require a mobile app to run.

We will, however, postpone the requirement that apps support multi-APK in order to receive the “Enhanced for Android Wear” badge. As a result, developers that bundle their Wear app with their mobile app, to support Wear 1.0 users, will continue to receive the badge for now. If your app supports both standalone and Wear 1.0 users, you will need to separately upload the Wear APK, in addition to bundling your Wear app with your mobile app.

We will continue to work on the latency issue around multi-APK delivery for Wear 1.0 devices, and will update the developer community when it is resolved. We will then proceed to remove the badge from non multi-APK apps, after a transition period, as planned.

If you have any questions or concerns, please let us know!

Post has attachment
When targeting SDK > 25, it's not possible to listen to battery charging state changes (so we can report that to the watch). Any ideas on how to overcome besides an inefficient polling? Check out my StackOverflow post for more details.

Stand alone Wear 2 apps are not found on play store on phones.

-We have published a wear 2.0 app that is stand alone - no phone app. It has been accepted for Wear OS distribution.
-It seems to work well and users can find and install from a web browser or from play store on the watch.
-However the app is not displayed on play store on android phones. You cannot search or even install from direct link.
-Google user logged into a web browser works great. It knows about your devices and allows install if you have a wear 2.0 device.
-It appears the vast majority of wear app store visits still come from app store on phone so makes it tough to get installs. (Without adding some clunky phone app that is not needed).

So is this by design at this time? If so, anywhere I could petition to have this changed? (For whatever that is worth, ha)

I want to DISABLE battery Optimization behavior in my own Android wear app.If I go to Settings Page,I am not able to find that option.

How can I achieve the Battery Optimization feature in Wear Devices?

Post has attachment
A couple of weeks ago, some you may have seen the watch face I created ahead of Google I/O. It was an unusual face to build, and I thought the folks here might like some insight into it.

If you haven't seen the face, it's a digital clock based on the animated digits used in the official I/O app. These digits had been made with Airbnb's Lottie framework, an animation tool that was built to be cross-platform, but wasn't really meant for Wear watch faces. So although I started with the example Android code on the Lottie site, I found that it didn't play well with WatchFaceService.invalidate() - the animation often wasn't fully rendered when onDraw() was called. It took some experimentation, but I eventually found that it worked much better to tie into Lottie's own AnimatorListenerAdapter, rather than using an external ValueAnimator as in their example.

The other twist was that all the digits were slightly different sizes. Apparently Lottie preserves the original size exported from After Effects (converted into dp), and whoever generated these animations hadn't been too fussy about uniform sizing. The best way I found to correct for this in my watch face was to use a simple layout (with scaleType="fitCenter") to do the dirty work of sizing them all; it avoided a bunch of messy size/scale calculations in Java.

At any rate, the code is open-source if you want to have a look. With these caveats, Lottie turns out to be a pretty solid base on which to build a watch face with complex animation, so maybe some of you will find this useful in a future project.

Hi +Hoi Lam , lately I have been getting some reports that users have to pay again in the watch play store after first buying the app on the phone. Before, a watch restart always fixed this, but in these cases it does not help. What could be going on here? And is there a workarround somehow?

And syncing of the app to wear 1.x watches still takes about a day in some cases. Have you guys been able to figure out what was/is going on there?


Hey guys, I have a Huawei watch 2, with built in GPS. I often go running with the watch alone, but I want my wife to be able to see where I am. Bear in mind that I am without internet when I go running. Is there any app to help?

Post has attachment
My first standalone Wear OS watch face and launcher widget. These are real pictures of old hubcaps taken out in the desert where I live. I would appreciate any feedback. Thanks!

Post has attachment
OK. Is this normal? ===> Android-Version: 9

Post has attachment
How I get voice input on Wear OS without interrupting the app flow. I'll have a keyboard input part later. What are some other ways to get input quickly?
Wait while more posts are being loaded