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!
Shared publiclyView activity