upvote
The vast majority of designers prefer animations. Without animations, there would be less jobs for designers. But I haven't seen any evidence that ordinary people prefer animations. Most ordinary people aren't even aware that it's possible to turn animations off, because the designers make this difficult.
reply
> But I haven't seen any evidence that ordinary people prefer animations.

There are mountains of evidence supporting the idea that people prefer animated UIs over static UIs going back decades. This is true even in the world of TUIs, again, going back decades. I genuinely don't understand how you can make this statement so confidently.

reply
Maybe if the question is “hey was that fancy animation really cool?”

Animation, used judiciously to communicate valuable information about the UX, is good. Most of the rest is only tolerable so long as it doesn’t slow anything down or change how scrolling works.

reply
A UI should be reactive rather than proactive. Any state changes should be explicitly requested by the user, who naturally knows what they requested, making "informative" animations redundant.

However, there is one legitimate use for UI animations: making it easier for spectators to follow what's happening. Spectators aren't the ones making the requests, so they can be confused if things happen too fast. Most computer use is not done for the benefit of spectators, so animations should be disabled by default, but it's beneficial to have the option of enabling them.

reply
> Any state changes should be explicitly requested by the user, who naturally knows what they requested, making "informative" animations redundant.

I can't really follow your thought process here for two reasons:

1. "Informative animations" (I interpret this as not-feedback-for-UI-interaction animations) are usually based on the response, not the request. So the user doesn't know the info which the animation communicates.

2. Most users immediately want some tiny acknowledgement of their request, e.g. a button's state changing (base -> pressed -> active/disabled). If the request takes longer than a few seconds, users really want a loading animation - otherwise they're less likely to wait until the response comes back, even if they know that it takes a long time. At least that's been my experience.

reply
We had functionally complete GUIs in the 90s. If something takes more than a few milliseconds to respond after 3 decades of hardware progress there's definitely something wrong.
reply
If we're talking about local CRUD, sure, but that's a tiny minority of use cases. As soon as your application does network requests outside your LAN, less than a few milliseconds is impossible for most regular users and developers. That's not to mention tons and tons of processes that definitely take more than a few milliseconds, like: compiling a meaningfully big codebase, compressing/uncompressing most files, rendering a video, ...

Those are just a few examples. What is the "something" that's wrong with all of us?

reply
Where can I find this evidence?
reply
Asking this in the age of AI says a lot...
reply
i despise most animations. Its only something that "product people" want
reply
Again, the vast majority of people prefer animated UIs to non-animated ones. My own anecdotal experiences in building UIs and talking to end users over both short and long time frames supports this.
reply
deleted
reply