4 ms·
This is a UI/UX pet peeve of mine. For things that people do a lot in your software, I think that extended animations are counter productive, because users quic
by trustfundbaby 13y ago
This is a UI/UX pet peeve of mine. For things that people do a lot in your software, I think that extended animations are counter productive, because users quickly get used to and irritated by them, since they get in the way of what they're trying to do.
Personally, I like to only use animations for things that don't happen very often at all, they help make those particular experiences more memorable.
- bigiain 13y agoOr, when you can use those animations to cover up a time-consuming but not resource heavy operation (waiting for network response, gathering entropy, loading from disk). But even then, the animation should try to explain why you're waiting, not just make you think "the programmer is just making me wait while they show off their stupid animation - again…" (A trick which Microsoft got _so_ wrong with their flying-folders and barber-pole progress bar animations…)
- shurcooL 13y agoSince you can't predict how often a user sees something (it could be someone else using your phone), it's better just to avoid blocking animations altogether. Let the animations be non-blocking. If you wanna go slow, things are unchanged. If you wanna go fast, no one is artificially stopping you.