0

So I made a watchface and I would like to put it on the Play Store. I partly did. When I go to the App page in Play Store with my phone it says my device is not compatible. I know this is because it states so in the Manifest.

Usualy I browse the Play Store on my phone for watch faces, install the one I like and it ends up on my watch (without a companion app on the phone).

So what changes do I need to do to make it installable over the Phone. What can I deliver to make you helping me easier?

Dimi Scha
  • 13
  • 2

1 Answers1

1

I assume that your watch face is a standalone app, i.e. it doesn't require an app to also be installed on the phone. If you're not sure take a look at the "Specify an app as standalone" section in the documentation.

Standalone apps for Android Wear 2.x and above (this includes Wear OS) can't be installed via the phone. You have two options:

  1. Use the Play Store app on the wearable device
  2. Go to the Play Store desktop website and select your wearable device as the install target

In other words, what you're experiencing is the expected behavior.

If you really want your app to be installed from a phone (or if you're targeting Android Wear 1.x) it has to have a phone app. From the documentation:

For Wear 2.0

On devices running Wear 2.0, when a user installs a phone app that has an associated watch app (either an embedded APK or an APK uploaded via the Play Console), the user gets a watch notification about the available watch app. Tapping the notification opens the watch Play Store, giving the user the option to install the watch app.

For Wear 1.0

Wear OS now allows you to distribute your Wear app the same way for both Wear 1.0 and 2.0. When a user installs your phone app, if you have a compatible Wear app in the Play Store, it will automatically be installed on Wear 1.0 watches.

However, I strongly advice against doing this for the sole purpose of discoverability on the phone.

TofferJ
  • 4,678
  • 1
  • 37
  • 49
  • Thanks for the clarification. I already asumed it is expected behavior. Why would you advise against making it Wear 1.0 compatible. I personaly find it very uncofortable to browse the play store on my watch. – Dimi Scha Feb 08 '19 at 06:17
  • I don't advice against making it Wear 1.0 compatible. I advice against adding a phone app for the sole purpose of having the app show up in the Play Store phone app for Wear 2.0 users. There are a few reasons for this: 1) Users might expect the phone app to actually add functionality. 2) It's a waste of data (downloading it) and space (storing it). 3) It might be a waste of your time since Wear 2.0 users are most likely already used to finding content through Play Store on the wearable. – TofferJ Feb 08 '19 at 19:45
  • Okay, I'll leave it as it is. Altough I still would like to know how to wrap my wearable app in an phone app. Would I need to start a new project for a phone app without any activities and then only refernece my werable app in the dependencies? If so then how exactly would I do this, how do I define the path and to what, the APK? – Dimi Scha Feb 11 '19 at 06:14
  • Never mind. I read the documentation so often and got lost in the first parts, that I never realized it is all mentioned further down on the page you linked. And in Android Studio there is an option to pair the watchface with an empty phone app. Thank you again for your time. – Dimi Scha Feb 12 '19 at 13:04