Showcasing Google Health in your app depends on the UX patterns and conventions
established in your UI.

For example, if your app is already promoting other app integrations, you should
follow those same principles to promote Google Health.

## Focus on the user benefit

The first time you introduce Google Health APIs to users, provide a meaningful
reason for them to set it up. Rather than describing Google Health API features
or just asking a user to "Connect to Google Health", tailor your message to
how a user benefits from those features.

If your app reads from Google Health, mention why would users want to see or use
their data in your app. Examples:

- Gives users more accurate insights in your app
- Let users see all of their data in one place in your app

If your app writes data to Google Health. Example:

- Let users share data from your app with Google Health to see all of their data in one place.

Before launching the standard account linking or OAuth consent screen, present
an **in-app disclosure** that explains the specific value of each permission you
are requesting (for example, *"We need Step data to calculate your daily
activity goals"* ). Don't request all scopes at once without clear context. Also
remind users to sign in to the Google Health mobile app with their Google
Account (or migrate their existing Fitbit account) before continuing to the
OAuth consent screen. See
[Link Google Health before OAuth consent](https://developers.google.com/health/setup.md.txt#link-google-health).

## How to promote Google Health and the APIs

To ensure a seamless user experience, introduce Google Health at intuitive
moments and make connection management transparent and accessible:

- Introduce the integration where it makes the most sense:
  - During your app's setup flow for new users, or by a modal or dialog when updating your app.
  - With a card or banner on your app's home screen.
  - When promoting a new feature that uses data from Google Health APIs.
  - In a dedicated **Connect Apps** , **Devices** , or **Settings** menu where users naturally expect to find app integrations.
- Clear calls to action and connection states:
  - When encouraging a user to connect to the Google Health APIs, use a clear and obvious call to action.
  - When connected, clearly display **"Connected to Google Health"** alongside a timestamp indicating the last successful data sync.
- Transparent permissions:
  - Avoid burying scope requests, consent toggles, or data-sharing settings behind excessive menus or ambiguous UI labels.
  - Avoid duplicate in-app permission toggles that conflict with Google Account consent settings.
- Simple disconnection:
  - Provide a **Disconnect** button, reachable in no more than one or two taps from your app settings (for example, *"You can disconnect from Google
    Health APIs at any time by going to Settings"*).
  - Never hide unlinking mechanisms or loop users back into the OAuth flow when they try to disconnect.
  - When a user unlinks their account, explicitly revoke their Google OAuth token, confirm that data synchronization has stopped, and prompt the user to choose whether previously synced health data should be retained or permanently deleted from your app servers.

If your app already promotes new data from other ecosystems, we recommend doing
the same for Google Health APIs and adapting the language where relevant.

## Google Health branding in your app

We appreciate your use of the Google Health API and kindly request that you
follow our brand guidelines. Avoid copying any Google app screens verbatim,
these will change without warning. You should adapt any guidance from Google to
fit seamlessly into your own app's UX patterns.

### Product names

When localizing your app, don't translate any of the product names provided
here.

Don't use legacy Fitbit or Google Fit logos or naming for Google Health API
integrations unless explicitly relevant to a migration flow.

| Asset | Guideline |
|---|---|
| Brand name | Google Health |
| App name | Google Health app |
| Service name | Google Health Premium |
| Feature name | Google Health Coach |

### Marketing assets

The Google Health logotypes are available for download. Use only the approved
Google Health wordmark, logos, and color styles provided here.

Don't alter the Google Health logo or brand assets in any way. This includes
stretching, skewing, changing the colors, or adding unauthorized effects (like
heavy drop shadows or outlines). However, you should adapt spacing, typography,
and button styles where possible to match your application's design language so
the integration feels built-in.

Light theme logos:

<br />

[Download Google Health logos](https://developers.google.com/static/health/resources/Google_Health_logos.zip) [Download Google Health Premium logo](https://developers.google.com/static/health/resources/Google_Health_Premium.zip) [Download Google Health logo](https://developers.google.com/static/health/resources/Google_Health.zip)

<br />

Dark theme logo:

[Download Google Health Premium logo](https://developers.google.com/static/health/resources/Google_Health_Premium_dark.zip)

For more information on the Google Health brand, see the [Partner Marketing
Hub](https://partnermarketinghub.withgoogle.com/brands/google-health/overview/).