Wear OS Design Guidelines (Android Developers)
Google’s design documentation for Wear OS smartwatches.
License: Apache License 2.0 — every page footer states content is “subject to the licenses described in the Content License,” which resolves to developer.android.com/license: documentation (including this guide) is Apache 2.0, with only non-documentation site content (images, brand assets) under the separate CC BY 2.5 license — the same open-license basis already used for Material Design and Carbon Design System elsewhere in the wiki.
Key points
- UX design principles names five constraints specific to a wearable: scope an app to one or two critical tasks rather than a shrunk-down phone app; optimize for the wrist by finishing tasks in seconds, not minutes, to avoid arm fatigue; favor glanceable surfaces (complications, tiles) over full-screen apps; keep content relevant to the wearer’s current time/place/activity, since the device is worn continuously; and design for offline/slow-connection use (exercising, commuting).
- Adaptive design: principles for adding value covers scaling a layout across different watch screen sizes using percentage-based margins and established canonical layouts, so extra screen space buys more glanceable content, bigger tap targets, and clearer hierarchy rather than just whitespace.
- Common design layouts defines three canonical layout types: tiles (non-scrolling, quick access to one task), scrolling app layouts (lists, dialogs), and non-scrolling app layouts (media players, pickers, progress displays).
- Tiles frames a tile’s purpose as showing only its single most critical piece of information — “Tiles should feel focused, concise, and purpose-driven” — kept predictable (always the same user-facing task) and relevant to present context.
- Typography accessibility covers the user-configurable font-size framework (±6% increments per system setting) a layout must hold up under at both extremes, and checking contrast both between text and background and between two type styles used side by side.
- One-handed gestures covers a double-pinch “primary action” and wrist-turn “dismiss” gesture, reserved for one-and-done interruptions (answering a call, pausing media, dismissing a notification) rather than full navigation — every gesture-triggered action must also have a visible, tappable equivalent, and every recognized gesture gets immediate haptic plus visual/audio feedback.
- Preventing text truncation and clipping covers designing for the smallest supported screen (not the largest), percentage-based rather than fixed margins, keeping interactive elements scrollable fully into view, and using a compact chip instead of a card in a dense layout since a card’s larger surface makes truncation harder to avoid.
- Notifications frames a wearable notification against three questions — is it valuable enough to buzz a wrist for, is it glanceable at a scan, is it timely — and covers collapsed/expanded states across four templates (standard, big text, big picture, messaging).