How developers are taking the guesswork out of animation coding

user_artoceania

• April 16, 2020
• 3 min read
• Design

A critical point in any product team’s workflow is when design starts handing over work to developers to bring to life. Handing off design specs that translate easily to code is tricky, and adding animation interactions to that gets even trickier. 

There are lots of solutions that help deliver baseline information developers need to build final products—like assets, type specs, color values—but getting specifications to build animations is rarely done through any set process. 

Here at InV, we’ve built a pretty cool connection to hand off important build information to developers, including motion specs. 

Motion handoff for most of us: 

The only way for developers to translate animations into testable experiences is through a lot of replaying, followed by educated guessing and rounds back and forth with designers.

(Check out Inv Cloud to learn more about animation handoff.)

It ends up looking something like this: 

1. Designers finalize prototypes for the development team, which includes screen transitions and animations. 
2. Developers pull whatever information they can get and watch replays of interactions as many times as possible.
3. Developers build transition movements in a test environment through guesswork.
4. Designers review the work and send it back to development because the animation is off.
5. Developers and designers meet to review animations again in detail and start the process over from step one.

(Read about General Assembly’s designer-developer collaboration process here.)

While this process feels like business as usual for many teams, there is a better way. Here’s how teams are solving this problem with Inv. 

Motion handoff from Studio to Inspect

Design teams building their prototypes with InV Studio are able to hand off their files with inspectable animation information for developers. Here’s how we do it: 

1. In Studio, designers can prototype and dictate advanced animations with Motion and Timeline. 
2. When the prototype is ready to go, designers click the Inv publishing icon, name the prototype, and click “Publish” to send files to Inv Cloud for collaboration. 
3. From your Inv Cloud account, developers can now view the new prototype in Inspect mode to get assets, measures, type information, color values, and any motion specifications. 
4. A lightning bolt icon in the layers panel of your prototype indicates there are inspectable motions in the prototype.
5. Developers can click into any layer with a lightning bolt to preview animations and inspect the interaction for the Bezier curve, Start Value, End Value, and CSS information.