The question I'm asking is "why" - why would Apple ship code that is so horribly broken (from a UI/UX) perspective.
I thought for sure that this slow-temperature-update bug would be fixed in WatchOS 27, but it's just as bad as in 26 and before.
Sometimes the temperature UI will show "--" instead of a temperature, until it finally updates, so clearly they do have code for the "no temperature data" case.
It just boggles the mind that "6 hour stale temperature data" doesn't trigger this same behavior.
There are some very weird rules for this where you get a limited number of updates per hour/day and if you eat your budget then you don’t get any more. Or if you crash a bunch the system will just stop asking you for new data. It’s an odd, somewhat inscrutable system
If only Apple computer had employees that would fix this system (that they are 100% responsible for building) :-)
Even if Apple is too cheap to pay the $0.00001 to get me real time temperature updates, you would think there would be an OS API to query the temperature, and that the various apps and complications would query this to get the source of truth.
But from the actual UI/UX, it must be that every App, and complication, and UI element are caching their own value.
That's the only way I can explain seeing 3 different temperatures displayed within a few seconds.
(NB: these are all Apple apps, I'm not using any third party apps)
The question I'm asking is "why" - why would Apple ship code that is so horribly broken (from a UI/UX) perspective.
I thought for sure that this slow-temperature-update bug would be fixed in WatchOS 27, but it's just as bad as in 26 and before.
Sometimes the temperature UI will show "--" instead of a temperature, until it finally updates, so clearly they do have code for the "no temperature data" case.
It just boggles the mind that "6 hour stale temperature data" doesn't trigger this same behavior.