3 ms·
Agree with the problem, disagree with the solution. Cut the animation times in half, and you're wasting only half the time. It will be too fast for some people
by shurcooL 13y ago
Agree with the problem, disagree with the solution.
Cut the animation times in half, and you're wasting only half the time. It will be too fast for some people, too slow for others.
Instead, avoid _blocking_ animations. Some animations are great as long as they don't prevent you from doing the next action.
Don't treat the user like an idiot. If they tap again before animation finishes, skip to end of animation and perform the action for that tap.
With iOS 6 folders, for example, I often tap a second time just a moment before the animation finishes, and my tap is ignored. It gets very frustrating when you're trying to be fast. Imagine a keyboard that would block your keypresses if you exceed 60 WPM.
- gdubs 13y agoThe thing to remember is that a lot of times the animation is masking the actual load time of an app. The app is often represented as a screenshot until it completely unarchives itself into memory. You reminded me of a feature I've been dying for though, semi-related: the ability to control tap-speed, similar to double-click speed on the desktop. I'd love to be able bring up the text selection menu more quickly. Edit: To your main point about caching taps -- I feel like while in some case that would be straightforward to implement, it could get pretty hairy for most average users.
- nwh 13y agoOn an iPhone 5 the lag of an application being resumed is almost non-existent. Under iOS7 I too am constantly having to re-touch just because I hit the end of the animation rather than the app.