Google Health 5.02: A Step Forward That Still Splits the User Base
Google Health 5.02 is an update to Google’s Fitbit replacement app that restores several familiar Fitbit features—such as hourly activity charts, expanded dashboard metrics, improved sleep-session controls, and faster food search—while exposing a growing gap between Android and iOS users in Google’s health ecosystem. The core message of this release is clear: Google is responding to backlash from the Fitbit-to-Google Health migration, but it is doing so in a way that benefits Android first and leaves iPhone owners waiting for parity. That choice matters, because health apps are not casual utilities. They shape daily routines, guide wellness programs, and anchor long-term tracking habits, and uneven feature delivery across platforms makes the whole system harder to trust for people who mix devices at home or at work.
What 5.02 Gives Back: Fitbit Muscle Memory, Mostly on Android
On paper, the Google Health update looks like a solid win for former Fitbit users. Google Health 5.02 brings back tools people missed after the migration, including hourly activity charts, expanded dashboard metrics in the Today and Health tabs, better sleep-session controls, and faster food search with macronutrient previews before a log is finalized. Both Android and iOS gain the redesigned Nutrition tile, which centers on calories eaten and calories remaining, plus sleep-session deletion, bug fixes for editing sleep, and in-app deletion for some logs synced from partner apps. These changes start to restore the "muscle memory" of the old Fitbit app: routines for checking activity, tuning dashboards, and reviewing sleep now feel less broken. However, the most tangible quality-of-life improvements land on Android first, reinforcing that this ecosystem is optimized for Google’s own mobile platform even when the headline promises cross-platform progress.
The iOS Gap: Missing Dashboard Reordering and Nap Tracking
The problem is not that iOS gets nothing; it is that iOS gets less, later. In Google Health 5.02, Android users gain drag-and-drop dashboard reordering in the Health tab’s Key Metrics section, plus a dedicated naps tab inside the daily Sleep Score view. These are practical features: dashboard reordering Fitbit users relied on to surface their most important charts, and nap tracking that matters for people with fragmented sleep. iPhone owners, however, are told to wait. Health tab drag-and-drop and the naps tab are Android-only in 5.02, with iOS support promised in version 5.03. Nutrition updates and log-deletion controls are live on iOS, but that does not erase the message that their experience is second-class. Google Health 5.02 fixes several Fitbit migration pain points, yet anyone depending on iOS dashboard reordering, nap tracking, custom foods, Apple Health write-back, or a combined 24-hour sleep view should view the migration as unfinished.
Android vs iOS Health: Trust, Timelines and a Fragmented Roadmap
The staggered rollout of Google Health 5.02 exposes deeper issues in Google’s cross-platform health strategy. Google outlined the update in a June support post, with iOS widely available on June 18 and Android 5.02 rolling out by June 22. That timing fits the broader Android reality, where Pixel and non-Pixel devices often get Google updates on different schedules. But in a health context, those delays are not mere inconvenience—they erode trust. Fitbit users built routines around dashboards, sleep tracking, food logs, and synced health data; when those workflows change unevenly across Android and iOS, the app becomes harder to recommend for mixed-device households, BYOD environments, and wellness programs that need predictable parity. Compounding this, several roadmap items remain unconfirmed in 5.02, including custom food logging, Apple Health write-back support, structured weekly workout schedules, a 24-hour combined sleep view, and AI Coach refinements, with no timelines in the notes. Google is asking users to be patient without giving them firm dates.
Fitbit Air’s Quiet Update and What Comes Next for Google Health
The first post-launch update for Fitbit Air underscores Google’s urgency but also its communication gap. A small group of users report a new build, 67.20001.253.2, arriving on top of the launch build 20001.245.19, with no changelog and no reliable way to force the update. Official instructions say users must open Google Health, tap Connections, select the tracker, and then tap Update—if the button appears at all. This low-visibility rollout mirrors the uncertainty around Google Health’s roadmap. Google Health 5.02 already leaves key items like custom foods and Apple Health write-back unconfirmed, and users are told that naps and dashboard reordering on iOS will arrive in 5.03 without a public date. The lesson is simple and quotable: "Google Health 5.02 fixes several Fitbit migration pain points, but iOS users should treat the migration as unfinished." Until Google delivers consistent Android vs iOS health parity and clearer release communication, its ecosystem will feel more like a work-in-progress than a reliable home for long-term biometric data.
