zlacker

>>walter+(OP)
I think the Apple software UI team has cultural problem in adhering to "one source of truth", and that's where most of the problems come from. I've seen this many many times throughout the years, from toggles, to actions, account creation (I have dupes from tapping a button too fast), etc: the UI doesn't match the internal state.

Another example is most any toggle that's linked to Apple cloud stuffs, like settings in your iCloud account or parental controls. You see it toggle immediately, but that's unrelated to the actual state. You can't know the actual state until you exit the page and go back. Meta gets this right with their apps: you toggle, the toggle turns disabled, then the toggle is re-enabled when the state is confirmed remote side.

>>nomel+xc1
Part of apple’s language design is to not show failure whenever possible.

It’s everywhere once you’re told. at most a loading icon remains loading or a setting resets itself when you don’t look, but those “there was an error -accept” popups that are a constant in windows are rarely seen this side of the fence.

It tends to become stupid when the network is involved, where lack of coverage, interrupted downloads and the like are common. They have to show it just works I guess.

>>kace91+Fh1
and you know what, that actually might be reasonable if the iPhone was smart enough to retry a few times - either with exponential backoff or when network connectivity is restored.

instead, it just pretends everything is working great lol.