This page lists some of the frequently asked questions and their answers.

## Q: Is Health Connect only available on the Android platform?

**A:** Yes. Both the Health Connect API and the Health Connect app are available
on the Android platform only.

For health sensor data use cases on Wear OS, refer to the
[Health Services API documentation](https://developer.android.com/training/wearables/health-services).

## Q: How do I access Health Connect?

**A:** The method of accessing Health Connect depends on the version of Android
that runs on your device:

- On Android 14, Health Connect is part of the Android system. You can access Health Connect by going to **Settings \> Security \& Privacy \> Privacy** , and look for **Health Connect**.
- On lower versions of Android that support Health Connect, including
  Android 13, Health Connect is a publicly available app that you can
  [download](https://play.google.com/store/apps/details?id=com.google.android.apps.healthdata) from the Google Play Store. You can access the
  app through one of the following ways:

  - Go to **Settings \> Apps**, look for Health Connect, and open it.
  - [Configure the quick access](https://support.google.com/android/answer/9083864) to Health Connect using Quick Settings, which can be found in the system tray.
  - Go to the Google Play Store page of Health Connect and tap **Open**.

| **Note:** Regardless of the version of Android that runs on your device, you can't access Health Connect as an app from the home screen because its intended design is to be a system app accessible through **Settings**.

## Q: How is health data migrated from Android 13 to Android 14?

**A:** The migration from the Health Connect APK for Android 13 to the Health
Connect system app for Android 14 starts automatically as soon as you upgrade to
Android 14.

During the migration, the Android 14 APIs are suspended with a "Migration in
Process" status. The status is also visible in the Health Connect UI. Once the
migration is complete, you can uninstall the standalone Health Connect APK.

Check the [Android 13 to Android 14 migration guide](https://developer.android.com/health-and-fitness/guides/health-connect/migrate/migrate-from-android-13-to-14) for more details.

## Q: Does Health Connect support Android phones without Google Play services installed?

**A:** No. Health Connect has certain compatibility requirements including that
mobile devices have Android 9 (API 28) or higher **with** Google Play
services installed.

## Q: How does Health Connect compare with Google Fit?

**A:** The following table describes key architectural differences between the
two APIs:


<br />


<br />


<br />


<br />


|                                                                                                                                                  ***Health Connect***                                                                                                                                                  |                                                                                                                         ***Google Fit***                                                                                                                         |
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Device-centric** Health Connect is device-centric. Data is stored on the user's device instead of being associated with a specific Google Account.                                                                                                                                                                   | **Google Account-centric** Google Fit is account-centric. Data is stored on a server-side infrastructure. Its data model is entirely tied to specific Google Accounts as opposed to the user's devices. This makes the server the source of truth in Google Fit. |
| **Fine-grained permissions** Users have granular control over which apps have read or write access to each data type through Health Connect. Health Connect benefits from a built-in, custom permissions mechanism. This allows Health Connect to centralize and refine the way permissions are managed and allocated. | **OAuth-based permissions** Permissions in Google Fit require additional work as these are based on OAuth authentication. OAuth scopes may also cover a larger number of data types.                                                                             |
| **Minor data processing** Health Connect involves very little data processing and derivation, with some minor exceptions for data types like Basal Calories and Basal Metabolic Rate (BMR). Therefore, developers will have access to more raw data with Health Connect.                                               | **Service-specific data processing** Google Fit processes more data, turning some data types into others or merging them. Google Fit processes data for a specific service, rather than providing access to raw data as Health Connect does.                     |

<br />

## Q: Is the Health Connect storage on-device or cloud based?

**A:** Health Connect provides on-device storage. Our goal is to create a system
that puts users fully in control of their data, as well as which apps and
services they share it with.

## Q: Which mobile devices are able to use the Health Connect app?

**A:** Only mobile devices with Android 9 (API 28) or higher can use the Health
Connect app. These devices must also have Google Play services installed.

## Q: Does a Java SDK exist on Jetpack? Will this be added eventually?

**A:** The Health Connect SDK is only available in Kotlin. We don't have
immediate plans to add a Java SDK to the Jetpack library. However, we may
eventually support both programming languages depending on developer feedback.

## Q: What is the range of historical data Health Connect can read or write?

**A:** Health Connect allows your app to read records with
`time` or `startTime` for up to 30 days before your app's
[first successful permission request](https://developer.android.com/health-and-fitness/guides/health-connect/develop/read-data#read-restriction). If you would like your app to
read records after 30 days, use the `PERMISSION_READ_HEALTH_DATA_HISTORY`
permission. If your app is uninstalled and then re-installed, the date is reset
which marks as your new starting date as if you use the app for the first time.

There are no restrictions on the data you share with Health Connect, however
avoid writing large amounts of historical data at this time. Similarly, avoid
writing data associated with future events such as a predicted
[`MenstruationPeriodRecord`](https://developer.android.com/reference/kotlin/androidx/health/connect/client/records/MenstruationPeriodRecord).

## Q: Who should I contact if I need help integrating with Health Connect?

**A:** If you have any technical questions, issues, or concerns about Health
Connect integration, submit a ticket to [Health Connect Developer
Support](https://issuetracker.google.com/issues/new?component=1676744&template=2072671).

Our support specialists work hard to respond to developer questions as
quickly and comprehensively as possible. In the meantime, consult the
[Health Connect documentation](https://developer.android.com/guide/health-and-fitness/health-connect) for any guidance you may need.

## Q: How do I declare access to read or write data types?

**A:** For your app to have read or write access to Health Connect data types,
use the Play Console to
[declare that your app accesses these types](https://developer.android.com/health-and-fitness/guides/health-connect/publish/declare-access).
| **Note:** If you are updating your declaration in the case where your app requires new data types, you need to include both new and existing data types, and exclude any data types you no longer need. If you only need to remove access to certain data types, include all of your existing data types but exclude the data types you no longer need.