Comment by xmddmx | Hacker News Reader

Comment by xmddmx | Hacker News Reader

Agree - I've had almost all of these problems with Siri.

Another thing I've noticed is the horrible lag with updating the UI. An example: On Apple Watch I have the temperature complication bottom center. It sometimes shows the current temperature, sometimes it hasn't updated in minutes or hours (bug #1). For example right now, it shows 66 which I know is incorrect. I tap it to go to the Weather app, a different temperature will be shown (56) (bug #2) and then about 10 seconds later (bug #3) it finally updates to the actual temperature (72).

If I go back to the home screen, finally the complication shows the correct temperature (72).

These kind of async refresh bugs are not unique to WatchOS, it's endemic throughout the Apple ecosystem.

Why? Is this poorly coded JavaScript web view apps? Is this React? Some sort of other async framework that works fine when you are testing on the Apple campus but doesn't work in the real world?

Or you open the Weather app, it updates, you walk somewhere without cell phone reception, open the weather app again, and it shows the old temperature, and suddenly it shows --. Temperature gone. WHY?

This is just background updates being slow

Right, that seems to be what is happening.

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)

There is an API, they are just not updated together

Reply on news.ycombinator.com