2 ms·
Indeterminate loading spinners suck. You're only supposed to use them when you don't know how long something is going to take, for example when you're setting u
by jeroenhd 5y ago
Indeterminate loading spinners suck. You're only supposed to use them when you don't know how long something is going to take, for example when you're setting up a socket to a remote server. After that, you're not supposed to use indeterminate spinners anymore.
Skeletons are just another big, flashy indeterminate loading bar. They feel slightly faster because you can get a feel for the content layout, but only as long as the size and behaviour perfectly matches the loaded content. Usually they don't, and the entire screen reflow six times before all the skeletons are loaded in, which take up more precious data to slow down the important parts of your application as well. Most of the time they feel slower because you're actively being tricked as a user by the "almost there" page layout. They're an indeterminate loading spinner in disguise.
If you want to make your code feel faster, show your users that something is happening. Give them actual, real progress bars. Fill up a bar somewhere as content comes streaming in from your myriad of endpoints and unnecessary tracking libraries. Focus on shaving down your load times instead of optimizing the way you show them! Do you really need those four JSON calls to load data that could've been in the HTML the first time?
- tgv 5y agoTo me, an indeterminate spinner says very clearly: no idea how long this may take. Progress bars provide more information, but might be at least as misleading as a spinner. My Netflix app typically loads a movie like this: 0% ... 34% ... 99% ... 99% ... 99% ... 99% ... 99% ... play, although sometimes it does: 0% ... 1% ... 2% ... 2% ... 54% ... play. Fortunately, the netflix progress indicator keeps spinning, so you sort of know that it's to be expected. If it were an unanimated progress bar, I would start suspecting an error when it gets stuck (as it routinely does).
- exodust 5y agoAgree, being stuck on 99% is worse than stuck on a loading spinner. The design problem that gets overlooked is how to inform users that things are taking longer than normal. Even the eventual fail message with "try again later" is often worded and designed without much consistency.
- sharken 5y agoIdeally no percentage increase should take more than maybe 10-15% of the total time. If the website or app consistently violates this, then it is time for a different design. But more often than not the "Good enough, ship it" wins out and the user experience is suffering. I can understand that time to market and maximizing profit is important, but at the second version the expectation is that it is improved. Google was very aware of this with their search engine, so these things matter.
- taneq 5y agoTo take this a step further, "progress indicators" suck when they don't actually give you any indication of how much progress is being made. My personal least favourite example ever is Windows Explorer when it's trying to connect to a network share that isn't there. It looks like an actual progress bar until you realise that it's only asymptotically approaching "done."