What the Fitbit to Google Health migration is and why it angered users
The Fitbit to Google Health migration is a forced app transition where Google replaced the long‑standing Fitbit app with the new Google Health app, changing design, features, and data views in ways that disrupted how millions of people track workouts, sleep, and daily health metrics. The switch began mid‑May when Fitbit on Android and iOS auto‑updated to Google Health 5.0, and it became mandatory for anyone setting up the new Fitbit Air fitness band. Long‑time Fitbit users say the app feels unfinished: core stats are harder to find, graphs are scattered across tabs, and familiar elements like Sleep Profile and the monthly “sleep animal” disappeared without an equivalent. A survey of more than 1,500 Android Authority readers found that “51% say Google Health looks better, but is worse to use,” underlining how design changes have trumped usability for many.
From missing basics to broken workflows: what users lost in the transition
The most vocal Fitbit users complaints focus on missing or degraded features that formed part of their daily routines. Runs were mislabeled as generic workouts, maps loaded slowly, and TCX exports contained incomplete data, which undermined years of trusted exercise history. Sleep tracking took a clear hit: Sleep Scores went missing in parts of the app, naps were harder to find, and Sleep Profile — including the popular monthly sleep animal — vanished. Nutrition tracking also regressed, with some users saying food logging became so difficult they stopped using it altogether. Stats and trends that used to live on simple, scrollable dashboards are now buried inside tiles and multiple tabs, forcing people to customize the Health tab before they can see what used to appear by default. For long‑time Fitbit owners, this felt less like an upgrade and more like losing the familiar tools they bought the hardware for.
Inside the Google Health app issues: UI, AI Coach, and UX missteps
Beyond missing features, many frustrations stem from how Google Health now presents information. The new interface leans on tiles, carousels, and status‑driven screens that react to the moment instead of laying out data in one long, scrollable feed. This makes basic metrics like yesterday’s steps surprisingly hard to locate. Android Authority’s poll showed that while a slim majority think the app “looks better,” half of respondents dislike using it because charts are unsortable and data is inconsistently placed across the app. Google’s Gemini‑powered AI Coach is another friction point: instead of being an on‑demand helper, its verbose, overly enthusiastic summaries often crowd out simple graphs and concise explanations. Some early preview testers say their feedback about this was ignored. For many, the app feels optimized to showcase AI rather than provide fast, transparent access to step counts, sleep history, or workout trends.
Google Health features roadmap: 39+ fixes to workouts, sleep, and nutrition
The backlash has pushed Google into a rare move: publishing a public Google Health features roadmap that lists more than 39 upcoming fixes and additions. Exercise tracking is first in line. This week’s updates correct runs that were mislabeled as general workouts and add splits to run summaries, while future releases aim to speed up map loading, improve map discoverability, and fix incomplete TCX exports, including for Fitbit Air and multi‑device sessions. Google also plans to improve automatic exercise detection and address metric inconsistencies when multiple devices feed data into Google Health. On the daily tracking side, the roadmap promises clearer Sleep Score display, a 24‑hour sleep view combining naps and main sleep, and better nap visibility across days. Nutrition fixes include stopping duplicate food logs when the same app connects through Health Connect and other paths, and cleaning up meal‑type errors from popular calorie‑tracking services.
A rare public accountability moment for Google — and what comes next
For a company known for abrupt product changes, this rollout stands out as one of Google’s most controversial app transitions. The forced Fitbit to Google Health migration, the dependence on version 5.0 to set up Fitbit Air, and a wave of negative Reddit threads and app‑store reviews have forced Google into public damage control. According to Technobezz, Google responded by posting a support‑center roadmap that it will “keep updating” as fixes ship throughout the summer, focusing on tracking accuracy, sleep and nutrition clarity, AI Coach behavior, sharing, and account migration. The plan is a significant cleanup effort, but execution will decide whether users stay or switch platforms entirely. If Google can restore lost Fitbit‑style features while keeping a cleaner, less intrusive Coach, it may turn this misstep into a stronger health platform. If not, the migration will be remembered as a case study in how not to replace a beloved app.
