Lab
A working experiment in treating motion as a system of reusable behaviours instead of a sequence rebuilt from scratch.
/
- Status
- Working Experiment
- Area
- Design Systems, Generative Motion
- Built by
- AMOK Lab
- Current outputs
- GIF / PNG Sequence
What if motion identity behaved more like a system?
Motion work is often recreated one animation at a time. A logo reveal. A piece of kinetic type. A grid animation. Another variation for another format. The output changes, but much of the underlying behaviour repeats. Motion Engine explores a different approach: define those behaviours once, then compose, adjust and reuse them across different content. The experiment asks whether motion can become systematic without becoming predictable.
Behaviours instead of templates.
Motion Engine is built around composable behaviours. Content enters the system as typography or vector material. Behaviours define how it moves. Parameters control the variation. The result is rendered live and can be exported for use elsewhere.
Enough control to repeat. Enough variation to move.
A motion identity has the same tension as any other identity system. If every output is completely different, recognition disappears. If every output is locked into a template, the system becomes repetitive. Motion Engine explores the space between those extremes.
The material stays editable.
The engine works with real typography and vector information rather than treating every composition as a finished video asset. Glyph-aware typography allows motion to act on letters more precisely. SVG support allows uploaded vector material to participate in behaviours such as drawing, reveals and logo motion. That means the system can operate closer to the ingredients of an identity instead of only manipulating flattened outputs.
A tool has to leave the experiment.
The current engine can export: - GIF - PNG sequence That is enough for the experiment to produce assets that can move into websites, social content, presentations and other editing workflows. The export layer is intentionally still limited.
The remaining question is not whether it works.
Motion Engine exists and functions. The more interesting uncertainty is what it should become. Is the strongest value: faster creation of motion assets; a way to encode motion identity; controlled tools for non-motion designers; motion governance for brand teams; a creative instrument for designers; simply a useful internal AMOK tool? Those questions are still open. That is why this remains a Working Experiment, not a released product. Internally, the next validation step is to show it to relevant designers and teams, identify the strongest user job, and only then decide whether it deserves packaging for wider use.
Built enough to learn from. Open enough to change.
Motion Engine already gives AMOK a reusable way to explore kinetic identity. Whether it remains an internal tool or develops into something others can use is deliberately unresolved. That is the point of the Lab.