探索 Wear OS 4 的功能
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Wear OS 4 引入了若干功能,有助于增强您的 Wear OS 应用
体验在将这些功能添加到您的应用之前,请让您的应用做好以下准备:
与 Wear OS 4 兼容。
表盘是用户查看手表时最先看到的内容,因此是 Wear OS 最常用的界面。用户主要通过表盘来自定义手表,以彰显个人风格并满足个人需求。
表盘格式是与三星合作打造的声明式 XML 格式,用于配置表盘的外观和行为。这意味着,创建表盘不涉及任何可执行代码,并且表盘 APK 中未嵌入任何代码。
Wear OS 平台负责处理呈现表盘所需的逻辑,这有助于您专注于创意构想,而非代码优化或电池性能。
与使用 Jetpack 表盘库构建的表盘相比,使用表盘格式构建表盘能够减少必要的维护和更新工作。例如,您无需更新表盘,即可受益于性能提升或耗电量优化,甚至无需获取最新的 bug 修复。
所有搭载 Wear OS 4 或更高版本的设备均支持表盘格式。
卡片
功能块 1.2 引入了对平台数据绑定的支持。这意味着,如果您的功能块使用平台数据源(例如心率、步数或时间),则功能块会每秒更新一次。
新版本的功能块还增加了对动画的支持。您可以使用补间动画为布局的局部更改创建平滑过渡,过渡动画可为功能块中新出现或正在消失的元素添加动画效果。
启动画面
从 Wear OS 4 开始,系统始终应用默认启动画面
应用启动时间(即应用冷启动和温启动)。此体验会自动应用于所有用户
在 Wear OS 4 或更高版本上运行的应用。
默认启动画面图标使用的规范与自适应图标相同。为了保持视觉一致性,请为启动器图标使用自适应图标。
如果您的应用实现了自定义启动画面或使用启动器主题,请迁移应用以使用 Jetpack 中提供的 SplashScreen
库。这样,所有版本的 Wear OS 上都会正确显示启动画面。如需查看完整说明,请参阅实现指南。
将 Wear OS 数据传输到新的移动设备
从 Wear OS 4 开始,用户可以请求系统传输其 Wear OS
将数据从一台移动设备传输到另一台移动设备中。系统将用户的 Wear OS 设备连接到新移动设备时,存储在穿戴式设备网络中的任何数据都会传输到这个新移动设备。然后,系统会断开 Wear OS 设备与旧移动设备的连接。
只要您的移动应用已在新移动设备上安装并正确配置,您的移动应用就会收到回调,其中包含与旧移动设备关联的 Wear OS 数据。
为您推荐
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-27。
[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# Explore features in Wear OS 4\n\nWear OS 4 introduces several features to help enhance your Wear OS app\nexperience. Before you add these features to your app, [prepare your app](/training/wearables/versions/4/test) for\ncompatibility with Wear OS 4.\n\nWatch Face Format\n-----------------\n\nA watch face is the first thing that a user sees when they take a look at their\nwatch, making it the most frequently used surface of Wear OS. Users rely on\nwatch faces to customize their watch to suit their style and meet their needs.\n\nCreated in partnership with Samsung, the [Watch Face Format](/training/wearables/wff) is a declarative\nXML format to configure the appearance and behavior of watch faces. This means\nthat there is no executable code involved in creating a watch face, and there is\nno code embedded in your watch face APK.\n\nThe Wear OS platform takes care of the logic needed to render the watch face so\nyou can focus on your creative ideas, rather than code optimizations or battery\nperformance.\n\nWatch faces that are built using the Watch Face Format require less maintenance\nand fewer updates than the ones built using the Jetpack Watch Face libraries.\nFor example, you don't need to update your watch face to benefit from\nimprovements in performance or battery consumption, or to get the latest bug\nfixes.\n\nThe Watch Face Format is supported on all devices that run Wear OS 4 or higher.\n\nTiles\n-----\n\n[Tiles 1.2](/jetpack/androidx/releases/wear-tiles#version_12_2) introduces support for platform data bindings. This means\nthat---if your tile uses platform data sources such as heart rate, step count, or\ntime---your tile is updated once per second.\n\nThe new version of tiles also adds support for [animations](/training/wearables/tiles/animations). You can use\ntween animations to create smooth transitions on changes to part of your layout,\nand transition animations can animate new or disappearing elements from the\ntile.\n\nSplash screens\n--------------\n\nStarting in Wear OS 4, the system always [applies the default splash screen](/about/versions/12/features/splash-screen)\non both cold and warm app starts. This experience works automatically for all\napps running on Wear OS 4 or higher.\n\nThe default splash screen icon uses the same specifications as\n[adaptive icons](/guide/practices/ui_guidelines/icon_design_adaptive). For visual consistency, use an adaptive icon for your\nlauncher icon.\n\nIf your app implements a custom splash screen or uses a launcher theme, migrate\nyour app to use the [`SplashScreen`](/reference/kotlin/androidx/core/splashscreen/SplashScreen) library, available in Jetpack. That way,\nyour splash screen can appear correctly on all Wear OS versions. For full\ninstructions, see the [implementation guide](/training/wearables/apps/splash-screen).\n\nTransfer Wear OS data to a new mobile device\n--------------------------------------------\n\nStarting in Wear OS 4, users can request that the system transfer their Wear OS\ndata from one mobile device to another. When the system connects the user's Wear\nOS device to the new mobile device, any data that's stored in the wearable\nnetwork is transferred to this new mobile device. The system then disconnects\nthe Wear OS device from the old mobile device.\n\nAs long as your mobile app is already installed and [properly configured](/training/wearables/data/transfer-to-new-mobile) on\nthe new mobile device, your mobile app receives a callback containing the\nWear OS data that was associated with the old mobile device.\n\nRecommended for you\n-------------------\n\n- Note: link text is displayed when JavaScript is off\n- [Migrate your splash screen implementation to Android 12 and later](/develop/ui/views/launch/splash-screen/migrate)\n- [Splash screens](/develop/ui/views/launch/splash-screen)\n- [App startup time](/topic/performance/vitals/launch-time)"]]