Wear OS 上的健康照護服務 API 是 Wear OS 裝置上各種感應器和相關演算法的中介 API。此 API 以省電方式為應用程式提供與活動、運動和健康相關的高品質資料。在搭載 Wear OS 3 以上版本的裝置上，健康照護服務提供一致的使用體驗，因此您只需編寫應用程式一次，而且無論使用何種裝置，健康照護服務都會確保應用程式執行相同作業。
您可能已經熟悉 Google Fit Android API，這個 API 可支援許多健身相關動作，例如讀取近乎時間、歷來資料和記錄活動。Google Fit Android API 標示為已淘汰。如果您的應用程式使用 Google Fit Android API，請參閱遷移指南，瞭解維護應用程式功能的替代方案。您可透過 Google Fit Android API 執行的許多動作，都可以透過 Android Health API 完成。舉例來說，您可以使用行動裝置上的錄製 API，而非 Google Fit Recording API。
如要規劃要使用哪些 API，建議您參考下列資料類型指南，瞭解可能會從 Health Connect 讀取哪些資料，以及您可以使用健康照護服務從 Wear OS 裝置讀取哪些資料：
[null,null,["上次更新時間：2025-07-26 (世界標準時間)。"],[],[],null,["# Get started with health on Android\n\nAndroid Health provides the following APIs to create health and\nfitness apps across form factors: [Health Connect](#health-connect) and\n[Health Services on Wear OS](#health-services). You can use one or both for your\napp experience.\n\nThis developer center includes guidance for using both APIs, and points to\nadditional resources from across Android to help you build health and fitness\napps.\n\n\u003cbr /\u003e\n\nRead and write on-device health and fitness data using Health Connect\n---------------------------------------------------------------------\n\n[Health Connect](/guide/health-and-fitness/health-connect) is an Android\nplatform that allows health and fitness apps to store and share the same\non-device data, within a unified ecosystem. It also offers a single place for\nusers to control which apps can read and write health and fitness data.\nHealth Connect supports reading and writing over 50 different data types,\nfrom cycling speed to body temperature. If you're building a new app, we\nrecommend you use Health Connect.\n\n[Get Started with Health Connect](/guide/health-and-fitness/health-connect)\n\nAccess high-quality sensor data with Health Services on Wear OS\n---------------------------------------------------------------\n\n[Health Services on Wear OS](/training/wearables/health-services)\nis an API that acts as an intermediary to the various sensors and related\nalgorithms on Wear OS devices. The API provides apps with high-quality data\nrelated to activity, exercise, and health, in a battery-efficient way. Health\nServices is consistent across devices running Wear OS 3 or higher, meaning you\nonly need to write your app once, and Health Services takes care of ensuring\nthe app performs the same, regardless of the device.\n\n[Get Started with Health Services](/training/wearables/health-services)\n\nAndroid Health across devices\n-----------------------------\n\n**Health Connect** is only available on Android mobile devices. However, if you\nhave other data sources connected to your mobile app, such as a wearable,\nyou can use your mobile app to facilitate the data transfer from the wearable\nto Health Connect and correspondingly from Health Connect to the wearable.\n| **Note:** Health Connect is not well-suited for providing live data, but rather storing and unifying data across apps and devices.\n\nAt this time, **Health Services** is only available for Wear OS\ndevices running Wear OS 3 or higher. For all other devices, including phones,\nyou should consult the documentation for [`SensorManager`](/reference/android/hardware/SensorManager).\n\n[Companion Device Manager](/guide/topics/connectivity/companion-device-pairing)\nand [Bluetooth connectivity](https://developer.android.com/guide/topics/connectivity/bluetooth)\nare additional options to connect companion devices that don't run Wear OS.\n\nYou might be familiar with the Google Fit Android API, which supports many\nfitness-related actions such as reading near-time and historic data and\nrecording activities. The Google Fit Android API has been\n[marked as deprecated](https://developers.google.com/fit/android). If your app\nuses the Google Fit Android API, consult the\n[migration guide](/guide/health-and-fitness/health-connect-guidelines/migrate/migration-guide)\nto learn about alternatives for maintaining your app's capabilities. Many of the\nactions you can perform with the Google Fit Android API can be done with Android\nHealth APIs. For example, you can use the\n[Recording API on mobile](/health-and-fitness/guides/recording-api) instead of\nthe Google Fit Recording API.\n\nTo plan out which APIs to use, you should consult the following data types\nguides to\nunderstand what data you could potentially read from Health Connect and what\ndata you could use Health Services to read from Wear OS devices:\n\n[Health Connect Data Types](/guide/health-and-fitness/health-connect/data-and-data-types/data-types)\n\n[Health Services Data Types](/reference/kotlin/androidx/health/services/client/data/DataType)\n\nThe most complete multidevice experiences use both Health Services and Health Connect\nto offer the most value for users.\n| **Note:** In order to read a particular data type from Health Connect back to your app, your user must have at least one app on-device that is writing that particular data type. For example, if you want to use heart rate in your mobile app and your app doesn't already measure heart rate, you need to rely on another app writing heart rate values to the Health Connect datastore in order to read heart rate data back."]]
