Nah. We have a spinner, but I also have a timeout handler. The reason is that the app's backend (and many of the servers on which it depends) can be hosted on

Nah. We have a spinner, but I also have a timeout handler. The reason is that the app's backend (and many of the servers on which it depends) can be hosted on the lowest-tier-dogshit-shared-hosting plan. I would love to have a better backend server, but we are a nonprofit, and can't afford better. This app would be a lot faster, with a more robust backend. But error handling/reporting is a true art, and should never be an afterthought. In my experience, I need to start thinking about error management, as soon as I start planning. In my experience, the best error handling is to not have errors, and, quite often, good UX is the answer to that. If the user doesn't do something that might cause agita, then they don't get an error.