Complications
Stay organized with collections
Save and categorize content based on your preferences.
A complication is a UI element on a watch face that contains highly-glanceable
information that users want to see often throughout the day. For example, you
could create a current weather complication, or a heart rate complication.

UX Principles
The following sections describe principles to keep in mind when creating
complications.
Glanceable |
Content forward |
Privacy first |
Complications are small components designed to help users complete
frequent tasks quickly. Make content simple and readable. |
Complications are most valuable when the content that the user needs is
made visible by simply raising their wrist, without needing further
interaction. |
The watch travels with the user everywhere they go. Consider how the
content in the complications is relevant to the user's context. |
Use cases
When tapped, complications can help users access a specific part of an app.
They can also perform a self-contained action. For example, tapping a
Water Count complication changes the glass count.

WearOS automatically includes an app shortcut complication, so you don't need to
create your own. Instead focus on creating complications that can help users
complete focused tasks.
Types
Complication types refer to the kinds of data shown on the complication or
supplied by a data source. A complication always has a single type that includes
required and optional fields. A required field contains the primary data. Most
complication types take their name from their required field. You can choose how
many complications to include in your watch face and the complication types to
support. There are five complication types.
Type |
Required fields |
Optional fields |
Class name |
Example |
SHORT_TEXT |
Short text |
Icon, Burn in protection icon, Short title |
ShortTextComplicationData |
 |
ICON |
Icon |
Burn in protection icon |
MonochromaticImageComplicationData |
 |
RANGED_VALUE |
Value Min value Max value |
Icon, Burn in protection icon, Short text, Short title |
RangedValueComplicationData |
 |
LONG_TEXT |
Long text |
Long title, Icon, Burn in protection icon, Small image |
LongTextComplicationData |
 |
SMALL_IMAGE |
Small image |
|
SmallImageComplicationData |
 |
LARGE_IMAGE |
Large image |
|
PhotoImageComplicationData |
 |
For more information about complication data sources, see
Complication types.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-05-20 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-20 UTC."],[],[],null,["# Complications\n\nA complication is a UI element on a watch face that contains highly-glanceable\ninformation that users want to see often throughout the day. For example, you\ncould create a current weather complication, or a heart rate complication.\n\nUX Principles\n-------------\n\nThe following sections describe principles to keep in mind when creating\ncomplications.\n\n|------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| Glanceable ---------- | Content forward --------------- | Privacy first ------------- |\n| Complications are small components designed to help users complete frequent tasks quickly. Make content simple and readable. | Complications are most valuable when the content that the user needs is made visible by simply raising their wrist, without needing further interaction. | The watch travels with the user everywhere they go. Consider how the content in the complications is relevant to the user's context. |\n\nUse cases\n---------\n\nWhen tapped, complications can help users access a specific part of an app.\nThey can also perform a self-contained action. For example, tapping a\nWater Count complication changes the glass count.\n\nWearOS automatically includes an app shortcut complication, so you don't need to\ncreate your own. Instead focus on creating complications that can help users\ncomplete focused tasks.\n\nTypes\n-----\n\nComplication types refer to the kinds of data shown on the complication or\nsupplied by a data source. A complication always has a single type that includes\nrequired and optional fields. A required field contains the primary data. Most\ncomplication types take their name from their required field. You can choose how\nmany complications to include in your watch face and the complication types to\nsupport. There are five complication types.\n\n| Type | Required fields | Optional fields | Class name | Example |\n|--------------|---------------------------|--------------------------------------------------------|--------------------------------------|---------|\n| SHORT_TEXT | Short text | Icon, Burn in protection icon, Short title | `ShortTextComplicationData` | |\n| ICON | Icon | Burn in protection icon | `MonochromaticImageComplicationData` | |\n| RANGED_VALUE | Value Min value Max value | Icon, Burn in protection icon, Short text, Short title | `RangedValueComplicationData` | |\n| LONG_TEXT | Long text | Long title, Icon, Burn in protection icon, Small image | `LongTextComplicationData` | |\n| SMALL_IMAGE | Small image | | `SmallImageComplicationData` | |\n| LARGE_IMAGE | Large image | | `PhotoImageComplicationData` | |\n\nFor more information about complication data sources, see\n[Complication types](/training/wearables/watch-faces/complications#types)."]]