[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# About complications\n\nA\n[complication](https://en.wikipedia.org/wiki/Complication_(horology))\nis any feature that is displayed on a watch face in addition to the time.\nFor example, a battery\nindicator is a complication. The\n[Complications API](/reference/kotlin/androidx/wear/watchface/complications/package-summary)\nis for both watch faces and data source apps.\n\n\nThe rest of this document describes data sources, watch faces, and\ncomplication types.\n\nComplication data source\n------------------------\n\nApps that provide data such as\nbattery level, weather, or step counts to watch faces for\ncomplications are called *complication data sources* . These data\nsources supply raw data\nand are not responsible for controlling how their data is rendered on a\nwatch face.\nTo learn about writing apps that provide data to watch faces, see\n[Expose data to\ncomplications](/training/wearables/exposing-data-complications).\n\nThe following diagram shows how Wear OS by Google mediates the flow of data\nfrom sources to watch faces.\n**Figure 1.** The flow of complication data.\n\nComplications on watch faces\n----------------------------\n\nWatch faces receive data from complication data sources, which lets them\ninclude\ncomplications without needing code for getting the underlying data. Watch\nfaces retain\ncontrol over how the data is rendered, so they can integrate data\nnaturally with their\ndesign. For more information, see the design guide about\n[Complications](/training/wearables/design/complications).\n\nTo learn how to add complications to a watch face, see\n[Add complications to a watch face](/training/wearables/watch-faces/adding-complications).\n\nComplication types\n------------------\n\nComplication types define what kinds of data can be shown in a\ncomplication or supplied by\na data source. For example, use the `SHORT_TEXT` type when the\ndata consists\nprimarily of a short string. A\n[`ComplicationData`](/reference/androidx/wear/watchface/complications/data/ComplicationData) object always has a single\ncomplication type that defines required and optional fields. A required\nfield\nrepresents the primary piece of data; most types take their name from\nthe required field.\n\nData sources use complication types differently from watch faces:\n\n- A data source chooses the types of complication data to supply, including which optional fields of those types to supply, and how many different types can be supported. For example, a step-count source might support the `RANGED_VALUE` and `SHORT_TEXT` types, and a next-meeting source might support the `SHORT_TEXT` and `LONG_TEXT` types.\n- You can choose how many complications to include in your watch face and the complication types to support. For example, a dial complication on a watch face might support the `SHORT_TEXT`, `ICON`, and `RANGED_VALUE` types. A gauge on the watch face might support only the `RANGED_VALUE` type.\n\nTo learn more about different complication types and fields supported by\neach type, see\n[Complication types](/training/wearables/watch-faces/adding-complications#types-fields)."]]