Suggestion for metrics collection
-
Watches collect different metrics like heart-rate, altitude, steps, temperature, battery percentage, hours of activities in the last 4 weeks …
Seeing how watch-face complications only supports some of them, and how the interfaces to display them differ, I’m assuming the firmware is not collecting them in a unified way.
If this is correct, it would be great to unify the way they are collected, and beyond that, have a registry of all collected metrics made available throughout the firmware.This design would allow choosing any metric in the watch-faces complications without the need to deal explicitly with individual metrics. It would also allow for a unified interface to display similar metrics: timeseries (like altitude and heart-rate), or counters (like steps and hours of activities) would be displayed by the same interface, making user experience more consistent, but also opening the door to improvements that would benefit every interface showing similar metrics.
An improvement that I would like to see for instance is the ability to zoom on timeseries metrics like altitude or heartrate, instead of being stuck to a fixed window. Or having the ability to display evolution of battery percentage or temperature in a watch-face complication. Or having a way to display the evolution of steps-per-day in the last 4 weeks.
Just my thoughts, I don’t know if this forum is a good place to post this suggestion. Please help me move this post to a better location if it’s not.
-
For me, this sounds like you want too much interaction with too much data on a very tiny screen. It would be very clumsy to do so.
The suunto app would be the place to look into data in more detail (if you think that would be useful)
-
I’m not sure I understand your comment.
My watch-face can display a history of altitude in the last 6 hours, but cannot display a history of temperature in the last 6 hours.
My watch-face can display the hours of training per week for the last 4 weeks, but cannot display the footsteps per week for the last 4 weeks.
The way heart rate history is shown is different than the way the altitude history is shown.
All these elements indicate that these metrics are not dealt with in a unified way.Consequence is that ever watch-face developer needs to deal individually with every metric they want to support, which is more complex and difficult to maintain.
This goes beyond watch-faces of course, but it’s probably the easiest to illustrate the point.
-
You also talked about this interaction with data, like zoom and selecting a display window. That is what a mean by too complex for a tiny screen.
And I don’t think you can draw a conclusion how data is handled based on how different parts of the ui look. The data can be the same but the widgets might be programmed by different people over a longer period in time (older widgets might not have been rewritten to benefit from newer functions in the os)
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login