Fitbit just became Google Health · May 7, 2026
Fitbit is gone. Some will rebuild their dashboards.
Others will ask who they were running for in the first place.
On May 7, 2026, Google launched the Fitbit Air ($99.99, screenless, ships May 26) and announced the Fitbit app's rebrand to Google Health, going live May 19. Fitbit Premium becomes Google Health Premium ($9.99/mo, $99.99/yr). The new Gemini-powered Health Coach exits preview the same day and goes global. The September Web API shutdown is still coming, but the brand is already gone.
Dozens of migration guides will tell you which sync app to download next. This page is not one of them. CityHeart is not a sync app, it is the answer to a quieter question : why do you actually run?
14-day refund if unused Stripe checkout 3,000+ hearts drawn
The migration timeline (factual)
Sourced directly from the Google Health API documentation. Refresh annually.
- May 7, 2026
Google launches Fitbit Air ($99.99, screenless, ships May 26) and announces the Fitbit app rebrand to Google Health. End of the Fitbit brand on software.
- May 19, 2026
Fitbit app officially becomes Google Health. Fitbit Premium becomes Google Health Premium ($9.99/mo, $99.99/yr, up from $79.99/yr). Gemini-powered Google Health Coach exits preview and goes global.
- July 2026 (expected)
Last fully supported month for legacy Fitbit Web API third-party integrations. Apps still relying on it must migrate to the Google Health API.
- September 2026
Fitbit Web API turns down per Google's published timeline. All third-party apps relying on it stop syncing data unless migrated.
- End of 2026
Google Fit APIs reach end of service. Health Connect becomes the canonical Android health-data layer.
What you might lose
Be honest with yourself: forced migrations always lose something. Here is what is worth backing up before September.
- Third-party GPX export to apps that used the Fitbit Web API stops working.
- Older Fitbit Premium custom workouts may not survive the migration to Google account auth.
- Apps connecting to "Fitbit data" without migrating to Google Health API will silently fail after September.
- Any local backup you have of your historic GPX matters, once it is gone from Fitbit, getting it back is hard.
Tip, go to your Fitbit dashboard before September and request a full data export. You will keep your activity history even if your sync app changes.
What CityHeart does, honestly
We are not a Fitbit replacement. We are a different product entirely, and we think some of you, when the dust settles, will want it.
- Heart-shaped GPS routes through real streets, dedicated to a person or cause.
- GPX file exported per route, works on every GPS watch that lets you sideload a planned course: Garmin, Apple Watch (via WorkOutDoors and similar), Coros, Suunto.
- Pixel Watch and Samsung Galaxy Watch support is rolling out via Health Connect in 2026.
- No analytics-only relationship, every route is dedicated to someone, named on your watch and in your Strava activity title.
Honest note about Fitbit-branded watches: we do not work on Charge, Sense, Versa, or Inspire. The hardware does not support loading a planned course to follow during a run, that is a watch- firmware feature, not an API one, and Health Connect does not change it. If you are shopping for your next watch in 2026, the list above is what works with CityHeart today.
The pitch in one line: When Fitbit closes, some will rebuild their dashboards. Others will pick a new watch and run a heart-shaped route through their city for someone they love, with that person's name carried in the GPX route title. CityHeart is for the second group.
We'll ping you when Health Connect ships
One email when CityHeart's Health Connect integration goes live in 2026, plus a heads-up the week the legacy Fitbit Web API breaks. No spam.
Run your first heart
Free preview. Pay only when you download. 14-day refund if unused. Your dedication name is baked into the GPX so it follows you onto your watch.
Read more, Google Health GPX · From Huawei · About CityHeart