Health Connect UX developer guidance

Stay organized with collections Save and categorize content based on your preferences.

It's important to promote your app's benefits to users. This helps users make the most out of your Health Connect integration. The following UX guidelines provide information on how to promote Health Connect in your app, focus on the user benefit, and more.

Promote Health Connect in your app

Promoting Health Connect in your app depends on the UX patterns and conventions established in your app. The following are a few examples of how to promote Health Connect:

  • A promotional card in your app’s home screen.
  • A modal or dialog when updating the app.
  • A notification sent to users.

Regardless of the UI treatment you choose, there are a few important things to consider when it comes to the way you describe Health Connect to your users.

Focus on the user benefit

The first time you introduce Health Connect to users, you should aim to offer a meaningful reason for them to make use of your integration. Rather than describing Health Connect's features, you should tailor your message to how a user benefits from those features.

Promote the unique benefits of using Health Connect such as detailed workouts, so that RunTracker users are encouraged to use Health Connect.
Refer to syncing health data from other apps, for example, without explaining the benefit of doing so to SleepTrack users.

Use clear language

Don’t ask users to "Connect to Health Connect." This is a jarring sentence and may also confuse a user’s understanding of the relationship between apps in the Health Connect ecosystem. Your UX should help users form a mental model of how Health Connect interacts with your app, so it’s important to consider which button labels work best towards achieving that goal.

Try using verb phrases like "set up" or "get started" for your button labels. Or, if you’re launching the permissions view, you can use more specific button text, like "Choose data to share."

Set expectations with a specific action that primes users for Health Connect permissions.
Mix the action (Connect) with the product name. This makes it unclear which app is being connected to what.

Refer to key concepts

A shared vocabulary helps users maintain a consistent mental model of the Health Connect ecosystem and how Health Connect relates to your app. It also enables users to find and manage their data and permissions more easily.

You can check user-facing language against this table of concepts to catch any outliers.





Apps can request access to Health Connect.

In Health Connect, access refers to any kind of interaction with health data.

Access acts as a binary on/off switch for an app. Remove access, and the app has no way to interact with users' health data.

"Allow MindFul to access your health data?"

"Remove access for all apps?"


For each app, users review and set permissions.

Permissions are at the heart of Health Connect’s value proposition.

They give users granular control over the data they share between apps.

"Tap an app to manage its permissions."

Read and write

With a user’s permission, apps can read and/or write selected data types.

A simple permissions model allows users to set which apps can read or write a given data type.

Writing also covers updating existing data in that type.

"Allow RunTracker to write data."


Data is stored in Health Connect.

When an app has write permissions, this data is stored in Health Connect.

This mental model, that Health Connect is a "destination" for storing and managing data, helps users know where to find their data.

"This includes data stored in Health Connect by your other apps."