that goes both ways. if you show the wpa_supplicant message, my mother wouldn't even understand if she is connected or not. nor would she gain anything by that information. you just came up with the other side of the same coin of terrible UX.
that goes both ways. if you show the wpa_supplicant message, my mother wouldn't even understand if she is connected or not. nor would she gain anything by that information. you just came up with the other side of the same coin of terrible UX.
>> On wpa_supplicant: 'associating... atempting authentication... getting dhcpc lease... dhcp timed out'
>> One says "sorry computer doesn't work" and the other tells you what you need to deal with the problem. Stop infantilising users, it's disrespectful and counter productive.
> that goes both ways. if you show the wpa_supplicant message, my mother wouldn't even understand if she is connected or not. nor would she gain anything by that information. you just came up with the other side of the same coin of terrible UX.
Yes, you need both. When I write error messages, I try to combine a "user friendly" summary with more technical information and a suggested action, e.g.:
"Wifi connection failed: dhcp timed out. Try reconnecting or checking the router's configuration."
If you don't communicate both, someone's going to be frustrated. And even nontechnical people who have no idea what DHCP is benefit from mentioning it in the message, since it gives them something to Google.
Honestly, I think those people can't be helped. They're technically helpless and catering to them makes everyone else as helpless as they are, which is a net loss.
We don't say "those people can't be helped" about people who are blind or deaf.
Well, we shouldn't. Many web designers seem to feel that way, though.
How is an impenetrable technical error code less scary than a pithy description of the actual problem? Eg.
"Wifi connection failed: dhcp timed out. Try reconnecting or checking the router's configuration."
vs
"Wifi connection failed: Code -49291994. Try reconnecting or checking the router's configuration."
For a real world example: https://www.flickr.com/photos/daveward/69888365
I'm not talking about dumping a stacktrace or dropping them into a debugger.
> We don't say "those people can't be helped" about people who are blind or deaf.
We also don't gouge out the eyes of sighted people because blind people exist, either.
The worst example I run into is when you get a notice that someone has tried and failed to login to your Gmail/iCloud/etc account, it tells you to change your password in the helpful suggestions. Why would you do that?
'not connected. more info: blah #32893289327". Microsoft did something similar with an error code that you could google. that was super useful for debugging. the error message was in laymen terms though.
Error IDs on everything, please.
I've done a little end-user support, and this is a pretty optimistic take on what you'd get. It would probably be more like "It didn't work." in both cases. Maybe you'd get "there was an error message"
Q: What do you see on your screen? A: Nothing
Q: Try again and tell me what happens. A: It didn't work and I still don't see anything.
Many people have an automatic reactions to any kind of error or message. They get dismissed automatically. It seems that some people don't even realize they're doing it.