CSS Loaders and Spinners
codepen.io
codepen.io
In all seriousness, they are beautiful but raise the concern that we are back to the days of Flash-style loaders before users get to see content.
None of these grab and say "I'm a busy waiting spinner". Let's not re-invent trivial things that are the way they are for a reason, I think EthanEtienne has the right idea, working on getting rid of them is the real innovation, not changing the way they look.
What's wonderful about the web is the ease of distribution. As I see more and more spinners, I'm becoming increasingly worried that the standards will become the new Flash. For an example of a website that bothers the hell out of me with it's loading is Blogspot.
Examples that are useful:
- Credit card processing (always seems to take 2-3 seconds)
- Big database query (searching maybe. But don't do this in regular webapps, just in those where the user expects the query to take some time, like in enterprise apps).
- Uploading or downloading a small file that takes a few seconds (instead of a progress bar that is misleading on small files)
- Buffering audio/video
Whenever you see a spinner or loading icon, you failed in UX design. Most of these feel slow and just plain wrong, they are pretty though, and the CSS is pretty awesome.
Use content progression instead of these damn spinners or loaders. Game dev's learned this a long time ago.
- my worthless 2c rant
I'd rather have a loading screen with a bit of interesting info about the game that I might find useful. Borderlands 2 does this but my SSD loads the levels so fast I usually can't read them.
It's not visible in the previews, but is when you click through.