The default recommendation is for a Wear OS app to work independently of a phone so users can complete tasks on a watch, without access to an Android or iOS phone. However, if you app requires a phone interaction for the watch app to function, you must mark your Wear OS app as dependent.
Plan your app
You can use Android App Bundle to automatically generate optimized APKs for each user’s device configuration under the same application listing. This allows users to download only the code and resources they need to run your app.
Generally, the minimum API level for a Wear OS app is API level 25 (Wear OS 2.0).
The target API level must be API level 28 or higher
(read more), we recommend setting
targetSdkVersion to API level 30 (Wear OS 3) to ensure that your app works well
on the latest platform version.
For information about network requests and high-bandwidth network access, see Network access and sync on Wear OS.
Define an app as a Wear OS app
You must define the
<uses-feature> tag in the Android Manifest file in your app.
For example, indicate that it is a watch app, as shown in the following example:
<manifest> ... <uses-feature android:name="android.hardware.type.watch" /> ... </manifest>
Identify an app as standalone
Wear OS apps must set the
in the Android manifest file.
The element indicates whether your watch app is a standalone (independent) app that doesn't
require another device to operate for core functionality. In this case you need to set the
setting for the element to
A watch app can be considered as one of the following:
- Standalone: completely independent app that does not require a phone app for core features including authentication; a phone app would provide only optional features.
- Non-standalone: dependent app that requires a phone app or another device for core features including authentication.
If a watch app is completely independent, it is in the standalone category. You must indicate
this categorization to the Google Play store by setting the
value of this
meta-data element to
<application> ... <meta-data android:name="com.google.android.wearable.standalone" android:value="true" /> ... </application>
If a watch app is non-standalone, set the value of the above
meta-data element to
false. Setting the element
false signifies that the watch app requires another device, but it won't
affect your app promotion on the Google Play Store.
Even if the value is
false, the watch
app can be installed before the phone app is installed.
Therefore, if a watch app
detects that a companion phone
lacks a necessary phone app, the watch app should
prompt the user to install the phone app.
Shared code and data storage
Code can be shared between a Wear OS app and a phone app. Optionally, code that is specific to a form factor can be in a separate module.
For example, common code for networking can be in a shared library.
Detect your app on another device
Your watch app can detect if the corresponding phone app is available and vice versa.
Your phone app or watch app can use the
CapabilityClient to advertise the app's presence
to a paired device. It can do so statically and dynamically. When an app
is on a node in a user's Wear OS network (such as on a phone, paired watch, or
in the cloud), the
CapabilityClient enables another
app to detect if it is installed. For more information, see
If one of your apps cannot detect the other, you can enable a user to open the Play Store listing on their remote device. This is a solution for watch apps that require their companion phone app's presence to function properly. A prerequisite is to check for the Play Store's presence on the remote device.
Note that not all phones support the Play Store (such as iPhones, etc.).
This section describes best practices for these scenarios:
- Your standalone watch app needs your phone app
- Your phone app needs your standalone watch app
sample on GitHub that shows this functionality. For more information
about the classes described below, see the
Wear OS API reference.
Also in that reference is information about the
PhoneDeviceType class, which contains a
getPhoneDeviceType() method that enables your
Wear OS app to check if a companion phone is an Android or iOS device.
Specify capability names for detecting your apps
For the app corresponding to each device type (watch or phone), specify a
unique string for the capability name in the
For example, in your mobile module, the
could include the following:
<resources xmlns:tools="http://schemas.android.com/tools" tools:keep="@array/android_wear_capabilities"> <string-array name="android_wear_capabilities"> <item>verify_remote_example_phone_app</item> </string-array> </resources>
In your Wear OS module, the
wear.xml file would include a
different value for the capability name,
such as the following:
<resources xmlns:tools="http://schemas.android.com/tools" tools:keep="@array/android_wear_capabilities"> <string-array name="android_wear_capabilities"> <item>verify_remote_example_wear_app</item> </string-array> </resources>
For more information, see Advertise capabilities.
App detection and opening a URL from a watch
Your watch app can detect if a user's companion phone has your phone app:
CapabilityClientto check if your phone app is installed on the paired phone. For more information, see the sample on GitHub.
If your phone app isn't installed on the phone, use the
PhoneDeviceType.getPhoneDeviceType()method to check the type of the phone.
PhoneDeviceType.DEVICE_TYPE_ANDROIDis returned, the phone is an Android phone. Call
RemoteActivityHelper.startRemoteActivity()on the Wear OS device to open the app store on the phone. Use the market URI for your phone app (which may be different from your phone URI). For example, use a market URI such as:
PhoneDeviceType.DEVICE_TYPE_IOSis returned, it means the phone is an iOS phone (with no Play Store available). Open the App Store on the iPhone by calling
RemoteActivityHelper.startRemoteActivity()on the Wear device. You can specify your app's iTunes URL, for example,
https://itunes.apple.com/us/app/yourappname. On an iPhone, from Wear OS, you cannot programmatically determine if your phone app is installed. As a best practice, provide a mechanism to the user (e.g., a button) to manually trigger the opening of the App Store.
Note that using the
RemoteActivityHelper API described above,
you can specify that any URL be opened on the phone from the watch,
and no phone app is required.
Details for detecting the type of paired phone
Here is a snippet that uses the
method to check the type of phone to which the watch is paired:
var phoneDeviceType: Int = PhoneDeviceType.getPhoneDeviceType(context)
int phoneDeviceType = PhoneDeviceType.getPhoneDeviceType(context);
The value returned by the
method is one of the following:
||The companion phone is an Android device.|
||The companion phone is an iOS device.|
||An error occurred in determining the type of the paired phone; another check should be made later.|
App detection starting from an Android phone
Your Android phone can detect if a user's Wear OS devices have your watch app:
NodeClient, find all watches connected to the user's phone. For more information, see the sample on GitHub.
CapabilityClient, check which of the user's watches have your app installed.
If your app isn't installed on all of the user's watches (compare the
results from Step 1 with the results from Step 2), allow the user to
open the Play Store on the remaining Wear OS devices from the phone via
RemoteActivityHelper.startRemoteActivity()method. Specifically, use the market URI for the Wear OS app (which may be different from your phone app's URI). For example, use a market URI such as:
Location data for watches paired to iPhones
If the companion phone is available, FLP uses the companion phone for location data.
Obtain only the necessary data
Generally, when obtaining data from the internet, you should get only the necessary data. Otherwise, you may introduce unnecessary latency, memory use, and battery use.
When a watch is connected over a Bluetooth LE connection, your app may have access to a bandwidth of only 4 kilobytes per second, depending on the watch. Therefore, the following steps are recommended:
- Audit your network requests and responses for extra data that only is for a phone app
- Shrink large images before you send them over a network to a watch
For cases where a high-bandwidth network is needed, see High-bandwidth network access.
Additional code samples
The WearVerifyRemoteApp sample further demonstrates the use of the APIs covered on this page.