[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],null,["**Note:** The [Watch Face Format](/training/wearables/wff) is\nrequired for watch faces to be installed on devices with Wear OS 5 or later\npre-installed and for all new watch faces published on Google Play.\n\nStarting in January 2026, the Watch Face Format will be required for watch\nfaces to be installed on all Wear OS devices.\n\nLearn more about the user-facing changes in this\n[Help Center\narticle](https://support.google.com/wearos/thread/284572445). \n\nA watch face is the first thing a user sees when they look at their watch,\nmaking it the most frequently used surface of Wear OS. Users rely on watch faces\nto customize their watches to suit their style and provide quick information at\na glance.\n\nOptions for creating watch faces\n\nThe Watch Face format (WFF) makes it easier than ever to build a watch face.\nCreated in partnership with Samsung, the Watch Face Format is a declarative XML\nformat to configure the appearance and behavior of watch faces. Unlike other\nwatch face APIs, where your APK must include the code to render the watch face,\nthe Watch Face Format only requires resources and declarative instructions. The\nWear OS platform handles the logic needed to render the watch face so you can\nfocus on your creative ideas, rather than code optimizations or battery\nperformance.\n\nWe provide several ways to create a watch face:\n\n- If you prefer a What-You-See-Is-What-You-Get style tool that lets you design the watch face directly, use [Watch Face Studio](https://developer.samsung.com/watch-face-studio/overview.html), which we support in partnership with Samsung.\n- If you're comfortable using [Figma](https://www.figma.com/design/) as a designer, or if you're looking to accelerate the first few steps of creating a watch face as a developer, use [Watch Face Designer](/training/wearables/watch-face-designer), which you access using a plug-in within Figma.\n- If you prefer to manage your watch configuration manually and publish to\n your own app store, you can define watch faces using XML, then publish using\n [Watch Face Push](/training/wearables/watch-face-push).\n\n Android Studio also includes support for building and running watch faces\n that use Watch Face Format.\n | **Note:** The guides on how to [represent the time](/training/wearables/wff/time), and subsequent guides within this part of the documentation, target developers who either use XML or build custom tools to create watch faces using Watch Face Format.\n\nWatch faces built with this format require less maintenance and fewer updates\nthan those built using the legacy Jetpack Watch Face libraries. For example, you\ndon't need to update your watch face to benefit from improvements in performance\nor battery consumption, or to get the latest bug fixes.\n\nAbout the format\n\nAt the heart of a Watch Face Format (WFF) watch face is a document that defines\nthe layout and behavior of the watch face. This document is written in XML,\nconforming to the WFF specification.\n\nThe Wear OS system includes a watch face renderer component. This component\nparses your WFF XML document and renders a watch face from it. Other resources,\nsuch as images and fonts, are pulled in as necessary.\n\nThis approach means you only need to spend time describing how the watch\nface should look, and Wear OS handles all of the code for drawing the watch\nface.\n\nTo deploy a Watch Face Format watch face to a device, package the XML document\nin a standard AAB or APK package.\n\nThe following diagram shows an overview of the approach:\n\nVersioning in WFF\n\nAs WFF evolves, additional features are added, represented by more elements,\nattributes, and data sources that all use the Watch Face Format.\n\nFor example, WFF version 2 introduced Weather support as a data source, which\nis not available in WFF version 1.\n\nWhen designing your watch face, be aware of which features you\nwant to use and their version availability. The reference guide marks\nall features with their availability.\n\nEach version of WFF aligns with a Wear OS release:\n\n| WFF version | Minimum Wear OS version | Minimum API level |\n|-------------|-------------------------|-------------------|\n| 1 | 4 | 33 |\n| 2 | 5 | 34 |\n| 3 | 5.1 | 35 |\n| 4 | 6 | 36 |\n\n[See this guidance](/training/wearables/wff/setup#declare-wff-use) for configuring your `AndroidManifest.xml` and Gradle\nbuild file appropriately.\n\nLearn more\n\nLearn more about the Watch Face Format in these guides:\n\n- [Available features](/training/wearables/wff/features): Explore the watch face capabilities that each version of Watch Face Format supports.\n- [Design guidelines](/design/ui/wear/guides/surfaces/watch-faces): Learn best practices for your watch face's layout and user experience.\n- [Watch Face Designer](/training/wearables/watch-face-designer): Learn how to use the Figma plugin to create your watch face.\n- [Setup](/training/wearables/wff/setup): Configure an Android App Bundle that supports the Watch Face Format.\n- [GitHub samples](https://github.com/android/wear-os-samples/tree/main/WatchFaceFormat): Get started by building sample watch faces and deploying them on the Wear OS emulator or your physical device.\n- [Optimize memory usage](/training/wearables/wff/memory-usage): Learn how to configure your watch face so the system consumes as little memory as possible when rendering your watch face.\n- [XML reference](/training/wearables/wff/watch-face): Explore the individual elements that are parts of a Watch Face Format file. The root element is always `WatchFace`. Note: To view features from a specific Watch Face Format version in the XML reference, check that the appropriate version button is selected at the top of the documentation page.\n- [Publishing guide](https://support.google.com/googleplay/android-developer/answer/13560201): Learn how to publish and monetize your watch face through the Play Store and alternative methods.\n- [WFF and memory validator](https://github.com/google/watchface): Use these open source tools to check your Watch Face Format file for errors and confirm acceptable memory usage before submitting to Google Play."]]