Android

17235 readers

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

💡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: [email protected]

For fresh communities, lemmy apps, and instance updates: [email protected]

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below

Rules

Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
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.
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.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

See thread

Chat and More

founded 1 year ago

MODERATORS

[email protected]

153

Google Fit dev APIs shutdown set, fate of Android & Wear OS apps go unannounced (9to5google.com)

submitted 3 months ago by [email protected] to c/[email protected]

39 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 37 points 3 months ago (1 children)

Dang, I just got a heart monitor that synced to Google fit to get my target heart points tracked...

[–] [email protected] 9 points 3 months ago (2 children)

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

[–] [email protected] 2 points 3 months ago (1 children)

Health Connect "beta" is a battery hog. Until they fix those issues, it's a non-starter for anyone caring about battery life.

[–] [email protected] 4 points 3 months ago* (last edited 3 months ago)

Not really the question I was answering, but that's not actually a health connect problem.

Withings had an issue, and the way they were connecting to it, which caused a battery drain. To be specific, withings health mate was constantly reading health connect data, which caused a massive power drain.

I'm not aware of any other battery issues with health connect other than Withings and their Health Mate app (specifically reading, not writing).

(Edit: why, why would autocorrect change writing to riding? For shame. To me, for not noticing sooner.)

[–] [email protected] 2 points 3 months ago (1 children)

😅 ok great.

[–] [email protected] 7 points 3 months ago (1 children)

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.

[–] [email protected] 1 points 3 months ago (1 children)

I'm using polar bears. 🤞

[–] [email protected] 1 points 3 months ago (1 children)

I've got a polar h10 myself, I know their app still connects to Fit not health connect, but I'm sure they will update.

I actually made an app to make use of health connect with my polar h10 for entirely different purposes, it's really a pretty minor backend change for them to make, so I'm sure Beat will get an update.

[–] [email protected] 1 points 3 months ago (1 children)

I got the coospo one, but found the polar apps easy enough to use.

[–] [email protected] 1 points 3 months ago

Got it, checking their list of compatible apps...

Worst case you could connect to Strava as a go-between should polar be far behind on health connect (again, doubt they would be).

But checking the coospo compatibility, it seems there are a ton of them that all support health connect with coospo, so you wouldn't be shut out even if health connect wasn't ready for Polar, you'll have a ton of options. Including using polar to sync to something that syncs via health connect.

Which is kind of what I do btw, aside from the app for the completely irregular use case I mentioned, I sync polar to Strava, Strava to Fit via health connect. I do that because fairly often I am using polar while cycling, so that's how I want my data to go. But I then found strength training shares nicely too, and running polar beat and my workout app, I can track all my workout routine items (jefit), which syncs via health connect, and then polar goes to Strava goes to health connect, and it all shows as a single session with great HR data.

So yeah, you'll be fine.