5 ms·

Someone please explain to me, why we have all these animations nowaways other than 'because we can' - what purpose do they actually have?

mrob 8y ago
Tricking the managers into thinking that the designers are actually contributing value.
red_admiral 8y ago
I think one of the original ideas was to "show where something had gone" - when you minimised a window, both on Win XP (if I remember right) and OS X, it wouldn't just "disappear" but would animate down to the taskbar / launch bar. That way you get fewer people confused about where their window went. I suppose you could just about make a case that when you have a modal element like a form to edit an item, if it takes up most or all of a small screen then having an animation to expand it makes a visual difference between "you're now on a new page" and "this form has popped up, but when you close it you'll be back on the page you were before - it hasn't gone away".
molf 8y ago
It can make it clear what happened after user interaction. Was an article added to the list during a refresh? Did the correct item actually go away after deleting it? It's easy to miss updates without animations. Even if you don't miss the update an animation will provide an additional confirmation that the correct thing happened. On touch devices there's also the fact that animations mimic input gestures. Imagine swipe-to-delete without the item actually moving, that would be super awkward to use... Of course, like anything, it is possible to mis-/overuse.
hawski 8y ago
They may be useful for beginners. Otherwise mundane app will look much more sophisticated. It can also make the experience more fun, which makes it easier to addict the user. Just think why slot machines are so colorful and flashy. Would they have same appeal if they would look and behave like a parking meter? I would not mind animations if: - they would not slow me down - I'm faster than them and I have to wait. It would be interesting if animations would be faster or disabled when user interacts faster than some threshold. - they would be interruptible - they would not cause performance degradation - they would not add more bugs. As with most asynchronous actions they are not properly tested when things happen simultaneously or are interrupted.
- CM30 8y ago
  An automatic option to disable animations if the user is faster certainly seems like an interesting one. Though it may be interesting just to let users choose whether they want to see animations in general. That'd solve a lot of problems here, and additionally give you some metrics in regards to how many people like the things.
  - JoshMnem 8y ago
    > Though it may be interesting just to let users choose whether they want to see animations in general. That would be the ideal solution. Make a setting in browsers and devices where users could turn off all animations. Designers could test their UIs with the setting on and off. Everyone would be happy.
fit2rule 8y ago
I agree with your sentiment - there really isn't a use for animations in the context of most UI. Except when there is - for example, first-user introduction/onboarding segue's, which guide the users attention around the app by highlights/flows, perhaps overlaid in a fashion that makes it clear that the overlay itself is impermanent (by fading it) .. but only if its got a real purpose, as you state. I appreciate this degree of assistance in learning a new app personally, especially on mobile. Animating the UI is what we want the user to do anyway - and many users are very animated about how they use their apps (i.e. selfie culture), so using animation to train the user to use the app properly, such that the user animates back, seems obvious.
JoshMnem 8y ago
Probably because playing with CSS3 is fun and most people have little aesthetic restraint or awareness of accessibility for visual motion sensitivity.

mrob 8y ago

Tricking the managers into thinking that the designers are actually contributing value.

red_admiral 8y ago

I think one of the original ideas was to "show where something had gone" - when you minimised a window, both on Win XP (if I remember right) and OS X, it wouldn't just "disappear" but would animate down to the taskbar / launch bar. That way you get fewer people confused about where their window went. I suppose you could just about make a case that when you have a modal element like a form to edit an item, if it takes up most or all of a small screen then having an animation to expand it makes a visual difference between "you're now on a new page" and "this form has popped up, but when you close it you'll be back on the page you were before - it hasn't gone away".

molf 8y ago

It can make it clear what happened after user interaction. Was an article added to the list during a refresh? Did the correct item actually go away after deleting it? It's easy to miss updates without animations. Even if you don't miss the update an animation will provide an additional confirmation that the correct thing happened. On touch devices there's also the fact that animations mimic input gestures. Imagine swipe-to-delete without the item actually moving, that would be super awkward to use... Of course, like anything, it is possible to mis-/overuse.

hawski 8y ago

They may be useful for beginners. Otherwise mundane app will look much more sophisticated. It can also make the experience more fun, which makes it easier to addict the user. Just think why slot machines are so colorful and flashy. Would they have same appeal if they would look and behave like a parking meter? I would not mind animations if: - they would not slow me down - I'm faster than them and I have to wait. It would be interesting if animations would be faster or disabled when user interacts faster than some threshold. - they would be interruptible - they would not cause performance degradation - they would not add more bugs. As with most asynchronous actions they are not properly tested when things happen simultaneously or are interrupted.

CM30 8y ago
An automatic option to disable animations if the user is faster certainly seems like an interesting one. Though it may be interesting just to let users choose whether they want to see animations in general. That'd solve a lot of problems here, and additionally give you some metrics in regards to how many people like the things.
- JoshMnem 8y ago
  > Though it may be interesting just to let users choose whether they want to see animations in general. That would be the ideal solution. Make a setting in browsers and devices where users could turn off all animations. Designers could test their UIs with the setting on and off. Everyone would be happy.

fit2rule 8y ago

I agree with your sentiment - there really isn't a use for animations in the context of most UI. Except when there is - for example, first-user introduction/onboarding segue's, which guide the users attention around the app by highlights/flows, perhaps overlaid in a fashion that makes it clear that the overlay itself is impermanent (by fading it) .. but only if its got a real purpose, as you state. I appreciate this degree of assistance in learning a new app personally, especially on mobile. Animating the UI is what we want the user to do anyway - and many users are very animated about how they use their apps (i.e. selfie culture), so using animation to train the user to use the app properly, such that the user animates back, seems obvious.

JoshMnem 8y ago

Probably because playing with CSS3 is fun and most people have little aesthetic restraint or awareness of accessibility for visual motion sensitivity.