I'd like to know the preferences of mobile developers when receiving animations mocked up in one of the various prototyping tools (i.e. Flinto, Principle, Pixate).<p>I'm mostly concerned with native because tools like Framer allow you to re-use code in web applications.<p>How do you arrive at the final values for timings, durations, springs, easing curves etc?<p>I've seen many different forms of animation handoff:
- Video file - dev required to guess at what's going on in the animation
- Gif - same as above
- Dev gets hands-on with the prototype - uses a mirror/viewer app to interact with the prototype but still needs to guess at what’s going on
- Spec sheets - a list of all the values for timings, durations, springs and easing curves, but difficult to use in context, difficult to put together and difficult to read.<p>Any others? I want to build a better way!