Design

Pivotal journey: Communicate a motion idea to an engineer

Assumptions

The motion designer has heard of Material Motion and would like to make use of it.

End-goal

A designer’s idea is realized in production code.

Ideal journey (does not exist yet)

1. Designer visits <material motion website>.
2. Designer visits <motion design/language page>.
3. Designer reads a one-pager on how to use a tool to describe motion using the Material Motion language.
4. Designer sends a link from the tool to the engineer.
5. Engineer exports the tool specification as code.
6. Engineer embeds the code in their application.
7. Engineer makes adjustments to the code as necessary.