As of May 11, 2026, it’s hard to ignore the impact of Google’s latest move: the Fitbit app is no more, replaced by Google Health. According to 9to5Google, this changeover might be a blessing in disguise. When you consider that Fitbit’s user base has been rapidly growing, with over 30 million active users in Q4 2025 [1], it’s clear that Google’s motivation isn’t just about revamping the app – it’s about revolutionizing the wearable market.
Key Takeaways
- Fitbit’s user base grew to 30 million active users in Q4 2025.
- The Fitbit app is being replaced by Google Health.
- Google’s move seems to be a strategic shift towards integrating wearables with its broader health ecosystem.
- This changeover is expected to bring both excitement and concern to the wearable tech industry.
- The future of wearable devices, such as smartwatches and fitness trackers, is uncertain.
Google’s Ambitious Bet on Wearable Tech
Google’s decision to replace Fitbit with Google Health is not just a minor update; it’s a significant shift in the company’s strategy. According to the 9to5Google report, Google Health will enable users to track their fitness data, medication, and other health metrics in one place
“It’s like a digital hub for your health and wellness journey,” says Google spokesperson.
This new approach will undoubtedly simplify the user experience and potentially open up new revenue streams for Google through targeted advertising and partnerships.
The pivot also reflects Google’s long-standing interest in health data. Back in 2017, the company launched Google Fit with a narrow focus: step counting and activity tracking. It didn’t gain much traction. The 2021 acquisition of Fitbit for $2.1 billion was the first real signal that Google was serious about health. That deal came with regulatory scrutiny, especially in the EU and U.S. where antitrust bodies demanded assurances that health data wouldn’t be mixed with ad profiles. Google agreed to keep Fitbit data separate—at least for ten years.
Now, with Google Health, those barriers appear to be softening. The company isn’t just rebranding Fitbit—it’s absorbing it. The new app combines Fitbit’s hardware-driven fitness insights with Google’s software muscle, cloud infrastructure, and AI capabilities. Users will see features like automated sleep staging, heart rate anomaly detection, and medication reminders—all pulled from multiple sources, including third-party apps and connected devices.
This isn’t just about convenience. It’s about lock-in. By centralizing health data under one roof, Google increases the friction for users who might consider switching ecosystems. Once your sleep patterns, workout history, and prescription logs live in Google Health, jumping to Apple Health or Samsung Health becomes more complicated. That’s intentional.
The End of Fitbit as We Know It
The Fitbit app, as we knew it, is gone. This changeover is a direct result of Google’s desire to integrate wearables with its broader health ecosystem. The integration of Google Fit (a fitness tracking app) with Google Health will create a smooth experience for users, allowing them to track their health metrics across different devices and platforms.
For longtime Fitbit users, the change is jarring. The app they’ve used for years—known for its clean interface, detailed workout summaries, and social challenges—has been stripped away. Some features, like community badges and step streaks, are missing. Others, like heart rate zone tracking, have been buried under new menus. Google says these will return in updated forms, but there’s no timeline.
What’s clear is that Fitbit is no longer a standalone brand in the way it once was. The hardware still carries the Fitbit name—devices like the Charge 6 and Sense 3 are still on shelves—but the software experience is now indistinguishable from Google’s own ecosystem. The Fitbit website now redirects to a Google Health landing page. Customer support is handled through Google accounts. Even firmware updates are pushed via Google Play Services.
This transition was always likely. Google didn’t buy Fitbit to preserve its brand identity. It bought it to accelerate its entry into health tech. The old Fitbit app was a patchwork of features built over 15 years. Google Health is a clean slate—one built with scalability in mind.
Health Data in the Cloud
Google Health will store users’ health data in the cloud, making it accessible from any device. This move has raised concerns about data security and privacy. If users are not comfortable with their health data being stored in the cloud, they might opt for alternative solutions, such as cloud-based health apps. However, Google’s emphasis on HIPAA compliance and data encryption ensures that sensitive information remains secure.
The company says all health data is encrypted in transit and at rest. It’s also stored in isolated databases separate from other Google services like Search, YouTube, and Gmail. For now, Google maintains that this data won’t be used for advertising. But that promise is limited. The ten-year commitment made during the Fitbit acquisition only applies to data collected through Fitbit devices. Google Health aggregates data from multiple sources—third-party apps, manual entries, connected scales, and even smartwatches from other brands. That gray area could become a battleground.
And while HIPAA compliance applies to certain health information when handled by covered entities (like insurers or providers), Google Health is primarily a consumer app. That means it’s not fully bound by HIPAA unless it’s sharing data with a healthcare partner under a business associate agreement. So while the app may meet some standards, it’s not the same level of protection you’d get from a medical record system.
Still, Google’s infrastructure offers advantages. Cloud storage means users can recover years of step counts, sleep logs, and heart rate variability data even after losing or replacing a device. Developers can build apps that pull from this data across sessions and devices. Machine learning models can analyze long-term trends to flag potential health risks—like irregular heart rhythms or declining activity levels—before they become emergencies.
But the trade-off is visibility. When your data lives in the cloud, you lose direct control. You can download it, sure, but you can’t run a local server to host it. You can’t audit every access request. You’re trusting Google’s systems—and Google’s future priorities.
Competition and the Future of Wearable Devices
The changeover from Fitbit to Google Health will undoubtedly impact the wearable market. Companies like Apple, Samsung, and Huawei will need to adapt their strategies to remain competitive. The future of wearable devices, such as smartwatches and fitness trackers, is uncertain. Will Google’s move spark innovation, or will it lead to a decline in the market? Only.
Apple has long dominated the premium wearable space with the Apple Watch. Its tight integration with iPhone, ECG feature, and fall detection have made it a favorite among health-conscious users. But Apple keeps its health data siloed. You can export it, but you can’t easily push it into third-party systems. Google’s more open approach—allowing data sharing via APIs—could attract developers and clinics looking for interoperability.
Samsung, meanwhile, has been pushing its Samsung Health platform across Galaxy watches and phones. It supports many devices, including non-Samsung wearables, and offers deep insights into sleep, stress, and activity. But it lacks Google’s cloud scale and AI tools. Huawei, despite being hampered by U.S. sanctions, has built a strong health suite in China, focusing on blood oxygen tracking and cardiovascular monitoring.
Google’s move changes the game. By unifying Fitbit’s hardware expertise with Google’s backend, it can offer a full-stack solution: devices, software, cloud analytics, and potential integration with telehealth platforms. That kind of vertical control is rare outside of Apple. And Google’s reach—especially in emerging markets where low-cost Android phones dominate—gives it an edge.
We’re already seeing ripple effects. Fitbit’s decision to discontinue older devices like the Alta and Flex lines suggests Google is focusing on models that can fully support Google Health. Newer devices come with longer battery life, built-in GPS, and improved sensors, all designed to generate richer data for the cloud platform.
But fragmentation remains a problem. Not all Android phones can run Google Health smoothly. Some manufacturers, like Xiaomi and OnePlus, still preload their own health apps. Carriers sometimes lock down system updates. This uneven rollout could limit adoption in key markets.
What This Means for You
As a developer or builder, this changeover presents both opportunities and challenges. On one hand, integrating Google Health into your app or service can simplify the user experience and increase engagement. On the other hand, adapting to Google’s new ecosystem and ensuring compliance with their standards may require significant effort and investment.
For app developers, Google Health’s API opens doors. Imagine a diabetes management app that pulls step counts, sleep quality, and heart rate data automatically—then syncs insulin logs from a smart pen. Or a mental health platform that correlates mood entries with physical activity and heart rate variability trends. With a unified data source, these integrations become easier to build and maintain.
Founders building digital health startups now have a choice: build on Google’s infrastructure or go independent. Choosing Google means faster development, broader reach, and access to advanced tools like AI-powered trend analysis. But it also means depending on a platform that could change its policies overnight. If Google decides to charge for API access, or restrict certain data points, startups built on its foundation could be left scrambling.
For hardware builders, the message is clearer. If you’re making a fitness tracker or health sensor, compatibility with Google Health is no longer optional—it’s table stakes. The same goes for clinic-facing tools. Telehealth platforms that want to pull patient-generated data will need to support Google Health if they want access to Fitbit users.
There’s also a design challenge. With Google Health handling core tracking, third-party apps need to offer more than basic dashboards. They’ll have to deliver insights, coaching, or clinical value. The bar is rising.
What’s Next for Google and Wearable Tech?
Google’s move to replace Fitbit with Google Health is just the beginning of a new era in wearable tech. we can expect to see more solutions and partnerships emerge. The question is: will Google’s dominance in the wearable market be a welcome change, or will it lead to a decline in competition and innovation?
Key Questions Remaining
What happens to users who don’t want to switch? Google says the old Fitbit app will stop receiving updates after Q3 2026. By the end of the year, it may not work at all. There’s no official path to export every data point—especially detailed workout logs or manual entries. Some users have reported missing data after migrating. If this becomes widespread, it could spark backlash.
Will Google Health support non-Fitbit devices long-term? Right now, it works with a range of wearables, including Garmin and Withings. But Google has a history of deprioritizing third-party integrations when they don’t align with core goals. If the company starts pushing its own hardware, support could dwindle.
And what about the regulatory landscape? The FTC and EU Commission are still monitoring Google’s use of health data. Any move to monetize Google Health data—even indirectly—could trigger investigations. The ten-year pledge not to use Fitbit data for ads expires in 2031. What happens after that?
One thing’s certain: health data is the next frontier for tech giants. It’s personal, continuous, and valuable. Google’s rebranding of Fitbit as Google Health isn’t just a product update. It’s a declaration of intent.
Sources: 9to5Google
