Increase your app's usefulness by extending it to Android Wear devices
Android Wear integration allows you to use Google Play and Android features across devices, to create a better user experience and improve user engagement.
Why it works
Android Wear surfaces information and features at useful times so that users don't have to check their mobile devices constantly. Notifications work straight away on Wear — but, by adding actions and enhancements, you can make your app more useful and increase engagement and retention.
- Automatic notification sync, enabling users to stay up to date even when they don't have easy access to their phones.
- Voice Actions, such as "Ok Google, take a note", enable hands-free experiences for your users.
- Full support from the Android SDK, offering activities, services, sensors, and much more for custom wearable experiences.
- Data replication APIs and RPCs enable data and actions to be shared between phones and wearables.
- Watch-only apps that users can discover without a phone. Android Wear apps can access the internet directly over Bluetooth, Wi-Fi, or cellular connections, without relying on the data layer APIs. So, you can continue to offer full functionality even if the paired phone is out of range or turned off.
- Include useful information on the watch face. Use the complications data provider to deliver users useful information from your app directly to the watch face.
- Notifications layout optimized for quick and responsive messaging.
Easily get the latest data from the Google Fit platform. Simply register a
PendingIntentto be notified of changes in the fitness data store, so your app doesn't have to keep querying for changes to weight, nutrition, and other data.
- Use the navigation drawer to let users access app views or context-specific actions. You can also use a single page drawer to further simplify navigation where there are seven items or less that can be easily identified using icons. Finally, use peeking at the top of the action drawer to provide quick access to the primary action.
- Use multiple app launchers to simplify access to two or three functions. Where your app offers discrete functions—such as tracking and analyzing activity in a fitness app—this approach makes it easier for users to find and launch your app's features.
Optimize the notifications experience using the latest Wear features. Support expandable notifications with
BigTextStyle, add the notification's primary action to the collapsed view, use the
MessagingStyleto offer a rich chat app-like experience, remove any Wear 1.x text guiding users to act by swiping horizontally, and offer inline actions.
Ensure complications fit the design of the watch face and properly handle their data type. Do this by using the
TextRendererclass so text adjusts to complication bounds and the
ComplicationDrawableclass to set the background color, shape, border, and font options. Also, let users configure or adjust complications from a settings menu. When testing, use the data provider test suite app to feed dummy data to complications and remember to provide complication data with the ComplicationProviderService.
- Offer apps that work alone using the Wear built-in Wi-Fi, GPS, or other connectivity functions. Include the com.google.android.wearable.standalone flag in your app's manifest to show it can function without a companion phone. Then use the android.hardware.type.watch hardware feature flag so your app becomes searchable and installable on Wear devices.
- Avoid relying on a companion app to sign a user in. Use a web UI accessible from your wearable app for sign-in and authentication.
- Help users discover the right companion apps for your Wear app. If you have to rely on a companion app or a companion app offers extra features, use the CapabilityApi to ensure users get directed to the companion app's Play Store listing. And, remember to mention these features in your Wear app's listing.