Creating Wearable Apps

Wearable apps run directly on the device, giving you access to hardware such as sensors and the GPU. They are fundamentally the same as apps built for other devices using the Android SDK, but differ greatly in design and usability and the amount of functionality provided. These are the main differences between handheld and wearable apps:

• Wearable apps are relatively small in size and functionality compared to handheld apps. They contain only what makes sense on the wearable, which is usually a small subset of the corresponding handheld app. In general, you should carry out operations on the handheld when possible and send the results to the wearable.
• Users don't download apps directly onto the wearable. Instead, you bundle the wearable app inside the handheld app. When users install the handheld app, the system automatically installs the wearable app. However, for development purposes, you can still install the wearable app directly to the wearable.

• Wearable apps can access much of the standard Android APIs, but don't support the following APIs:

  • android.webkit
  • android.print
  • android.app.backup
  • android.appwidget
  • android.hardware.usb

  You can check if a wearable supports a feature by calling hasSystemFeature() before trying to use an API.

To conserve power on a wearable device, you can enable ambient mode for your Wear app. Devices transition from interactive to ambient mode when the user is idle on an activity or when the user covers the screen with their palm. Wearable apps that can transition into ambient mode are called always-on apps. The following describes the two modes of operation for always-on apps:

Interactive

Use full color with fluid animation in this mode. The app is also responsive to input.

Ambient

Render the screen with grayscale graphics and do not present any input cues in this mode. This display mode is only supported on devices running Android 5.1 or higher.

On devices running versions prior to Android 5.1 or for apps that do not support ambient mode, when a user is idle on an activity or when the user covers the screen with their palm on an activity, the Wear home screen is displayed instead of your activity in ambient mode. If you need to show persistent content on versions prior to Android 5.1, create a notification in the context stream instead.

Note: We recommend using Android Studio for Android Wear development as it provides project setup, library inclusion, and packaging conveniences that aren't available in ADT. The rest of this training assumes you're using Android Studio.

Lessons

Creating and Running a Wearable App

Learn how to create an Android Studio project that contains both the wearable and handheld app modules and how to run the app on a device or emulator.

Creating Custom Layouts

Learn how to create and display custom layouts for notifications and activities.

Keeping Your App Visible

Learn how to enable ambient mode for your apps, so they remain visible while still saving battery power.

Adding Voice Capabilities

Learn how to launch an activity with voice actions and how to start the system speech recognizer app to obtain free-form voice input.

Packaging Wearable Apps

Learn how to package a wearable app inside a handheld app. This allows the system to install the wearable app automatically when users install the companion handheld app from the Google Play store.

Debugging over Bluetooth

Learn how to debug your wearable over Bluetooth instead of USB.