Wear OS のヘルスサービスは、Wear OS デバイスのさまざまなセンサーと関連アルゴリズムの仲介役として機能する API です。この API は、アクティビティ、エクササイズ、健康に関連する高品質のデータを、バッテリー効率の高い方法でアプリに提供します。ヘルスサービスは Wear OS 3 以降を搭載するデバイス間で一貫しています。つまり、アプリの作成は 1 回だけで済み、デバイスに関係なくアプリのパフォーマンスが同じになるようにヘルスサービスが対処します。
Google Fit Android API は、ほぼ時間データや履歴データの読み取りやアクティビティの記録など、フィットネス関連の多くのアクションをサポートしている API をご存じかもしれません。Google Fit Android API は非推奨となりました。アプリで Google Fit Android API を使用している場合は、移行ガイドを参照して、アプリの機能を維持するための代替手段をご確認ください。Google Fit Android API で実行できる操作の多くは、Android Health API で実行できます。たとえば、Google Fit Recording API の代わりに、モバイルで Recording API を使用できます。
使用する API を計画するには、次のデータ型に関するガイドを参照して、ヘルスコネクトから読み取ることができるデータと、ヘルスサービスを使用して Wear OS デバイスから読み取ることができるデータを理解する必要があります。
[null,null,["最終更新日 2025-07-26 UTC。"],[],[],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."]]
