| ▲ | hypfer 2 hours ago | |||||||||||||||||||||||||
People often forget that animations serve purely a supportive role and do not exist for the purpose of having animations. They are there to mask loading times and ease from one state into the other. That's why we have them. This knowledge eventually got lost (figuratively speaking) and now we have code that needs to wait on the animation to finish. Another amazing example of cargo culting. | ||||||||||||||||||||||||||
| ▲ | alexdbird an hour ago | parent | next [-] | |||||||||||||||||||||||||
> to mask loading times and ease from one state into the other I'd expand on this: used well, they show the user than a state change is happening directly because of a particular action of theirs, and hint at how they might reverse or modify it. In fact I'd disagree with masking. If something appeared instantly with no hint as to why, that is a distinct anti-pattern on a touch screen. | ||||||||||||||||||||||||||
| ▲ | antihero an hour ago | parent | prev [-] | |||||||||||||||||||||||||
They aren’t purely for that, they also contribute to how an application feels to use in a creative manner. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||