The quest for the Universal Workout API: Part 1
What workout APIs are already out there?
Problem with all health apps today
Most health apps today exist in silos. Everytime you download a new one you have to enter age, sex, weight. Workouts from one, don’t count in others. So specialization is good of course, but I wish apps could share workout data.
I am currently using two separate workout apps.
Strong does a great job with custom exercises and tracking what I did last time.
Fitbod does a good job tracking muscle recovery and recommending workouts.
I want the recommendations from Fitbod and the tracking from Strong. Currently I enter workouts into both systems. This is time consuming and wasteful.
So I thought, can I create a workout data object or API that works for all workout types?
Before I go about re-inventing the wheel, I decided to look at what workout APIs and data objects are already out there.
Current Workout Data Objects
I found 3 well established workout APIs.
- Apple HealthKit
- Google Fit
- Strava API
Apple has their HealthKit API which offers the HealthKit Workout data object which has a number of useful properties
Google has their Google Fit API. It is a little more extensive and a bit more confusing than the HealthKit.
Strava has a really robust API. Seems to focus a lot on running as that is one of their core competencies.
Coming up Part 2
In Part 2 I will investigate the strengths and weaknesses of each of these APIs, and others I discover and see how they overlap or diverge.