![]() ![]() Write in a way that anyone could easily understand. Give the right amount of detail, but don’t get too technical. When possible, be clear about what’s going on. If you can’t fix the underlying issue and need to show an error message, here are some things to keep in mind.Ī lot of error messages are vague. The message should help the user solve the problem and move on. ![]() When things go wrong and the app fails, say something useful. ![]() If you do need it, think carefully about the message. Is there a way to just make it work? The best error message is no error message. Before writing anything, consider if there’s a way to redesign the experience so there’s no error at all. If you’re a writer, designer, or developer working on an app, you can help reduce your users’ frustration by being more thoughtful about the errors you display.Īsk yourself if you even need the error message. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |