this post was submitted on 05 May 2024
160 points (93.0% liked)

Android

17681 readers
43 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

πŸ”—Universal Link: !android@lemdro.id


πŸ’‘Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

πŸ’¬Matrix Chat

πŸ’¬Telegram channels / chats

πŸ“°Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Carighan@lemmy.world 68 points 6 months ago (3 children)

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.it 57 points 6 months ago* (last edited 6 months ago) (2 children)

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.”

[–] realbadat@programming.dev 3 points 6 months ago

Health connect doesn't set your step count goals, because what it does in the back end (because that's what it is, the back end API) is set a way to read and write that data.

The front end, Google Fit, also connects to health connect on the back end. And the Fit app is not given a shutdown here, just the API it also uses in the back end.

I suspect Google will stop developing Fit, as they kind of already have. However, all these varieties of other apps out there (Fitbit, Withings Health Mate, Samsung Health, MyFitnessPal, etc) can use health connect data, and do allow you to set goals. They use the same data, and now are more interoperable with Health Connect than they were with the Fit API.

[–] Defaced@lemmy.world 3 points 6 months ago

Come on now, that's not just a Google problem and you know it, no need to shit on Google for something damn near every tech company does. Google does their fair share of shitty things, this isn't really one of them.

[–] scrubbles@poptalk.scrubbles.tech 20 points 6 months ago (3 children)

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.

[–] DeathsEmbrace@lemmy.ml 9 points 6 months ago (1 children)

Wait until you realize Microsoft actually cares only because they have already analyzed and predicted that this would hurt their bottom line.

[–] mindlight@lemm.ee 12 points 6 months ago

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

[–] FalseMyrmidon@kbin.run 6 points 6 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.

[–] hemmes@lemmy.world 1 points 6 months ago

Public Folders have entered the chat

[–] evo@sh.itjust.works 17 points 6 months ago

Yes, worst clickbait title I've seen in a while. Health Connect was announced 2 years ago...