Ten Health Metrics, Two Platforms
We checked 10 metrics against Apple's and Google's own docs. Every one exists on both. The shapes don't match, and that is the part that costs you.
Product breakdowns, API deep-dives, and playbooks for builders in health, wellness, and fitness tech.
Counted out of Apple's own documentation, not from memory.
We checked 10 metrics against Apple's and Google's own docs. Every one exists on both. The shapes don't match, and that is the part that costs you.
The main React Native HealthKit bridge last released in October 2024. Its Android counterpart cut five versions in one week this August.
An empty health read has several causes and only one is 'connect your device'. Here is the order to rule them out before you write that empty state.
Apple stores heart rate variability as SDNN. Health Connect stores RMSSD. Different statistics, no conversion factor, and one chart that quietly misleads.
64 HealthKit quantity types state cumulative aggregation, 53 state discrete. Choose wrong and nothing errors, no test fails, and the chart still renders.
Nutrition is HealthKit's largest group with 39 identifiers, ahead of Activity at 37. It is also the group almost nobody fills. Your food database is why.
Apple ships the data type years before most apps ship the feature. The additions since iOS 16 are a public preview of what the platform expects to matter.
HealthKit's Mobility group is 9 identifiers the system derives from ordinary walking. No workout to start, no extra hardware, and almost nobody reads them.
HealthKit defines 17 error cases. The authorization-denied one is documented for saving, not reading — which is why an empty read is so hard to debug.
58 of HealthKit's 240 identifiers carry zero words of discussion prose, and the median across all 240 is 15 words. What to do when the docs say nothing.
HealthKit has 240 type identifiers and 127 of them shipped in iOS 8.0. None is marked deprecated. The full version histogram, and what it costs you.
Resolving which value enum decodes a HealthKit category type took three attempts. The first resolved 29 of 30 and was wrong in the worst way.
The places an Apple type and an Android record stop meaning the same thing.
Google closed Fit API sign-ups on 2024-05-01 and documented support ends in 2026-12. Both confirmed. The first date was the one that mattered.
Approval gates, engineering effort, and the bill your users pay.
5 of 24 products bill your end user, not you. All five are direct wearable integrations, and the hardware requirement, not your budget, sets your reach.
12 of 24 products cost the developer nothing, and four of those are rated high engineering effort. The API price is the smallest term in the integration.
4 of 24 products list contact-sales, and their gate text describes four different waits. What to ask for, and what to have ready before the call.
Three directory columns decide your build order: approval gate, engineering effort, user-side cost. Start the clocks you cannot compress on day one.
Half the directory makes you get approved before production, and the gates are six different obstacles. Which ones start clocks you cannot compress.
We track 13 dated ecosystem changes. Only 6 come from a primary source. A confirmed date is a plan; a reported one is a rumour with a number on it.
Dated deprecations, wind-downs, and how to tell a confirmed date from a rumour.
341 pages, 1188 FAQ entries, 283 resolving citations, median stamp age 36 days. What those numbers prove, and the larger thing they do not.
Most health apps read data before they do anything. A whole category skips it — no OAuth, no entitlement, no PHI. Here's when that's the right call.
Why we're building a hub for the people shipping the next generation of health, wellness, and fitness products — and what you can expect to find here.
A practical framework for evaluating fitness and workout APIs: exercise data, motion tracking, AI coaching, pricing, and the questions that matter.