“We don’t recommend migrating to Health Connect if you’re an existing Google Fit REST API or Fitbit Web API developer. However, we do recommend migrating to Health Connect if you’re already integrated with the Fit Android API.”
“Consider integrating with Google Fit REST API if you want to integrate with the Google Fit ecosystem.”
Hello,
You're saying in your readme that:
Google Fitness API is deprecated and will be turned down in 2024, thus this package will also transition to only support Health Connect.
But according to Google's documentation, only the Android API is being depreciated. As stated here: https://developer.android.com/health-and-fitness/guides/health-connect/migrate/migration-guide
The Google Fit REST API through OAuth is not being deprecated, and it seems that this is the one you are using for Google Fit interconnection.
Isn't there a misunderstanding on Google's announcements here? Can you confirm that you're really going only to support health connect going forward?
Thanks a lot
A lot if info here: https://developer.android.com/health-and-fitness/guides/health-connect/migrate/comparison-guide
“We don’t recommend migrating to Health Connect if you’re an existing Google Fit REST API or Fitbit Web API developer. However, we do recommend migrating to Health Connect if you’re already integrated with the Fit Android API.”
“Consider integrating with Google Fit REST API if you want to integrate with the Google Fit ecosystem.”