I was wondering if it would be difficult, or detrimental to battery life to add heart rate variability to the API that watch apps/watch faces could access. It’s an interesting metric, and I have some health reasons for wanting this metric. According to github copilot, I could “sort of” access this metric by changing the heart rate sampling rate and doing stuff with that, but, to be honest, I have not actually checked that that’s possible.
Thanks
It appears that a developer could set the sample rate down to every second. I would also suppose that if an app ran continuously at that sampling rate, the battery would negatively be affected. How much, I cannot say. The Pebble watch itself has limited storage so the sampling data would probably need to be cached on the watch then periodically fed to a Javascript “Settings” page to store locally on the phone. The JS page would then need to do its calculations to yield results longer term. That said, would running continuously even be needed? If one needed continuous feedback of the time between beats, there would be better alternatives than a wearable. However to monitor over time and get a deviation from a norm, I’d say is probably very realistic. Interesting project.