Interaction types

Wear OS lets users quickly glance at information and take action. Apps, tiles, complications, notifications, and voice actions help people get things done with the watch.


Developers can create branded, engaging experiences using Wear OS apps. These apps can take full advantage of the watch's hardware capabilities to provide rich and interactive experiences.

The app is a destination where users can interact with content and complete their task. There are many entry-points to an app, including tapping on a complication, a tile, a launcher entry, and a notification.


Figure 1. The Wear OS app launcher.


Tiles provide quick access to glanceable information and actions. Users choose which Tiles they want to see and swipe to them from the watch face.

Tiles are great for use cases in which the user needs more information than can be displayed in a complication.


The user can scroll quickly through the Tiles carousel for quick access to information and actions.


Watch faces can tell more than time; they can show relevant, timely data. By including a complication, installed apps display useful information and actions, such as upcoming appointments.

People can tap to interact with complications, including tapping to learn more in the app, or tapping to change the state of the complication. For example, imagine a complication that helps track how many glasses of water you are drinking with a quick tap.


Figure 2. A watch face with data complications for an exercise and calendar app.


Notifications provide ambient, contextual data.

Notifications can be expanded to offer more interactions, such as replying to a message, opening a location on a map, or playing a song. Notification templates are available for instant messaging, and calendar events.


Figure 3. A notification in the notification stream.

Voice actions

Voice actions enable hands-free interactions with Wear OS. These actions help people answer questions and can trigger specific actions on installed apps.


Figure 4. After the user has spoken the voice command, "OK Google, show me my agenda," the query appears as text on screen.

How it all fits together

Consider prioritizing content across surfaces according to how important and frequently users need it, as demonstrated in this example weather app:


P1: What's the weather right now?


P1: Tell me about a weather advisory


P1: What's the weather right now?

P2: What's the weather today?


P1: What's the weather right now?

P2: What's the weather today?

P3: What's the hourly breakdown?

P3: Preferences