How to design good error messages

When we create new products, the design of error messages is rarely the first thing on our list. We tend to focus more on a happy path, so we leave error states until the end of the design process. However, the way error messages are designed can have a tremendous impact on user. But bad error handling paired with useless error messages can fill users with frustration and can make users abandon your product. This video discusses five important rules worth remembering when you design error states.
Rule 1 - Prevention is better than cure 00:47
Rule 2 - Never rely on the red color alone 04:41
Rule 3 - Write helpful error messages 05:45
Rule 4 - Right place for validation output 07:52
Rule 5 - Validate user input on fly 09:07
----
Twitter: / 101babich
Instagram: / 101babich
#uidesign #ui #userinterface #userexperience #ux #error #productdesign

[@theemplaylist]

Amazing. Thank you for sharing!

[@leoplatt376]

Great video

[@Aranimda]

Error messages are getting worse. Most programmers seem to unable to write an error message more helpful and informative than "Something went wrong, please try again later".