Why do we still have the 7 day limitation of HealthKit data on Apple Watch?

Question

Created 3w

Replies 1

Boosts 1

Participants 1

It may have made sense in the early days of watchOS, but given the Apple Watch is now 10 years old and we have "Standalone" Apple Watch apps, it no longer makes sense to have this seemingly arbitrary limitation of only being able to query 7 days of data on the watch. I have an open feedback (FB7649612) from 2020 with no responses and ask this question every year at WWDC Developer labs. WHY must we still deal with this limitation which only causes other developers to store critical health data in iCloud or on their own servers in order to provide a robust stand alone watch experience on the Apple Watch. Even Apple themselves must either use a separate private API or use iCloud for the new Vitals app. How else can I escalate this request?

Boost

Answer 1

codingLawyer OP

2w

I thought maybe my my use cases might help better explain why this is needed, here are a few: (1) My App, Athlytic, compares your current HRV, Resting Heart Rate, Respiratory Rate, Blood Oxygen, and Wrist Temp to your 60 day baselines. Because of this limitation I cannot make this comparison on the watch. (2) My App stores your most commonly used workout types to populate a list of workouts to choose from to start. However if you go on vacation longer than 7 days, I have no way of knowing what your previous workouts were to populate the list resulting in a poor user experience. My app compares your Restorative Sleep (REM and Deep) from last night vs. your 60 day average. I cannot do this on the watch. There are many many other examples but these are just a few.

2