Earlier this week, the company detailed how the "Google Fit APIs have been deprecated" and that the shutdown is set for June 30, 2025.
    • realbadat@programming.devEnglish
      0·
      5 months ago

      If it uses health connect to send the data it’s still all good. And if you bought something recently made, it should.

        • realbadat@programming.devEnglish
          1·
          5 months ago

          Just to be clear - it’s the API that’s shutting down, not the app. Not that Google has put in effort for the app either, it hasn’t updated since health connect afaik, but health connect is the health and fitness tooling going forward.

          Fitbit has health connect support now, so even if they shift and drop Fit (I hope not, though I also hoped they wouldn’t kill the web interface), and make Fitbit the main Google fitness app, it will still work with Fitbit as the app.

  • Carighan Maconar@lemmy.worldEnglish
    0·
    5 months ago

    This is just shutting down an already outdated API. Devs should be moving off of it, and now it has a year out set for full removal instead of just being deprecated.

    • Moonrise2473@feddit.itEnglish
      1·
      5 months ago

      But in typical Google fashion, the replacement is inferior and doesn’t have the same features

      However, there is no replacement for the Goals API that lets Google Fit users set “how many steps and heart points they want to aim for each day.”

    • Scrubbles@poptalk.scrubbles.techEnglish
      1·
      5 months ago

      If it’s not killed by google, it’s replaced with a crappier version. Having developed against many Google APIs, “deprecation” is a very frequent word they use. Most of the time there is no stated reason why an API had to be deprecated, just that it is being deprecated. They also give minimal time to switch over, the worst one I had was PubSub’s API having a mandated migration we had to perform - in under 3 weeks. Very difficult for an already tasked team of engineers who had a mountain of other more pressing work. Why I actively push against working on GCP, or google products at all. I’ve successfully pushed 2 companies away from using Google cloud now.

      Microsoft, as an example of the opposite, will have years long deprecation strategies, and usually go overboard with making sure engineers have a good replacement, and documentation on how to migrate. They have a lot to be hated for, but damn are they good with managing downstream engineers.

      • FalseMyrmidon@kbin.run
        1·
        5 months ago

        AWS also rarely turns off services that customers are using going so far as to support customers using outdated services for years. Of the major cloud providers only Google does this.

        • mindlight@lemm.eeEnglish
          1·
          5 months ago

          History is full of companies who went under because they didn’t analyze and predict what would hurt their bottom line…