In most apps, transitions like these tend to be painfully slow. A 300-millisecond transition animation blocks the user just like a blocking system call stops a running process; it forces them to do nothing but stare at your animation, because they can't read or target any UI elements until they've stopped moving.<p>You wouldn't randomly put "usleep(300000)" in your programs, so why punish your users by blocking them in the same way?<p>Yes, I understand that it's pretty. But often, I think, as designers we can be so enthralled by the beauty of our creations that we appreciate them as art and forget the perspective of a user who is simply trying to find the answer to a question or get something done.<p>In the vast majority of situations, no transition is necessary. As a user, I don't want to wait 300 ms to do the next thing. Don't make me wait. If I must wait, keep the delay under 100 ms so that the system feels responsive.<p>This is Webflow, a website building tool, so its design choices have a bigger impact; they affect the design of many websites. I would argue against making it trivially easy for website designers to force their users to wait. If the user really does want a transition, use a shorter default duration, like 100 ms.