3 ms·
I disagree a little with their point on avoiding error codes, just messages; codes can be used for an easy reference with a customer support department, and eas
by roteakin 3y ago
I disagree a little with their point on avoiding error codes, just messages; codes can be used for an easy reference with a customer support department, and easy reference for tech support as well.
But yes, show the friendly, descriptive error message in large, bold letters, and let the user know which code to rephrase if they need to call support.
- mrweasel 3y agoSadly we frequently only see the error codes and a pointless message. I have a local streaming app on my AppleTV. When, not if, it crashes you get "Error, code: 12345X, use this code if you contact customer support." Customer support may have a spreadsheet where they can lookup the code, but as a user, that's pretty pointless. It would be better for the customer to get the error "Something in the application crashed, please restart" or "Something bad happened at our end, there's nothing you can do, we have been automatically notified."
- dfxm12 3y agoThe context is about giving a user advice on how to overcome an issue. To an end user: Merely displaying "Error code 429" is terrible, of course. "Contact the help desk like this and let them know the error code is 429" is better. Norman doesn't seem to be against this if there is nothing the user can do to handle the error on their own. If error code 429 is something the user can fix (maybe they need to wait 3 minutes before trying again), then just letting them know that is best.