Google Is in Full-On Damage Control Over Its New Health App

Google is scrambling to fix widespread bugs and user complaints after replacing the Fitbit app with its new AI-heavy Google Health app, which has been plagued by inaccurate data, mislabeled workouts, missing sleep scores, and frequent crashes. The company detailed planned fixes in a blog update, but the rocky migration has drawn comparisons to past app disasters like Sonos and Nest, risking user trust in a competitive health wearable market.

If there’s one thing you don’t want to screw around with as a tech company, it’s apps. Just ask Sonos https://gizmodo.com/how-a-bad-app-led-sonos-ceo-to-resign-2000549262 , which literally had to fire its CEO and start anew over fallout from a botched app update. Google apparently didn’t get that memo because its recent shift from the Fitbit app to the newly christened Google Health https://healthapp.google/ has been… rocky. People are crashing out over the recent app update, and it’s not hard to see why. In case you missed it, Google recently retired its Fitbit app with the launch of the Fitbit Air https://gizmodo.com/googles-screenless-fitbit-air-relies-on-gemini-to-be-your-personal-health-coach-2000755566 , a screenless fitness band and Whoop https://gizmodo.com/the-whoop-5-0-is-a-massive-upgrade-to-health-tracking-i-wasnt-ready-2000628501 competitor. In name and in design, the Fitbit app is no more, and Google Health is the new software du jour. That shift has ushered in quite a few changes, and to no one’s surprise, several of those tweaks have to do with AI. Google Health, as people have learned, is AI-heavy, and therein lies a lot of the app rollout’s problems. There are a lot of stumbles, but here’s a brief, incomplete list: - Data points were straight-up wrong or inconsistent between different parts of the app - Workouts were mislabeled running versus general activity - Sleep scores were missing - There was duplicative content - AI summaries were sycophantic and overly verbose - Random app crashes Not great. And to make matters worse, the general consensus seems to be that people don’t find the visual update to the app to be overly appealing either, with complaints on Reddit https://www.reddit.com/r/fitbit/comments/1tmevrs/google health ruined fitbit/ over the app being noisy and difficult to parse. I, admittedly, was never a user of the Fitbit app, so I don’t have the same context, but here’s a comparison of how the app used to look and how it looks now. I’ll let you make up your own mind on which feels cleaner. Google, for its part, is already rushing to fix things, including all of the bugs that I outlined above, and it’s detailed those fixes in a blog update https://support.google.com/googlehealth/thread/437068226/sharing-upcoming-roadmap-and-improvements?hl that was pushed out yesterday. The company says they should be rolling out in the week ahead. Whether that will sate people who were upset by the shift is another question entirely. As we’ve seen with past app disasters like the Sonos one I mentioned previously, shifts like this can easily put a bad taste in people’s mouths that isn’t easy to get rid of, and it’s not like people don’t have a growing array of other health wearables to switch to. For now, Google Health users will have to buckle down, it appears, and hope that Google can get its post-Fitbit era ducks in a row. This is also not the first time that Google has experienced a messy app migration. There was similar backlash when Google tried transitioning Nest users from the Nest app to the Google Home app https://gizmodo.com/the-google-home-app-is-getting-a-necessary-revamp-1849611590 . It took years before the Google Home app finally got feature parity https://gizmodo.com/the-google-home-app-is-getting-a-necessary-revamp-1849611590 with the Nest app, and even then, Google still hasn’t discontinued the Nest app for some reason.