When building health apps, the fundamental choice is between platform APIs (Apple HealthKit, Google Health Connect) and direct device integrations. One provides access to billions of users through 2 implementations. The other requires maintaining dozens of device-specific connections to reach 30% of the market.
The Core Question
If your users have already connected their Fitbit, Garmin, or Apple Watch to HealthKit or Health Connect, why build a direct integration to those same devices? You're duplicating data paths that already exist while excluding the 90% of smartphone users without wearables.
The Coverage Reality
The global device landscape reveals a massive gap:
- 4.88 billion smartphone users worldwide - universal computing platform
- ~560 million wearable owners globally - concentrated in affluent urban markets
- 90% of smartphone users don't own wearables - excluded by wearable-only strategies
In the United States with the world's highest wearable adoption, only 44% own wearables while 91% have smartphones—platform APIs reach 2x more people. In emerging markets, the ratio is 10-50x in favor of smartphones.
Key Insight: Users Have Already Done the Integration
Garmin users sync to Apple Health. Fitbit users sync to Google Fit. Oura Ring owners have HealthKit enabled. WHOOP added Apple Health sync in 2022. Your target users have already connected their devices to platform APIs. Building direct integrations duplicates work they've already completed.
Platform APIs (HealthKit / Health Connect)
What Are Platform APIs?
Apple HealthKit (iOS) and Google Health Connect (Android) are OS-level health data aggregation systems. They collect data from:
- Any wearable that syncs to the phone - Apple Watch, Fitbit, Garmin, Oura, Whoop, etc.
- Smartphone sensors directly - accelerometer, gyroscope, barometer, GPS
- Third-party health apps - nutrition trackers, meditation apps, period trackers
- Manual user entries - symptoms, medications, clinical measurements
One integration gives you access to all of these sources through standardized data formats.
✅ Platform API Advantages
- 2 integrations, infinite devices: HealthKit + Health Connect = all wearables
- 4-8 hour implementation: vs 2-4 weeks per device for direct integration
- Reaches 100% of users: Wearable data PLUS smartphone sensors
- OS-optimized battery usage: Shared sensor access, batched updates
- Standardized data formats: No device-specific parsing logic
- Historical data included: Years of baseline data from day one
- User trust advantage: 73% opt-in rate vs 58% for direct OAuth
- Automatic future-proofing: New devices work without code changes
- 1-2 hours monthly maintenance: vs 6-12 hours per device integration
⚠️ Considerations
- Less granular real-time data: Batched updates (typically 15-60 min) vs streaming
- No proprietary metrics: Standardized data only (no Garmin Training Load, Whoop Strain)
- Requires user device sync: Data only available after wearable syncs to phone
- Platform dependency: Subject to Apple/Google policy changes
- Limited to mobile: iOS/Android only (not desktop)
HealthKit Capabilities (iOS)
Apple HealthKit provides access to:
- Activity: Steps, distance, flights climbed, active energy, exercise minutes, stand hours
- Sleep: Duration, stages (light/deep/REM), quality, bedtime/wake time
- Vitals: Heart rate, HRV, resting HR, blood pressure, respiratory rate, oxygen saturation
- Workouts: Type, duration, intensity, calories, route tracking
- Body: Weight, BMI, body fat percentage, lean body mass
- Nutrition: Calories, macros, water intake
- Mindfulness: Meditation minutes, stress tracking
- Reproductive: Menstrual cycle, ovulation
- Clinical: Lab results, immunizations, medications (where available)
Health Connect Capabilities (Android)
Google Health Connect provides:
- Activity: Steps, distance, active calories, exercise sessions, elevation
- Sleep: Duration, stages, quality metrics
- Vitals: Heart rate, HRV, blood pressure, respiratory rate
- Body: Weight, body fat, hydration, temperature
- Nutrition: Calories, macros, hydration
- Workouts: 50+ activity types with detailed metrics
- Cycle Tracking: Menstrual data, symptoms
Health Connect aggregates data from 200+ Android health apps and wearables through standardized interfaces.
Direct Device Integration
What Is Direct Integration?
Building OAuth connections directly to device manufacturer APIs:
- Fitbit API - Fitbit/Google devices
- Garmin Connect API - Garmin watches and cycling computers
- Oura Cloud API - Oura Ring
- Whoop API - Whoop Strap
- Polar API - Polar watches
- Suunto API - Suunto watches
- ...and 90+ more device manufacturers
✅ Direct Integration Advantages
- Proprietary metrics access: Garmin Training Load, Whoop Strain, Oura Readiness
- Real-time streaming: Millisecond-level data updates (for supported devices)
- Device-specific features: Firmware updates, device configuration
- Potential partnerships: Co-marketing with device manufacturers
⚠️ Direct Integration Trade-offs
- 2-4 weeks per device: OAuth, certification, API learning curve
- 6-12 hours monthly maintenance: Per device integration
- Different data formats: Device-specific parsing for each manufacturer
- Reaches only 30% of market: Wearable owners only, no smartphone fallback
- Complex OAuth flows: Different for each manufacturer
- API deprecation risk: Manufacturers change APIs without coordination
- Battery drain concerns: Multiple OAuth connections, frequent polling
- Lower user trust: 58% opt-in rate vs 73% for platform APIs
- No historical data: Must accumulate baseline from zero
The Duplicate Data Problem
When you build a direct Garmin integration, here's what actually happens:
- User wears Garmin watch collecting sleep and activity data
- Garmin watch syncs to Garmin Connect app on their phone
- Garmin Connect automatically syncs to Apple Health or Health Connect
- You build an OAuth flow to Garmin Connect API
- Your app now gets the same data through two different paths
You've built expensive duplication. The user already completed steps 1-3 before downloading your app.
⚠️ Real-World Example: WHOOP's Reversal
WHOOP resisted platform API integration for years, maintaining a closed ecosystem. In 2022, they added Apple Health sync. Why? Users demanded unified health data. They wanted their WHOOP data alongside their nutrition, meditation, and other health metrics. WHOOP's closed approach was a barrier to adoption, not a competitive advantage.
The trade-off is clear: Platform APIs provide faster implementation, lower maintenance burden, and reach 3-10x more users than direct device integrations.
When Direct Integration Makes Sense
There are legitimate use cases for direct device integration, but they're rarer than most assume:
Valid Use Cases
- Medical-grade monitoring: FDA-cleared applications requiring specific sampling rates and raw sensor access
- Research studies: Clinical trials demanding precise protocols and unfiltered data for scientific validity
- Proprietary hardware: Companies manufacturing their own devices (even Peloton supports platform APIs alongside direct connections)
- Real-time coaching: Applications requiring <1s latency (though most "real-time" use cases work fine with 15-60s platform API batching)
- Device configuration: Apps that need to modify device settings or firmware
The Hybrid Approach
Even when direct integration is justified, the smart strategy is:
- Platform APIs as foundation: Ensure 100% user coverage (wearables + smartphones)
- Selective direct integrations: Add 1-2 critical devices for enhanced features
- Graceful degradation: Users without those specific devices still get full value
This way, power users with specialized hardware get enhanced precision while everyone else gets full functionality.
The Intelligence Layer Advantage
Raw data isn't enough. Platform APIs provide standardized access, but you still need intelligence to transform measurements into insights.
Most health data aggregators (Terra, Rook) provide webhook pass-through with minimal storage. You receive raw data and must build:
- Data storage and retention systems
- Anomaly detection and data quality validation
- Behavioral pattern recognition
- Health scoring algorithms
- Predictive models for churn, health outcomes
- Personalization engines
This is immensely valuable to most apps and prohibitively expensive for most teams to build in-house.
Sahha's Complete Solution
Sahha combines platform APIs with pre-built intelligence:
- Platform API integration: HealthKit + Health Connect (wearable data from all devices)
- Smartphone sensor collection: Sleep, activity, behavioral patterns (100% user coverage)
- 5 validated health scores: Sleep, activity, mental wellbeing, overall health, readiness
- 14 behavioral archetypes: "Consistent Early Sleeper", "Highly Active", etc.
- Predictive analytics: Churn risk, depression symptoms, performance readiness
- 3-month data retention: Historical analysis and trend detection
- Real-time webhooks: Immediate alerts on score changes
Result: Complete coverage (wearables + smartphones) with actionable intelligence, not just raw data.
Platform Comparison: Who Supports What?
| Platform |
Platform APIs |
Direct Devices |
Smartphone Sensors |
Intelligence |
| Sahha |
HealthKitHealth Connect |
Minimal |
✅ Yes (unique) |
✅ 5 scores + archetypes |
| Terra |
HealthKitHealth Connect |
✅ 90+ devices |
❌ No |
❌ Raw data only |
| Rook |
HealthKitHealth Connect |
Limited |
❌ No |
❌ Raw data only |
| Spike |
Limited support |
Medical devices |
❌ No |
GenAI processing |
| Vital/Junction |
Deprecated |
Deprecated |
❌ No |
Labs only now |
Decision Framework
Which approach is right for you?
Choose Platform APIs if you need:
- 100% user coverage (not just wearable owners)
- Fast implementation (days, not months)
- Low maintenance burden
- Standardized data formats
- Historical baseline data
- Universal device compatibility
- Better battery efficiency
- Higher user trust and opt-in rates
Consider Direct Integration only if:
- You're building medical-grade monitoring requiring FDA validation
- You need sub-second data latency for real-time coaching
- You're manufacturing your own hardware
- You require device-specific proprietary metrics
- You need to configure device settings or firmware
Choose the Hybrid Approach if:
- You want both universal coverage AND enhanced features for power users
- Platform APIs provide your foundation (100% users)
- Direct integration adds 1-2 selective enhancements
The Global Perspective
If you're building for markets beyond Silicon Valley, platform APIs aren't optional—they're essential:
- United States: 91% smartphones, 44% wearables → Platform APIs reach 2x more people
- India: 64% smartphones, 5-10% wearables → 6-12x advantage
- Brazil: 45% smartphones, 3% wearables → 15x advantage
- Sub-Saharan Africa: 33% smartphones, <1% wearables → 33x+ advantage
Wearables are a luxury good concentrated in affluent markets. Smartphones are the universal computing platform.
Conclusion: The Clear Choice
The evidence is overwhelming:
- Platform APIs reach 3-10x more users at 1/100th the cost
- Direct integration duplicates work users already completed (they've synced their devices to HealthKit/Health Connect)
- Smartphone sensors provide behavioral insights that complement wearable data
- Intelligence layers transform raw data into actionable insights (what Sahha provides)
Companies like Strava (135M users) and MyFitnessPal (200M users) prove the platform API model works at scale. Even previously closed ecosystems like WHOOP added platform API support because users demanded unified health data.
Ready to Choose Your Approach?
See how major health data platforms compare on integration approach, coverage, intelligence, and cost:
Compare Platforms →