Building a fitness or wellness app? Here's what you need to know about provider integration branding in 2025

Integrating with health data platforms like Garmin, Fitbit, Strava or others can boost your app's value. But each platform has strict branding rules that you need to follow. Get these wrong and you'll face app rejection in app stores or forced updates.

This guide shows you the universal principles for staying compliant across all major health data provider platforms, plus where to find the specific rules for each provider.

Why this matters to you

Platform providers invest heavily in brand recognition and user trust. Their branding guidelines exist for three key reasons: protecting their reputation, ensuring user security, and maintaining consistent experiences across integrations.

When you follow these rules correctly, you demonstrate professionalism and improve your chances of smooth app approval. When you don't, you risk:

• App store rejection or removal
• Legal issues requiring costly fixes
• Confused users who don't trust your integration
• Forced redesigns that delay your launch

Provider specific rules & key requirements for 2025

Each platform maintains detailed branding guidelines that change regularly. Here's the key health data providers and their current requirements.

Google Health Connect (Google Fit)

Google Fit is being deprecated in 2026, with Health Connect becoming the core part of the Android Health platform. Health Connect offers comprehensive UI guidelines that emphasize user-centric design and data transparency.

Key requirements:

• Follow Android's Material Design principles for consistent user experience
• Use clear, descriptive language when requesting health data permissions
• Implement proper data source attribution and transparency
• Provide seamless experience across the Android Health platform
• Never use "Google" or "Google Fit" in your app title - only use nominatively in descriptions
• Use approved color schemes that complement Android's design language
• Ensure proper authentication flows that match Android Health standards
• Display clear data usage explanations before users grant permissions
• Implement robust error handling for Health Connect integration failures

Apple HealthKit

Apple's approach to HealthKit branding focuses on the "Works with Apple Health" badge system. The Works with Apple Health badge is used to visually communicate your app's compatibility with the Apple Health app on iPhone.

Key requirements:

• Use the official "Works with Apple Health" badge for HealthKit-enabled apps
• Use of the Works with Apple Health badge is only permitted in connection with the availability and access of health data through the Apple Health app
• The badge is available in white with an outline rule - other color options are not available
• Don't alter the artwork in any way except to change its size to fit your design
• Do not add a trademark symbol to the Works with Apple Health badge artwork provided by Apple
• When using the Apple Health icon in your app: don't alter its appearance, mask it to change corner radius, or add embellishments like borders, color overlays, gradients, or shadows
• Maintain minimum clear space around the Apple Health icon
• Provide a coherent privacy policy and request access to health data only when needed
• Provide descriptive messages when asking for permission to access health data
• Follow Apple's Human Interface Guidelines for HealthKit for complete design and usage requirements

Strava

Strava maintains detailed developer guidelines that emphasize authenticity and proper attribution. The platform is particularly strict about logo usage and partnership implications.

Key requirements:

• Use only official Strava logos and assets provided in their brand guidelines
• Never modify, rotate, or alter the Strava logo in any way
• Maintain minimum clear space around the logo (typically equal to the height of the "S" in Strava)
• Use the orange brand color (#FC4C02) only when specified
• Always use "Connect with Strava" or "Powered by Strava" language, never imply direct partnership
• Ensure the Strava logo is not the largest or most prominent element on your interface
  
  

Fitbit

Fitbit has specific requirements for third-party developers that differ from other platforms. Instead of using the Fitbit logo directly, developers must use official badge systems to indicate compatibility.

Key requirements:

• Use only official Google Fitbit logos and assets from the Partner Marketing Hub
• Never reposition, stretch, distort, change fonts/colors, or alter element sizes of the logo
• Use a “Works With Fitbit” or “Works With Fitbit Watches” badge (not the Fitbit logo)
• Use Google Sans typeface for consistency with the new wordmark
• Maintain proper clear space around logos as specified in current guidelines
• Refer to API Terms of Service and associated Logo Guidelines at dev.fitbit.com for developer-specific requirements

Huawei

Huawei provides comprehensive branding guidelines through their HMS Core documentation, focusing on proper logo usage and integration standards.

Key requirements:

• Use official Huawei Health logos with proper minimum sizes and clear space
• Follow specified color schemes (typically Huawei's signature red #FF0000)
• Implement proper authentication UI that matches Huawei's design language
• Use appropriate language for describing the integration
• Ensure compliance with Huawei's app verification requirements

Garmin

Garmin's brand guidelines emphasize professional presentation and proper attribution when integrating with their ecosystem.

Key requirements:

• Use official Garmin Connect logos and wordmarks
• Maintain brand color consistency (Garmin blue #007CC3)
• Follow proper logo placement and sizing requirements
• Use approved terminology when describing Garmin Connect features
• Implement clean, professional UI elements that complement Garmin's design aesthetic

Tip: Branding requirements change frequently. Bookmark these docs and check quarterly to avoid surprises.

Common mistakes that get apps rejected on app stores

Based on real developer experiences, these are the most frequent branding violations:

Logo modifications: Changing colors, adding effects, or resizing logos beyond specified parameters.

Partnership implications: Using language that suggests official endorsement or partnership without formal agreements.

Outdated assets: Using old logos or branding elements after platforms have updated their visual identity.

Hierarchy issues: Making platform logos more prominent than your own app branding.

Universal Best Practices

These principles apply regardless of which platforms you're integrating:

Design consistency: Keep your app's branding as the primary focus. Platform logos should support your design, not dominate it. Use consistent button styling across all integrations and implement proper loading states.

Example: Your “Connect with Strava” button should match your app’s style but include the official Strava logo.

Legal compliance: Never imply official partnerships unless you have them. Include proper disclaimers in your privacy policy. Keep your language factual and measured. Use phrases like "Connect with [Platform]" or "Sync with [Platform]" rather than suggesting endorsement.

Logo handling: Always use official assets downloaded directly from platform developer resources. Never modify, rotate, or alter logos. Maintain proper clear space around logos as specified in each platform's guidelines. Ensure logos aren't the largest visual element on your interface.

User experience: Tell users exactly what data you'll share before they connect. Make it easy to disconnect from platforms. Test your integration flows on different devices. Implement proper error handling and loading states for all connections.

Authentication and UI: Follow each platform's specific design language for authentication flows. Use approved button styles and dimensions. Meet accessibility requirements for touch targets and contrast ratios.

Your implementation checklist

Before you launch, verify these items:

1. Download fresh assets: Get current logos from each platform's official developer resources.
2. Review legal language: Have someone check your partnership claims and privacy policy.
3. Test with real users: Make sure your integration flows are clear and easy.
4. Submit early: Give yourself time to fix any branding issues.
5. Document everything: Keep track of guidelines for your team.
6. Set update reminders: Check for guideline changes quarterly.

Proper branding integration isn't just about avoiding legal trouble. It's about building user trust and showing you're a professional developer who pays attention to details.

Each platform's specific requirements matter, and they change regularly. Bookmark the official guidelines above and check them before every release. Your users will appreciate the seamless, professional experience, and platform providers will view you as a reliable integration partner. When you respect branding requirements, your app ships faster, your users trust it more, and your integrations remain stable.

‍

Whether you’re building a fitness tracker, wellness app, or a clinical dashboard, Spike Wearables & IoT API gives you the foundation you need to scale fast and deliver accurate, reliable user insights.

Schedule a demo and learn how we can make health data in your app richer & more personalized.

‍