Skip to main content
Technology & EngineeringAndroid Kotlin30 lines

Wear OS Compose, Tiles and Complications

Design and validate a glanceable Wear OS feature across Compose app screens, Tiles and watch face complications. Use when choosing surfaces, navigation, data updates, or representative watch tests.

Quick Summary10 lines
Pick a user task and decide what a two-second glance should convey. A single value users check repeatedly suits a complication when supported by the watch face. A compact summary with one next action fits a Tile. A Compose app screen can handle richer navigation, settings and detail. Use the official implementation model for each surface: Tiles use ProtoLayout and Tiles APIs, rather than sharing a Compose UI tree with the app.

## Key Points

- [Wear OS interface surfaces](https://developer.android.com/training/wearables/user-interfaces)
- [Wear OS Tiles and ProtoLayout](https://developer.android.com/training/wearables/tiles)
- [Wear OS power guidance](https://developer.android.com/training/wearables/apps/power)
- [Wear OS accessibility guidance](https://developer.android.com/training/wearables/accessibility)
skilldb get android-kotlin-skills/wear-os-compose-tiles-complicationsFull skill: 30 lines
Paste into your CLAUDE.md or agent config

Wear OS Compose, Tiles and Complications

Pick a user task and decide what a two-second glance should convey. A single value users check repeatedly suits a complication when supported by the watch face. A compact summary with one next action fits a Tile. A Compose app screen can handle richer navigation, settings and detail. Use the official implementation model for each surface: Tiles use ProtoLayout and Tiles APIs, rather than sharing a Compose UI tree with the app.

Share state without multiplying work

Keep a shared local snapshot with the value, freshness, identity and access state each surface is allowed to display. Consider a weather feature: the complication shows the current temperature, the Tile adds the short forecast, and the app presents hourly detail and location settings. Read the same cached data on all three surfaces. Give the Tile and complication explicit stale, signed-out and offline display states. Avoid a per-surface polling loop. Choose refresh behavior according to the source's actual update cadence, scheduling rules and battery cost.

Make a Tile or complication action route to a meaningful in-app destination. The destination must validate the current account, permission and entity again before showing private information or acting. A stale action needs a recovery screen. Keep protected or personal values out of shared glanceable surfaces when current device or account state does not permit them. Exercise changes in watch/phone connectivity for companion apps and retain a usable state during disconnect.

Verify the watch as a distinct device

Start with a small round screen and test larger configurations, large text, TalkBack, outdoor contrast, rotary and touch input as applicable. Keep short content and actions within the visible safe area, and verify localization without assuming every label will fit. Check the Tile preview in the selector and whether the chosen watch face slot accepts the complication data type. A working Compose route does not prove those surfaces render.

Test with an emulator and a physical watch when possible. Compare app, Tile and complication after a data change, then disable connectivity and revoke access. Confirm each surface falls back without repeatedly waking the device and that its in-app action leads to an accurate current state. Record OS, watch face, supported surface, measured update behavior and what was not exercised.

References and rights

Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.

Install this skill directly: skilldb add android-kotlin-skills

Get CLI access →