A common challenge when designing digital products, specially when creating design deliverables, is having to explain an app flow, a transition between two screens, or even a change between two or more states in the same screen.

A designer’s skill to imagine these transitions is almost as valuable as the skill required to explain them, to create a visual representation that will help maintain one same vision for the product among different teams (Design, PMs, Development, etc).

Static deliverables, like wireframes, comps, app flows in PDFs, etc. help to communicate the visual side of the product. But motion, behaviors and interactions shouldn’t be left open to interpretation. And just sending an MP4 file to the dev team doesn’t really help as you’d expect.

It’s common to see design deliverables with flows that show, let’s say, a screen with “state A” and then a slightly different “state B”. But designers need to plan for more than just A and B, as there’s a bigger need to envision, deliver and communicate the expected transition of going from A to B and back again.