探索 Wear OS 4 的功能
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Wear OS 4 推出了幾項功能,有助於提升 Wear OS 應用程式的品質
無須專人管理在應用程式中加入這些功能前,請先讓應用程式做好準備,
與 Wear OS 4 相容。
使用者查看手錶時,最先看到的就是錶面,因此錶面是 Wear OS 上使用率最高的介面。使用者會根據自己的風格和需求,透過錶面打造個人專屬的智慧手錶。
錶面格式是 Google 與 Samsung 攜手開發的宣告式 XML 格式,可用於設定錶面的外觀和行為。也就是說,開發人員製作錶面時,無須用到任何可執行的程式碼,也不必在錶面 APK 嵌入任何程式碼。
Wear OS 平台會負責轉譯錶面所需的邏輯,讓您可以專注於實現創意構想,而不必在程式碼最佳化或電池效能方面多費心思。
相較於使用 Jetpack Watch Face 程式庫建構的錶面,以「錶面格式」建構錶面可減少維護和更新的需求。舉例來說,您無需更新錶面,即可提高效能或減少電池耗電量,甚至取得最新的錯誤修正項目。
凡是搭載 Wear OS 4 以上版本的裝置,都能支援錶面格式。
資訊方塊
我們在資訊方塊 1.2 版推出了平台資料繫結的支援功能。換句話說,如果您的資訊方塊會使用心率、步數或時間這類平台資料來源,更新頻率就會是每秒一次。
新版的資訊方塊也支援動畫。您可以透過補間動畫,在部分版面配置更動時製作流暢的轉場效果,而轉場動畫則可為資訊方塊中新增/淡去的元素加上動畫效果。
啟動畫面
從 Wear OS 4 開始,系統一律會套用預設啟動畫面
應用程式比較容易啟動系統會自動為所有人
應用程式。
預設啟動畫面圖示使用的規格與自動調整圖示相同。為了在視覺上維持一致,請為啟動器圖示使用自動調整圖示。
如果您的應用程式實作自訂啟動畫面,或使用啟動器主題,則請遷移應用程式,改為使用 Jetpack 提供的 SplashScreen
程式庫。這樣一來,啟動畫面就能在所有 Wear OS 版本上正確顯示。如需完整操作說明,請參閱實作指南。
將 Wear OS 資料轉移到新行動裝置
自 Wear OS 4 起,使用者可以要求系統轉移 Wear OS
資料。當系統將使用者的 Wear OS 裝置連線至新行動裝置時,所有儲存在穿戴式網路的資料都會轉移至新的行動裝置。然後,系統會中斷 Wear OS 裝置和舊行動裝置的連線。
只要新行動裝置上已安裝行動應用程式並正確設定,您的行動應用程式就會收到回呼,當中包含與舊行動裝置相關聯的 Wear OS 資料。
為您推薦
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間:2025-07-27 (世界標準時間)。
[null,null,["上次更新時間: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)"]]