How to Enable Google Fit, Apple’s HealthKit, and Other Services to Share Data with Your App

Whatever your reasons are, you will still encounter the same questions like:

• What data do fitness trackers and apps collect?
• How can you enable Google Fit, Apple’s HealthKit, Garmin, Strava, Fitbit, and other services to share data with your application?
• Are there any special privacy, security, or other requirements you need to oblige in order to fulfil to integrate these services into your app?

In this guide, we’ll cover all of the already mentioned, as well as some other questions like comparing Google Fit kit vs Apple Health Integration. Let’s start by figuring out the general scheme of how you can integrate these services into your app.

📲 How to Get Fitness & Health Data for Your App from other Apps?

For non-developers

If you're a gym and yoga studio owner, personal coaches, or fitness influencers who has little background in the tech industry, let’s dedicate some time to talking about how third-party app features integration works from the technical point of view.

To access fitness & health data provided by such services as Google Fit, Apple Health, Garmin, and others, you’ll need to integrate their public API — application programming interface. To put it simply: write a special part of code that will enable your app to reach out to those services, ask them for data and display it in your application.

In the description of each service, we’ve left links to the service’s documentation that explains what your developers should do. So just show it to your development team if you already have one — and they’ll be all set!

In case you’re still looking for a Tech Partner, drop us a line with your idea and we’ll be glad to see how we can apply our experience to help you!

For developers

Links to the documentation can be found in paragraphs dedicated to each service 🙂

---

Let’s start by taking a look at two major fitness & health data services — Google Fit and Apple Health!

🏃‍♂️ Google Fit

Google Fit was released in 2014. The same year the company also introduced the Google Fit SDK to provide developers with tools for mobile and web app development.

Actually, there are quite many fitness apps using Google API. The most well-known are Nike Run Club, Strava, Runtastic, 8fit Workouts, Calorie Counter — MyFitnessPal, and others.

What’s even more interesting is that the list of Google Fit compatible apps isn’t only limited to fitness applications. For example, you can find such apps as Pokémon Go (game), Calm (mindfulness), or Clue Period Tracker (women’s reproductive and overall health).

Your app can access this data by asking permission to do so. Except for that public data, Google Fit can also store restricted health data types. However, since these kinds of data relate to sensitive healthcare information, you’ll have to apply for OAuth API verification to get it. Then, Google will review your application and either grant or deny verification. Such protected info includes:

• Oxygen saturation
• Body temperature
• Blood pressure
• Blood glucose
• Cervical position and others

If you need data that isn’t covered by the platform yet, Google allows creating custom data types.

Requirements

Since health and fitness data is usually quite sensitive, you should also be aware of how Google Fitness APIs comply with modern security requirements and how you integrate them without breaking these rules.

The full Terms and Conditions can be found here, so we’ll just cover the key points:

• If you use Shareable Data Types from other providers, you may be required to comply with additional third-party terms. For example, if you’d like to use any custom fitness data (e.g., NIKEFUEL fitness points) in your app, you must comply with the terms of the provider (the NIKE+ Developer Terms in that case).
• Google Fit isn't meant to be used with medical devices. As Google explicitly states it, "do not use Google Fit APIs with any product or service that may qualify as a medical device" as it defined in the Section 201(h) of the Federal Food Drug & Cosmetic (FD&C) Act.
• Using Google Fit APIs doesn't automatically make your app HIPAA-compliant. That means that you are solely responsible for any applicable compliance with HIPAA. Moreover, if you plan to involve any kind of Protected Health Information (according to HIPAA), you’ll need to get prior written consent from Google to use such.
• Finally, you have to agree that you will neither sell any content you get from Google Fit for advertising, promotions, etc., nor allow your end-users to do so.

Integration

To enable Google Fit to share data with your app, you’ll need a Google account and Google Play Services. Good news for your developers: Google provides clear and extensive documentation on how to retrieve data from Google Fitness API! Let them check it below:

• Android APIs for developing Android apps
• REST API for developing apps on any other platform (including desktop web)

Now, let’s switch to Apple’s healthcare data framework and check the differences between HealthKit and Google Fit!

🧘‍♀️ Apple’s HealthKit

Just like Google Fit, the Apple Health app was announced in 2014 and included in Apple devices with iOS 8+. Quite a fruitful year for fitness apps, isn’t it?

Along with the app, the company also released the Apple HealthKit API, which is a part of the iOS SDK for app development on Mac.

The tool became popular really quickly. The list of apps compatible with HealthKit includes such popular names as:

• fitness apps — Strava, Runtastic Steps, Garmin Connect
• nutrition apps — Lifesum, Foodzy
• healthcare apps — HealthyNow, Hello Doctor

** full list of examples can be found here*

How does the Health app collect such data? It’s provided either by:

• devices (for example, iPhone or Apple Watch may count the number of steps taken and calories burned);
• apps (user has their own favorite hydration app that shares this data with Apple Health);
• the user themselves (when they manually enter their weight).

Note that developers aren’t allowed to create custom data types. So, if you decide to connect Apple Health framework to your app, make sure that it provides all the types of data you need. Otherwise, we’d recommend you to consider using another fitness data service that either provides all the required data types or allows you to create custom ones — like Google Fit API.

When developing fitness apps that work with Apple Health you can enable them to access and read the data as well as save new data to HealthKit.

Requirements

Apple has quite strict guidelines for developers that want to enable data exchange using the Apple Healthkit SDK. Here are the key things to consider:

• You must get explicit permission from a user to read and write their data. It might be heart rate, running or workout data, blood pressure - you need their permission. Moreover, users can grant or deny their permission for each type of data: for example, they may grant permission to share their blood pressure and heart rate after any form of exercise but prevent your app from accessing any nutrition data.
• Data must be kept only on users’ devices.
• You can only access the Apple HealthKit APIs if your app is primarily designed to provide fitness or health services. How can you prove this to Apple? As they put it in their guidelines, “it must be clear in both your marketing text and your user interface”.
• Obviously, you can’t disclose any information gathered via the Apple HealthKit framework for advertising. That indicated that you can still run in-app ads but not use health & fitness data for that purpose. Also, Apple allows sharing this information with third parties but only with user permission and only if the third parties also provide fitness or health services (for example, yoga classes) to the user.
• Finally, you must have a coherent and clear privacy policy. Additionally, you should provide a URL during the app submission process, so that users can easily find and check it out on the App Store page of your fitness or health app.

You can find more details on user privacy on the official pages of the iOS HealthKit framework: Protecting User Privacy and HealthKit Interface Guidelines.

Integration

Apple has a comprehensive step-by-step guide for iOS developers. Note that you can only integrate HealthKit into iOS applications.

For that, however, your Development Team will need to use iOS SDK 8 or higher. The guide for that can be found here.

🏄‍♀️ Garmin

Garmin is one of Apple’s and Fitbit’s key competitors on the market of fitness wearable devices. With millions of users, Garmin also represents a huge database of fitness data that you can access from your fitness app, too.

That has been proven by the number of third-party fitness apps and websites that have partnered with Garmin for facilitated data exchange. To name a few big names: Nike+, Strava, MyFitnessPal, Run Keeper, and others.

However, you can customize your data feed and read only those metrics that are essential for your app, leaving out the unnecessary ones.

The list of supported activity types is also huge and includes over 30 names. Except for basic running/cycling/swimming activities, Garmin also provides data on such special sports like kitesurfing, snowboarding, and others.

Requirements

Garmin’s Privacy Policy and Agreement are available only for those who have requested and been granted access to the company’s API and SDKs.

However, as of 2019, it included common security requirements:

• You are allowed to transmit and share any end-user data only with the fully informed consent of the end-user.
• It’s prohibited to sell or rent data you get using Garmin’s API or SDKs.

However, it also included a number of special responsibilities such as:

• If you’re going to change the location or URL of your privacy policy, you must first get Garmin’s written consent at least 30 days prior to the change.
• If you’d like to mention Garmin for any marketing purposes, you must first obtain written approval.

Integration

Garmin provides access to its framework upon request. Usually, the request is processed within 2 business days. The approval grants you access to the Garmin Developer Portal.

They also hold an integration call to better understand your needs and help with high-level technical details. Typically, integration takes 1-3 weeks. Typically, integration takes 1-3 weeks.

You can send your request here:

Garmin Health SDKs Overview | Garmin Health API Overview

🚴‍♂️ Fitbit

Enabling Fitbit to share data from 20+ million users opens your way to one of the biggest fitness data storages. Additionally, with comprehensive documentation, the development becomes a “piece of cake.”

Just like Garmin, Fitbit integration allows creating your own apps for Fitbit wearable devices and integrating user data into your desktop or mobile applications. Here are APIs and SDKs you should use for that purpose.

You should also be careful with details. For example, your app, business name, domain name, and even email address or social media username can’t contain not only the name “Fitbit” itself but also the “-bit” ending. You are also not allowed to use their logo, icon, and even fonts from any Fitbit Products.

You can check all the needed policies and requirements here:

• Fitbit Platform Terms of Service
• If you’re developing an application for a Fitbit Product, then it must also comply with the Fitbit App Gallery Guidelines and Fitbit Application Distribution Agreement.

Integration

To connect Fitbit SDK and develop apps and clock faces for Fitbit devices, you’ll need:

• A Fitbit user account.
• A Fitbit OS device for testing. It’s not mandatory to buy one — you can use the Fitbit OS Simulator for Windows or macOS instead.
• The latest Fitbit mobile app for iOS, Android, or Windows Phone, paired with a Fitbit device.
• A computer with access to the Fitbit Studio.
• An internet connection for the Fitbit device.

Look for all the details here:

Fitbit SDK | Fitbit Web API

🏂 Strava

Strava is another popular fitness platform that can be a source of valuable health & workout data for you. However, the company is also quite strict on how you use that data, so they expect your application to augment the Strava user experience in the first place.

Nevertheless, the Strava API is used by many big names such as Fitbit, Peloton, or Aaptiv. The company is actually really proud of the number of apps integrated with them, so you can find many cases on this list.

By the way, one of the projects we’ve worked on is featured on that list under the wellness category — look for WePulse. Closer to the end of this article we'll share our expertise using that case!

Strava doesn’t have all these data types listed in one place, but you can check this page for more info.

Requirements

Strava’s guidelines are somewhat similar to the ones Fitbit has. Except for basic security requirements, you are not allowed to create an app that replicates or competes with Strava.

However, the company also has a few special requirements. For example:

• You must use the provided Strava logos and links in places where you use data provided by Strava.
• Your app must include the button that allows users to connect strava.
• You must also include the “Compatible with Strava” or “Powered by Strava” logos on all websites, applications, and media (prints, videos, images).

To make sure your app matches all the requirements for Strava integration, check the following links:

• Strava API Agreement
• Strava API Brand Guidelines

Integration

All the info on integration can be found in the Getting Started Guide and Strava API Documentation.

🦸‍♂️ Our Expertise in Health and Fitness Data Sharing Implementation

At Stormotion, we have also implemented fitness data integration from third-party services into our clients’ apps. One of the projects we’ve worked on, WePulse, is even featured on the Strava website.

WePulse is a French corporate well-being platform aimed to motivate employees across Europe to adopt a healthier lifestyle. The company has over 85 000 signed up employees and 150 partners, including BNP Paribas, Go Sport, and the city of Paris.

We started working on their project when our other client, a German corporate health platform HUMANOO, acquired WePulse.