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.
When possible, provide clear in-context disclosures and explain what type of data might be shared and why before launching the standard account linking or OAuth flow.
How to promote Google Health and the APIs
Here are a few ways you can promote Google Health and the Google Health APIs in your app:
- As part of your app's setup flow for new users.
- With a card or banner in your app's home screen.
- Through an entrypoint within a Settings screen or similar where you have your existing list of app integrations.
- When promoting a new feature which uses data from Google Health APIs.
- With a modal or dialog when updating your app, similar to your app's setup flow.
Make sure that connection and disconnection options are clear:
- Place entry points, connection states, and settings where users naturally expect them.
- When encouraging a user to use the Google Health APIs, use a clear and obvious call to action to the user.
- Ensure users can easily find how to revoke permissions or disconnect their
Google Health integration directly from your app settings.
- "You can disconnect from Google Health APIs at any time by going to Settings"
- Avoid burying scope requests, consent toggles, or data-sharing settings behind excessive menus or ambiguous UI labels. Data permissions should not be obscured.
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:
Dark theme logo:
Download Google Health Premium logo
For more information on the Google Health brand, see the Partner Marketing Hub.