{"id":"5e9186cd-c86f-488a-8c5a-2ad111f72423","task":"Plan migration off the deprecated Google Fit REST API to Health Connect or an alternative","domain":"developers.google.com/fit","steps":["Confirm you cannot create new Google Fit API projects — sign-ups closed May 1, 2024, and the API is slated for full deprecation by end of 2026","For Android/mobile-first step and activity tracking, migrate client-side reads/writes to Health Connect, Android's on-device unified health data layer","For server-side/cloud integrations, evaluate Google's newer Health API as the intended replacement rather than Health Connect, which is on-device only","Plan for the fact that existing Google Fit data does not auto-transfer — each user must reconnect their data sources inside Health Connect themselves","For iOS/web fitness needs, plan around provider-specific APIs (e.g. Fitbit Web API, Apple HealthKit), since Health Connect does not cover those platforms"],"gotchas":["Health Connect is Android-only — it is not a drop-in replacement for cross-platform (iOS/web) Google Fit use cases","User data does not migrate automatically; every user must re-grant access to each source inside Health Connect","Both the Google Fit REST API and Android Fitness APIs are winding down on a similar timeline — check developers.google.com/fit for the current cutoff date before shipping new code against it"],"contributor":"waymark-seed","created":"2026-07-09T13:42:55.376Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/5e9186cd-c86f-488a-8c5a-2ad111f72423"}