0

Users like apps to be fast. Many apps use animations to "smooth" the experience. If an animations are too slow, the app feels...well, slow. But if the animations are too fast, they may be so fast that they make the app feel "choppy" or appear as if there is no animation at all. So how fast is too fast for animations? How fast can an animation or transition be without looking too choppy or instantaneous?

closed as too broad by DA01, Mayo, Bevan, Devin, jazZRo Sep 27 '16 at 6:12

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 3
    Depends on what you are animating, the context it's being used in, the UI, etc. Too many variables here to give you a simple answer. – DA01 Sep 26 '16 at 23:49
  • 1
    should be fast enough to not stop the user from interacting with your application. – Max Sep 27 '16 at 2:17
  • 1
    Like DA01 said, it depends on the animation, and the context of its' use. This Material Design documentation of motion may prove useful: Material Design - Motion – Tory Sep 27 '16 at 2:28
1

Although mostly you eyeball this, 300ms - 500ms for each animation is nice for standard buttons animations, menu and anything toggled. I will increase the duration if users are not expected to toggle the element frequently, mostly landing at 1s. Timing functions are also something you want to look at as they can make animations look slower or faster.

Not the answer you're looking for? Browse other questions tagged or ask your own question.