3 ms·
I think animations, as most program them, slow down the UI exactly as you say. But when their timing is tight, and the whole thing happens in under, say, half
by tomc1985 9y ago
I think animations, as most program them, slow down the UI exactly as you say.
But when their timing is tight, and the whole thing happens in under, say, half a second, you get the benefits of that context association and it still feels really cool and high-tech. People jsut set their animations too slow. (Seriously, nothing should ever take longer than 500ms)
- white-flame 9y agoI don't have a link, but in referencing interactivity tests for some remote software development I did some years back, the maximum time between pressing a button and perceiving its effect to be considered "instant" is around 200ms. You don't want to go slower than that if you want it to "feel" fast & responsive.
- tomc1985 9y agoEven better. Does that give the animation enough time to show though? At that speed I'd guess you might as well make something instant
- Filligree 9y agoAt 60 frames per second? Sure, that's enough for 12 frames.
- bostik 9y agoYou're talking about Nielsen thresholds, and the limit for "instantaneous" is actually ~100ms.[0] Anything slower is considered to have taken some time. Now, if that wasn't depressing enough - the Nielsen research is from early 90's. In the intervening 25 years, the users have certainly not become any less impatient. 0: https://www.nngroup.com/articles/response-times-3-important-limits/ https://www.nngroup.com/articles/response-times-3-important-...
- yason 9y agoPeople jsut set their animations too slow. (Seriously, nothing should ever take longer than 500ms) They could start with 500ms and subtract 100ms from each UI activity after each time it is used until the delay is 0ms. The user would learn the interactions on the screen first and then not be bothered by the animations later. As a bonus the user might actually thing the program "speeded up after a 'break-in' period".
- zeveb 9y agoNow that's an awesome idea! It'd be fine to actually just store that setting in memory, and reset with every restart: I wouldn't mind a half-second delay on my first window zoom after restart if I knew that it'd drop down to zero four zooms later.