That's kind of a trademark of Apple, they absolutely hate showing progress and detailed information about what's going on (maybe for design reasons? Who knows). When it does not work, there's generally no way to know what's happening and why.
That's kind of a trademark of Apple, they absolutely hate showing progress and detailed information about what's going on (maybe for design reasons? Who knows). When it does not work, there's generally no way to know what's happening and why.
Not that windows is much better
Since Microsoft went the UWP route, these nice error codes have been starting to vanish. Probably because when end users see an error they don't understand, their mind goes blank and their instinct is to click whatever button that makes the error go away, leading to confusion. A simple "try again later" will be a much more enjoyable experience for non-technical people than "Could not update your computer. The foobar failed to parse the widget tree (0xc0000005). Try again later."
When I did customer service, this trend had always irked me about Apple devices. I've had to tell a lot of people to contact Apple (which they never did of course, silently blaming us for their device not working) because all Apple's software said was "try again later".
And now it's spreading to other devices as well. Even if error codes are available, the error messages have been simplified and most error codes aren't documented. I wish there was some kind of generic standard shortcut or gesture that copied the stack trace of any fancy exception to your clipboard so people with technical know-how can actually solve the problem instead of getting told to "try to reboot my router" by a vague, generic help page when Netflix can't find a video stream that matches my video decoding hardware.
I would like to see more details. Sometimes I won't be able to interpret them, often I will be able to, and I'd rather be able to see why something failed so I can fix it.
So we were looking at smartwatches available, and we were deciding between the Apple Watch and fitbits. I was surprised to learn the fitbits give you incredibly detailed data on the quality of your sleep but Apple watch doesn't... and I was thinking huh, that's strange, certainly the Apple Watch has the sensors to be able to produce the data and Apple has the engineering talent to make sense of the data and present it to the end-user in a meaningfully appropriate manner.
I can't find the article now, but apparently it came out from Apple engineers that they ultimately chose not to disclose detailed data to the user because burdening the end-user with this information can cause a mental overload... so instead Apple opted to focus on developing habits (hence the 'go to sleep' notifications and the clever sleep-hour alarms).
I've had some time to reflect on this since I was having these conversations with my acquaintances... and I've gotta say, I think I agree with Apple's approach.
Maybe they care how the user feels about getting stuck at "99% complete" for long periods, caused by uncertainties. Seriously.
Also, I don't treat my kid that way.