The iOS 8 animation curve

Apple sped up the animations before release, but for some they still felt too slow. Since iOS 8 didn't fundamentally change the animations curves, that perception has lingered. Recently, to highlight the difference between pre-iOS 7 and post-iOS 7 animations, Omni developer William Van Hecke made a video:

See more

Van Hecke attributes the difference to a change in interruptibility — Springboard previously allowing you to act before an animation finishes versus now making you wait until the animation finishes before you can act.

It's my understanding, however, that iOS animations have never been interruptible. They simply ended quickly pre-iOS 7 and now, post-iOS7, they ease out.

Whether shorting the animation tails or making the animations interruptible is the best way to reverse the feeling and the perception of slowness Hecke refers to, I don't know enough to say. Either way, and to his credit, Van Hecke filed the issue with Apple's bug reporter:

See more

More information on the animations from former UIKit engineer Andy Matuschak:

See more
Rene Ritchie

Rene Ritchie is one of the most respected Apple analysts in the business, reaching a combined audience of over 40 million readers a month. His YouTube channel, Vector, has over 90 thousand subscribers and 14 million views and his podcasts, including Debug, have been downloaded over 20 million times. He also regularly co-hosts MacBreak Weekly for the TWiT network and co-hosted CES Live! and Talk Mobile. Based in Montreal, Rene is a former director of product marketing, web developer, and graphic designer. He's authored several books and appeared on numerous television and radio segments to discuss Apple and the technology industry. When not working, he likes to cook, grapple, and spend time with his friends and family.

  • Really really........this guy is a little too anal .....nothing he said is that serious
  • This has definitely bothered me since running the betas of iOS 7. They tightened them up a little since, but I run in to the "lost input" issue almost every time I open my phone. I'm glad it's not being forgotten about, it's at the top of my iOS 9 wish list.
  • I repeatedly run into a situation where I close out of an app (hitting the home button). I then quickly swipe the screen to change to a different home screen page and my input is not registered (because the app close animation is not finished). Sent from the iMore App
  • I fear 1gb of RAM might not handle a lot of interruptibility very well...
  • This has bothered me particularly when going into/out of multitasking, but this was an interesting explanation of why. Thanks! Sent from the iMore App
  • Don't have this problem on my iPad Air when I used gestures to close an app and swipe pages, responds mid animation, it just causes the app icons to all disappear for a second. Sent from the iMore App
  • This annoyed me since the first iOS 7 dev preview. I sort of got used to it, first expecting it was a bug that would eventually be fixed and eventually just forgot about it, and the crappy experience it produced. So glad to see someone bring this up again and with clear video to illustrate the problem. Apple should fix this for iOS 9.
  • This will most likely be addressed when Apple introduces 2 gigabytes of RAM on the next iPhone. 1 gigabyte of RAM has always been limited no matter how well it runs on 1 gigabyte of RAM. Posted via the iMore App for Android
  • The iPad Air 2 has 2gb of RAM and still has these issues. I don;t think RAM has anything to do with this.
  • You guys keep mentioning RAM and this really shouldn't have to do with RAM. The animation doesn't need to be interrupted. It just needs to be cut off just like that example in iOS 3.
  • More RAM doesn't hurt anybody. Especially the still 1 gigabyte maximum that Apple has been using since 2012 with the iPhone 5 on the iPhones. Posted via the iMore App for Android
  • Agree. But it's not the reason for this blocking of the input by the animations. Sent from the iMore App
  • You're not there in testing to know whether more RAM would hurt the battery life among other things. Stop using the argument of more RAM when it comes to things like this. Sent from the iMore App
  • It would most certainly negatively affect the battery life. Sent from the iMore App
  • Yeah it's annoying as fuck to use iOS with animations working like this...
  • The same people who cares about this, will be the same ones who complains when the input lags and stutters like iOS 3. Face it you'll never be happy. Sent from the iMore App
  • I really don't think this is nitpicking. Just wanting the animations to accept input like they did pre iOS 7. By the way this has nothing to do with the amount of ram. If so, then iOS 3 on his original iPhone wouldn't exactly be a good counter example. Sent from the iMore App
  • *took "too" long - title I always felt, and still feel, that iOS7 animations are useless and have fallen way short of Rene's hyperboles of "radical rethinking of mainstream multitouch interface", of "enabling discovery though play", "rewarding intuition with delight" and "making computing fun". At the end of the day, its none of that. To me the overall "cleanliness" is still confusing at times, so much that I had to activate accessibility features to differentiate labels from buttons, and the animations have been tuned down for a while to try and remedy the iOS 8 landscape bug, and I have not missed them a bit. As for the faux-parallax, it was useless on Amazon's device and its just as useless on iOS.
  • Couldn't agree more! Very well said what I thought first time I installed iOS 7. And still hate it. waiting for every animation to finish every time... iOS 6,5,4 felt much faster, mostly because faster animation. No matter if you have iPhone 5S, iPhone 6, iOS feels so slow and it is very annoying. Reduce motion doesn't help. I wish they would consider change it. and I'm surprised, people are talking about it now, not long time ago. When you read that youtube video, lots of people have the same opinion.
  • Is this due to the animations or just loading time of apps? Meaning, the apps have gotten so much larger and more complex, storage so much larger (so much more to read through upon IO), that maybe while the animation is happening, the app is still actually loading up in the background and until it’s ready, you see the animation and image of the app. I say this because I often catch apps animation appear and once the app is responsive, it actually updates and looks different than what the animation showed. What we are seeing, I suspect, is the saved screenshot while the app is loading or “waking up” from it’s saved state. So again, I’m asking is this really a lack of responsiveness due to animations, or just loading lag covered up with an animation rather than just having a blank screen or the previous screen frozen for a moment?? The reason I ask, and why the difference matters is because if the lag was due to animation, then that could be fixed (just reduce or remove the animation). If it’s due to loading, then that’s another story entirely and the animation is a welcomed distraction.
  • I think the forced delay actually makes the user think before aimlessly swiping a screen that isn't even there yet. For most users, I don't see the tiny delay as an issue. Once every now and then it bothers me for 1/10th of a second but not enough to care. Sent from the iMore App
  • I just tweet to vzw support asking why my phone service is so slow. Can it be that it's my iPhone 6 plus? This thing is like as slow as my iPhone 2. What's going on?
  • You people are crazy! I like the animation, it looks good to me! Sent from the iMore App