For years, one of Fitbit’s strangest iPhone problems was not the tracker on your wrist. It was the data wall after the workout.
Google Health 5.05 changes that. Google’s official community release notes say iOS users can now share data from Google Health back to Apple Health, including exercise records, steps, vitals and sleep recorded by Fitbit Air. The setup path is profile icon, Partner apps, then Apple Health, followed by the permission prompts.
GearPulse’s view: this is relevant because wearable loyalty is often more emotional than platform companies admit. Some people like Fitbit because the devices are lighter, cheaper, simpler for sleep, or familiar after years of use. If those people carry an iPhone, they should not need a small pile of workaround apps just to keep their health history in one place.
This also pairs neatly with our recent indie apps piece. That article was about software reducing clutter. This update does the same thing in a more concrete way: it removes a data chore people should not have had to solve themselves.
What Google changed
The 5.05 release is not only about Apple Health, but that is the consumer headline.
| Google Health 5.05 item | Platform | Practical meaning |
|---|---|---|
| Share Google Health data back to Apple Health | iOS only | Fitbit-style activity, sleep and vital data can flow into Apple’s health database. |
| Partner apps setup flow | iOS | Users manage permissions through Google Health before data starts writing to Apple Health. |
| Smart Health Links | U.S. only | Users can share selected medical-record summaries by URL or QR code, with Google’s medical-purpose caveat. |
| Fitness fixes | Android and iOS release context | Google says it addressed VO2Max, exercise-map and post-workout editing stability issues. |
The Verge, 9to5Google, MacRumors and Lifehacker all covered the same core shift: native Fitbit-to-Apple-Health syncing is finally here through Google Health. MacRumors also notes user reports that not every metric, such as HRV, necessarily transfers cleanly yet, so this should be treated as a meaningful bridge rather than a perfect mirror.
Why this matters more than it sounds
Wearables are intimate devices. They know when you slept badly, when you skipped workouts, when your heart rate looked odd, and when your routine changed. Splitting that record across apps is more than untidy. It makes trends harder to trust.
If you use an iPhone, Apple Health is often the default long-term archive. If you use a Fitbit or Pixel Watch, Google Health is the device-side home. Until now, that split pushed people toward third-party sync utilities, manual exports or just giving up on a complete view.
Native sync does not make Fitbit the obvious iPhone wearable overnight. Apple Watch still owns the deepest iPhone integration. But it does make Fitbit less awkward for people who prefer a lighter tracker, longer battery life, or a device that feels less like a second phone on the wrist.
What to check before you celebrate
I would still approach the update with a little patience. Google says the rollout will happen in phases over the week, depending on carrier and device. That means some users may not see the option immediately.
| Check | Why it matters |
|---|---|
| Confirm Google Health is on version 5.05 | Older versions may not show the Apple Health write option. |
| Review Apple Health permissions carefully | Health categories are sensitive; only share what you actually want in Apple Health. |
| Compare a few days of data | Sleep, workouts and vitals can sync differently depending on source and permission. |
| Watch for missing metrics | Early reports suggest some categories may not transfer for everyone. |
| Keep third-party sync apps disabled at first | Double-writing data can create duplicates and messy health trends. |
The permission piece is not a formality. The App Store listing for Google Health says the app may handle health and fitness data, purchases, location, contact info, user content, identifiers, usage data and sensitive information depending on features. That is not shocking for a health app, but it is exactly why the setup should be deliberate.
Smart Health Links need a separate mindset
Google also added Smart Health Links in the U.S. The idea is that users can share selected medical-record summaries with providers or family members via URL or QR code. Google’s own release notes include a caveat: the feature is not meant for medical purposes or as a substitute for official clinical records.
That distinction matters. Sharing a summary before check-in could be convenient. Treating it like a definitive medical file would be a mistake. Health apps are useful context tools, not a replacement for clinical records, doctors or emergency documentation.
Who benefits most
| User type | Impact |
|---|---|
| Fitbit tracker owner with an iPhone | Biggest win: less friction getting daily data into Apple Health. |
| Pixel Watch user who also uses iOS health tools | Useful if Google Health is part of your tracking flow. |
| Apple Watch owner | Probably less important unless you also keep Fitbit history. |
| Data nerd | Worth testing carefully to avoid duplicates and missing categories. |
| Privacy-sensitive user | Useful only if the permission tradeoff feels acceptable. |
The people who should be happiest are the ones who never wanted a platform war on their wrist. They just wanted their steps, sleep and workouts to land where the rest of their health data lives.
Bottom line
Google Health 5.05 is not a flashy wearable launch, and that is why it is good.
It fixes a practical annoyance for Fitbit users on iPhone, reduces the need for third-party sync hacks and makes mixed-device health tracking feel a little less punished. The sensible move is to update, connect slowly, review permissions and compare the first few days of data before trusting the pipeline completely.