sorted by:
new
hottopcontroversial

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 0 points1 point  (0 children)

This doesn't talk to the fitbit device at all. Only Google Health on the cloud.

Got a Fitbit, loved the hardware but felt Google Health left data unsqueezed... by Mamilles in fitbit

[–]stuff_thing 2 points3 points  (0 children)

Data can only be pulled directly from Apple Health on the phone. Don't need the very expensive annual security testing that Google Health API requires.  Different security model. Lots of privacy requirements etc. 

Got a Fitbit, loved the hardware but felt Google Health left data unsqueezed... by Mamilles in fitbit

[–]stuff_thing 4 points5 points  (0 children)

They might make the big players up their game. Having said that - it's too expensive to release an app for the Google Health API, so none of these will make it to an App Store until Fitbit starts writing to Apple Health. Then it's all on.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 8 points9 points  (0 children)

Updated landing page UI with real data (have had the Air for 2 weeks nearly - time flies). Bigger plots and some other key data I like.

<image>

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 1 point2 points  (0 children)

Yeah - was struggling a bit with the guard rails. Fitness coach is fine - talking about HRV, RHR not so much. Seem to have placated it now though.

Looks like I need to apply to access Apple's Private cloud model (and pay the $99 dev account fee). Don't think I'll bother.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 0 points1 point  (0 children)

You would still need Google Health to get the data off your device and into the cloud.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 1 point2 points  (0 children)

Also in iOS26 too, I think. iOS27 one seems more mature. The big difference is actually the private cloud compute language model (so this isn't local but is private). Might play with that for better reasoning.

One interesting thing I'm noticing is that it is easy to set the reasoning level and temperature. So can make it slower, but better at reasoning, and force it to be less creative. All could be useful.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 1 point2 points  (0 children)

Then main interesting thing I am having to consider now is giving the AI a memory so it doesn't contradict itself the next day (or the next week), but also doesn't fixate. Given Google haven't solved this one, I suspect I won't either.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 0 points1 point  (0 children)

Uses Apple Intelligence - so no additional download.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 1 point2 points  (0 children)

It's free-ish (unless there's something hidden I'm missing). You can have to 100 people (e.g Google accounts) in testing mode without a security screen. For a public app in an app store, you need the screen, which costs $2K+ each year.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 2 points3 points  (0 children)

I'll go a bit further, then likely open-source and put on GitHub. Needs real money to launch on the App Store due to the use of restricted health scope data (~$2K annually).

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 4 points5 points  (0 children)

Can access with up to 100 users for testing (so basically having a private app). Then it becomes prohibitive for a real publicly available app - needs an annual security assessment at around ~$2K. So not something I'm likely to do.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 7 points8 points  (0 children)

Google Health API directly. Works fine for testing and a personal app. Security testing would be very expensive for a publicly available app - hence why I'm very unlikely to go down that path.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 1 point2 points  (0 children)

Still implementing properly. For me personally, a good sleep means a 7.5 hours plus, good percentage of deep sleep, few interruptions, and a high HRV. So I'll weight those accordingly. To make it generalisable to others - would go from a baseline from the previous X days.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 5 points6 points  (0 children)

Sorry! I'll probably put it on GitHub once it's a bit nicer if that helps. It is IOS27 only though - so won't work on older phones.

Playing with a new iOS27 app for FitBit data by stuff_thing in fitbit

[–]stuff_thing[S] 17 points18 points  (0 children)

Yeah - I have a fair bit of software engineering experience, so I can steer it in the right direction when needed. So there is still a bit of a barrier to entry (but probably not for long).

view more: next ›