Attention all developers using the Google Fit SDK: the clock is ticking. As part of Google’s ongoing efforts to streamline its services, Google Fit API has been discontinued and will eventually be fully replaced by Health Connect. In this article, we’ll break down the shutdown timeline, outline the necessary steps to ensure a seamless transition, and speculate on what this move might mean for Google’s future plans.
Google’s Fit API Shutdown Timeline
According to Google’s timeline, sign-ups for the Google Fit API have already been stopped, and developers must complete the migration to Health Connect by June 30, 2025, when all Google Fit API services will be discontinued. This includes transitioning apps that rely on the popular REST API. Developers are required to fully integrate with Health Connect by the deadline.
What Developers Need to Do
If you’re currently using Google Fit APIs, there are two main options to handle the transition:
1. Rebuild Infrastructure for Health Connect
This option involves completely re-coding how your application integrates with the new Health Connect system. Here are the essential steps you’ll need to follow:
- Integrate Health Connect: Start by incorporating Health Connect into your app. This includes defining the necessary data types and access modes, as well as implementing read and write functionalities.
- Migrate Gradually: Keep both the Google Fit API and Health Connect active during the transition. This allows you to test new features and gather user feedback while ensuring service continuity.
- Clean Up: Once the migration is complete, remove any Google Fit SDK code from your application, update your documentation, and monitor app performance to ensure everything runs smoothly.
You can find more information about each step in the official migration guide by Android.
While Health Connect offers improved interoperability and data access across devices, this path requires significant redevelopment of your existing integrations, which can be both time-consuming and costly. Additionally, you’ll need to stay alert about future updates to maintain compatibility.
2. Use a Third-Party API Like Spike
For a more streamlined transition, consider using a third-party API aggregator such as Spike:
- Unified Integration: Spike integrates with various health and fitness platforms, including Google Fit and Health Connect, covering over 300 wearables and health data sources. This provides a scalable, all-in-one solution.
- Effortless Implementation: Schedule a demo with Spike and complete a brief questionnaire. Following this, you’ll have an implementation kick-off meeting where Spike’s developers will guide you through the integration process.
- Continuous Support: Benefit from 24/7 support through Slack, allowing you to focus on app development rather than managing infrastructure.
Spike relieves you of the burden of manually handling updates and migrations. Instead, Spike manages all future transitions and upgrades, ensuring that your app stays compatible with the most recent wearables and health platforms, allowing you to focus on development rather than infrastructure maintenance.
Conclusion
With the Google Fit API shutdown looming, developers need to make critical decisions about their infrastructure. Whether you choose to build an in-house solution with Health Connect or work with a third-party API like Spike, the goal should be to minimize disruption and future-proof your app against the fast-evolving wearable industry.