pop

I've done a bit of work on React Native animations. We are mostly working on two experimental animation APIs. One is implemented fully in JS and is used when we need to implement gestures and respond to ongoing touch interactions. This is tricky because we need to be very careful to keep our JS frames very short and fast during the gesture, avoiding expensive allocations and making sure we don't try to process too much data in Relay. The other API is much more magical. You configure the animation for your component immediately before a setState. The new layout is computed normally, but instead of directly updating the native views, we use POP[1] to animate to them on the main thread. This is a really easy-to-use API, but there are a few caveats. We're still developing, stabilizing, and cleaning up these tools. It's great to hear your inte

The curves used in iOS are all pretty standard, they're easily to replicate if you want. It's pretty easily to replicate iOS functionality in iOS itself just because it's a better environment, it's not the 'secret' numbers. But if taking the example of Paper, it's built on top of Pop which is absolutely open source and handles all the animations: https://github.com/facebook/pop. So in theory you should be able to replicate all this stuff on the web, but you can't because it's just not build with highly responsive UI in as the focus.

Compare this to 'Paper', Facebook's other iOS app which has 4 stars: https://www.facebook.com/paper https://itunes.apple.com/us/app/paper-stories-from-facebook/... Not only is it a great app, but it's also given back to the iOS community in the form of several great open source projects: https://facebook.github.io/origami/ https://github.com/facebook/pop http://asyncdisplaykit.org I find it fascinating that Facebook has two independent iOS efforts, and that while one is clearly better than the other, they seem content to pursue both apps. (Notably, Paper is still not available outside the US–I use Papers personally and can't imagine going back to the default app which just feels a bit lifeless in comparison, crashes/bugginess aside.)

I agree, and it does seem like these ideas are catching on. The frameworks you mention, and also a big push by Facebook on iOS in the past year are notable examples. The FB "pop" framework was just made public (I think) this week: https://github.com/facebook/pop Also their quartz composer prototyping framework: http://facebook.github.io/origami/ Awesome collection at your tumblr!