Google Fit 迁移常见问题解答
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
此次迁移会影响哪些人？
使用 Google Fit API 和 Google Fit REST API 的所有开发者。
有何变化？
- Google Fit API（包括 Google Fit REST API）将于 2026 年被废弃。
- 自 2024 年 5 月 1 日起，开发者将无法注册使用这些 API。
如何开始？
为用户提供顺畅的过渡体验，请参阅迁移指南。
在迁移期间，我可以使用 Google Fit API 执行哪些操作？
如果您是使用 Android 版 Google 健身 API 的开发者，我们建议您立即迁移到 Android Health API，以确保您向用户提供的服务不会间断。与 Fit API 相比，Android Health API 具有多项优势，包括：
- 记录步数：Android Health 将提供移动设备上的 Recording API，无需 Google 用户账号，也无需您请求访问 API 权限范围。这也是检索步数数据的更省电方式。移动版 Recording API 首先将支持记录步数数据，不久后就会支持记录距离和卡路里数据。
- 健康数据共享：通过与 Health Connect 集成，您的 Android 应用只需一次关联即可访问不断壮大的应用生态系统中的数据。此外，数据存储在设备端，让用户可以完全控制自己的数据。
迁移期过后，Google Fit API 会受到什么影响？
Google 健身 API 将无法再使用。迁移期结束后，您应该已迁移到 Health Connect 或其他 Android Health API。
迁移期过后，Google Fit REST API 会怎么样？
Fit REST API 没有替代方案。
我们建议 Fit REST API 用户迁移到 Android Health API。了解哪种方式最适合您的需求和用户：
- 健康数据共享：Health Connect 会将整个 Android 设备和应用组合中的数据整合到一个生态系统中，为 Android 开发者提供一个通用的健康平台。Health Connect 提供了一个 API 来读取和写入用户的健康数据，在存储时标准化数据架构，并集中处理权限控制。
- Fitbit Web API：Fitbit Web API 是一个平台通用接口，用于与 Fitbit 生态系统集成。借助该 API，用户能够直接在云端存储、共享和管理数据。在 Fitbit Web API 中，用户的数据与其 Fitbit 账号关联而非与其设备关联。这意味着，Fitbit Web API 以账号为中心而不是以设备为中心。
如需了解详情，请参阅 Health Connect 比较指南。
如何获取帮助？
如果您发现了 bug 或需要迁移方面的帮助，请使用我们的问题跟踪器提交反馈。
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-27。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-07-27。"],[],[],null,["# Google Fit Migration FAQ\n\nWho does this migration impact?\n-------------------------------\n\nAll developers who are using the Google Fit APIs and Google Fit REST APIs.\n\nWhat's changing?\n----------------\n\n- The Google Fit APIs, including the Google Fit REST API, will be deprecated in 2026.\n- Developers cannot sign up to use these APIs as of May 1, 2024.\n\nHow do I get started?\n---------------------\n\nTo provide a smooth transition for your users, review the\n[Migration guide](/guide/health-and-fitness/health-connect/migrate/migration-guide).\n\nWhat can I do with my Google Fit APIs during the migration period?\n------------------------------------------------------------------\n\nIf you are a developer using Google Fit APIs for Android, we recommend migrating\nto Android Health APIs now to ensure uninterrupted service for your users.\nAndroid Health APIs offer several advantages over the Fit APIs, including:\n\n- **Recording steps** : Android Health will provide the [Recording API on mobile](/health-and-fitness/guides/recording-api), which doesn't require a Google user account or the need for you to request access to API scopes. It's also a more battery-efficient way to retrieve step count data. The Recording API on Mobile is launched with steps.\n- **Health Connect** : By integrating with [Health Connect](/health-and-fitness/guides/health-connect), your Android app can access data from a growing ecosystem of apps with just one connection. Plus, data is stored on-device, allowing the user to be in full control of their data.\n\nWhat will happen to the Google Fit APIs after the migration period?\n-------------------------------------------------------------------\n\nGoogle Fit APIs will no longer be available for use. After the migration\nperiod, you should have already [migrated to Health Connect](/guide/health-and-fitness/health-connect/migrate/migration-guide) or\nother Android Health APIs.\n\nWhat will happen to the Google Fit REST APIs after the migration period?\n------------------------------------------------------------------------\n\nThere is no alternative to the Fit REST API.\n\nWe encourage Fit REST API users to migrate to the Android Health APIs. See\nwhich one best fits your needs and users:\n\n- **Health Connect**: Health Connect unifies data across Android's portfolio of devices and apps into an ecosystem, providing a common health platform for Android developers. Health Connect provides an API for reading and writing the user's health data, standardizes the data schema upon storage, and centralizes permissions control.\n- **Fitbit Web API**: The Fitbit Web API is a platform-agnostic interface to integrate with the Fitbit ecosystem. It gives users the ability to store, share, and manage their data directly in the cloud. In the Fitbit Web API, the user's data is tied to their Fitbit account instead of their device. This means the Fitbit Web API is account-centric instead of device-centric.\n\nCheck out the [Health Connect comparison guide](/health-and-fitness/guides/health-connect/migrate/comparison-guide) for more\ndetails.\n\nHow do I get help?\n------------------\n\nIf you find a bug or need help with the migration, submit your feedback using\nour [issue tracker](https://issuetracker.google.com/issues/new?component=1676744&template=2072671)."]]
