The one I hate is the error message that simply says "Something went wrong." maybe with a frowning cat icon, but with no other diagnostic message that could be used to determined what exactly went wrong and what corrective action to take.

Thank you, computer, for being totally unhelpful.

> error message that simply says "Something went wrong."

Actually, are there HCI guidelines for communicating inexplicable internal errors to the user? I definitely write assertions that really should never ever fail - if they do, we are in a completely unanticipated state. Either there's been a truly massive logic bug, or maybe even a memory error flipped a bit, but in either case, I have no idea what state the program is in or what caused it to get there.

What would a good tech writer tell the user in this situation? I can't think of anything all that much more helpful than "something went wrong". Maybe "There is a serious bug in the program, totally our fault, please help us by reporting it"?

This annoys me so much, and it's another reason I hate phone apps, because they do this all the time. Usually ANY error resolves to "something went wrong". I'm not expecting a stack trace, but they're too scared to show the user ANY tech jargon at all, and it's another reason why young people are computer illiterate. At least I can access the developer console on modern webshit when using an actual computer.

I had to logcat an app recently which failed with no error at all incidentally, to find out it was overzealous DNS blocking that prevented it from talking to its api endpoint. I don't to Android development, but I'm guessing apps would be aware of name resolution failures, and should be able to tell the user about it, without using fucking logcat.