The Big Picture
The promise of a single health hub that unifies data from all your wearables sounds like a dream. Google Health, launched globally yesterday, was supposed to be that dream. But after testing it on day one with a WHOOP strap, an Apple Watch, and a handful of other devices, the reality is sobering: it saw almost nothing meaningful.
Google Health is not a bad app. Its interface is clean, its calorie and step tracking graphs are genuinely intuitive. But its core value proposition—aggregating data from multiple trackers into one cohesive dashboard—falls apart the moment you step outside the Google ecosystem. If you're using a Fitbit Air or a Pixel Watch, you're fine. For everyone else, especially those with a WHOOP, Garmin, Eight Sleep, or similar device, Google Health is currently a glorified step counter.
The root cause isn't Google's incompetence. It's a systemic data siloing problem that has plagued the wearable industry for years. Google Health relies almost entirely on Apple Health for third-party data, and Apple Health itself is only as good as what third-party companies allow it to read. And as it turns out, most of those companies are guarding their most valuable metrics—HRV, sleep stages, recovery scores—behind their own app walls.
Key Insights
The most revealing moment in the test came when I connected Google Health to Apple Health, expecting it to pull years of accumulated data from my WHOOP and Eight Sleep. Instead, it grabbed only nutrition, weight, and steps. Heart rate variability? Missing. Resting heart rate? Missing. Sleep data? Also missing. Google Health was allowed to read everything from Apple Health, but Apple Health simply didn't have that data to give.
This isn't an Apple problem. As many commenters on the video pointed out, Apple has opened HealthKit to developers. The blame lies squarely with third-party companies like WHOOP and Eight Sleep, which intentionally limit what they write to Apple Health. WHOOP, for example, does not write HRV data to Apple Health. Eight Sleep writes only one or two HRV readings per night—far from enough for meaningful analysis. These companies want you inside their own apps, where they can upsell subscriptions and keep you locked in.
Google Health compounds this by offering almost no direct integration with third-party devices. As of launch, the only external data source you can connect is Strava. That's it. No WHOOP, no Garmin Connect, no Eight Sleep API. If you want your non-Apple data in Google Health, you have to route it through Strava first—a clunky workaround that most users won't even know exists.
Practical Application
For now, there's one reliable path to getting more data into Google Health: use Strava as an intermediary. If you own a Garmin, WHOOP, or other device that syncs to Strava, connect Strava to Google Health. This bypasses Apple Health's limitations and gives Google Health at least some activity and heart rate data.
But even this workaround has gaps. Strava is designed for logging workouts, not continuous health metrics like overnight HRV or resting heart rate. So you'll still miss the recovery and sleep data that many users care about most.
If you're a Fitbit or Pixel Watch user, you're in luck. Google Health will give you a complete picture, including sleep tracking and AI coaching (with a premium subscription). For everyone else, the honest advice is to wait. Google is likely working on direct integrations with major wearable brands—they've already hinted at expanding the app and services section. Until then, Google Health is best used as a supplementary dashboard, not your primary health hub.
What to Watch Out For
First, don't assume that connecting Apple Health to Google Health will automatically populate your dashboard. As the test showed, even with full read permissions, Google Health may fail to sync heart-related metrics for reasons that aren't entirely clear. This isn't a one-time glitch; it's a recurring issue with any app that reads from Apple Health. The data transfer is unreliable at best.
Second, be aware that the free version of Google Health is severely limited. AI coaching is completely disabled. Sleep tracking is not automatic—you have to log it manually. And the vitals tab may remain empty for days. If you're expecting a Bevel or Athlytic competitor out of the box, you'll be disappointed.
Third, watch for the data paywall dynamic. Third-party companies are increasingly treating your own health data as a premium feature. WHOOP, for instance, won't write HRV to Apple Health because they want you to see it only in their app. This isn't just an inconvenience; it's a deliberate business strategy that undermines the entire concept of a unified health platform.
Expert Perspective
From a product strategy standpoint, Google Health's launch feels rushed. It's clear that Google is betting heavily on Fitbit integration to drive adoption, but that leaves a massive portion of the wearable market—Garmin, WHOOP, Oura, Eight Sleep—without a clear reason to switch. The app's reliance on Apple Health as a data pipeline is a fundamental design flaw, because Apple Health was never designed to be a universal repository for third-party wearables.
The irony is that Google has the technical capability to solve this. They could open direct APIs for any wearable manufacturer to write data into Google Health. They could leverage Health Connect, their existing data-sharing framework, to bypass Apple Health entirely. But they haven't done that yet. Instead, they've launched a product that works perfectly only if you buy their hardware.
This is reminiscent of Apple's early Health app struggles. Apple Health launched in 2014 with similar data gaps and only became reliable after years of third-party partnerships. Google Health is at the same starting line, but the wearable market is far more fragmented now. Users own multiple devices from different brands, and they expect their data to follow them. Google Health, in its current state, fails that expectation.
Actionable Takeaways
1. If you own a Fitbit or Pixel Watch, Google Health is a solid choice. You'll get full data, AI coaching, and automatic sleep tracking with premium.
2. If you use multiple third-party wearables, connect your devices to Strava first, then link Strava to Google Health. This is the only reliable workaround for now.
3. Do not rely on Apple Health as a bridge for HRV, sleep, or recovery data. Most third-party companies don't write these metrics to Apple Health, so Google Health won't see them either.
4. Wait for direct integrations. Google has confirmed they're working on expanding app connections. Until then, keep using your current health app (Bevel, Athlytic, or the native wearable app) as your primary dashboard.
5. Be skeptical of any marketing that promises a "unified health hub." The wearable industry is built on data silos, and no single app can overcome that without buy-in from every major manufacturer.
