The old dashboard is part of the health record

A fitness app dashboard is not just a screen. For many people it becomes the morning check: sleep, steps, workout, food, heart rate, battery, yesterday's comparison, and the one number they glance at before deciding whether the day is normal.

That is why a forced health-app migration has a different failure mode from a normal redesign. If a music app moves the queue, it is annoying. If a habit tracker moves the data, renames the metric, changes the daily view, hides export, or inserts coaching before the numbers, the user has to rebuild a routine that may have taken years to settle.

The Google Health and Fitbit transition is a useful current case. Google's help page says the Fitbit app became the Google Health app starting May 19, 2026, with automatic updates rolling out between May 19 and May 26. It describes a new four-tab structure: Today, Fitness, Sleep, and Health. It also lists removed or changed features: badges are no longer supported, some social features are removed, certain sleep and health metrics are renamed or moved, and some data tied to removed features is only available to download or delete for a limited window.

None of that automatically means the redesign is bad. Consolidating Fitbit, Pixel Watch, Health Connect, Apple Health, medical records, and premium coaching into one place can make sense. A single app can reduce duplicate logs and make cross-device history easier to inspect.

The complaint is narrower: a habit app should not treat the old route to a daily answer as disposable.

The community reaction shows why. Reporting from The Verge and 9to5Google notes complaints about dashboard customization, food logging, exercise labels, data that felt lost or moved, and coach-generated messages taking space in the Today view. A large Reddit thread has the same pattern in rougher language: people are not only angry about a new logo. They are angry that their morning run, lunch log, sleep comparison, spreadsheet routine, or old one-page daily scan now takes more digging.

A health app migration needs a habit map before it needs a launch story.

The habit map should list the jobs users already do:

- compare today with yesterday
- check the last run without opening three tabs
- log food quickly, including custom items
- see sleep and naps without mixing stale cards into today
- export or verify data before trusting the new view
- find the same metric name after a rename
- remove incorrect logs without asking a coach to do it
- keep family or child account migration from blocking the main account

Google's roadmap is instructive because many planned fixes point back to those jobs. It includes more dashboard customization, custom food logging, hourly step charts, a combined sleep view, run-label fixes, better data-source labels, and shorter coach messages. Those are not decorative tweaks. They are repairs to daily paths.

The hard counterargument is that old dashboards can trap a product. If every legacy view stays forever, the app becomes a museum of habits, and new users never get the simpler unified design. A migration also has to handle newer data sources, privacy settings, premium features, and devices that did not exist when the old app was designed.

That is fair. But there is a middle position.

Do not freeze the old app. Preserve the old answers.

A forced migration should ship with a compatibility checklist: where each major old metric moved, what was removed, how long data can be exported, which routines now require a different path, which known bugs are open, and whether users can pin the metrics they check daily. If a coach or recommendation layer appears, it should be easy to quiet it until the user has rebuilt trust in the numbers.

The product test is simple: can a long-time user still answer their ordinary question in under a minute on the first week after migration?

If the answer is no, the app did not only change its design. It broke a habit record.

The old dashboard is part of the health record

// COMMENTS

ON THIS PAGE