Motion
Pivotal journey: Concept to production
Assumptions
Two groups are primarily involved: motion designers and motion engineers. Both are aware of Material Motion.
End-goal
Productionize a motion concept.
“V1” ideal journey
- Motion designer conceives of a motion concept to satisfy product need.
- Motion designer creators mocks/prototypes to illustrate the concept.
- Motion designer gets design and engineering feedback and iterates.
- Motion designer describes their concept using the Material Motion language.
- The engineer creates a new director and applies the language described by the designer.
- The engineer wires the necessary aspects of the greater app architecture to the director.
- The engineer and motion designer iterate on the implementation.
- The implementation reaches a satisfactory point and is shipped.
“V2” ideal journey
Goal is to enable more collaboration between motion design and engineering.
- A motion designer conceives of a motion concept.
- A person uses Material Motion languages to prototype the concept either within the context of an existing app or in a playground.
- The person gets design and engineering feedback and iterates.
- The implementation reaches a satisfactory point and is shipped.
“V3” ideal journey
Goal is to completely remove the design/engineering hand-off.
- A person conceives of a motion concept and creates a director in a tool.
- The person uses Material Motion languages to prototype the concept either within the context of an existing app or in a playground.
- The person gets design and engineering feedback and iterates.
- The implementation reaches a satisfactory point and is shipped.
