Live data from Hacker News

Ban the Throbber

banthethrobber.neocities.org

11–14 of 14 posts

Re: Ban the Throbber

#12
There's a place for spinners, but I agree in the sense that the average user shouldn't be waiting for a spinner in an average session. A green path should be a good experience.

An edge-case user should expect it for expected waits of up to 10 seconds (progress bars for 10sec+ expected waits), because their edge case shouldn't inflict preloading on average users. But ghost loading will make it less annoying in any event, and there should be reasonable timeout error handling.

Re: Ban the Throbber

#13
jfc, please no, I already have to use too many apps that don't give any feedback while they are waiting for a request to finish. I am so sick of systems that don't account for request latency, especially on mobile.

The purpose of the throbber is to tell the user that their tap landed on the right place and the app is actually doing something.

Re: Ban the Throbber

#14

The throbber was the beginning of developers gaslighting users. It began as an indicator during long loads that your system hadn't frozen (because whatever process was running had to update it), and became a useless animation that communicated nothing.

Yes, it tells you nothing. It has no relationship to what's going on at the other end, which may well also be nothing.

It tells you that the app is actually doing something and your tap didn't land outside the button.
Post reply on HN