UX Pitfalls > Dealing with Errors = Duplicate

Now that chapter 05: Error Handling exists, we could find space in there for some of the UI related concerns. I have introduced the types of errors a user might experience, and you can pad that out.

Another approach would be taking the "Showing Errors to Users" angle, and talking specifically about what problems can occur when your API client gets API errors it might not expect, or might deal with poorly.

- White screens of death, spitting weird errors right at users, etc.

- Should API errors be reported to API client developers, or API developers, and/or support, so they can do something about it? Not every 404 or validation error, but some should?