Week 8 Session: Movement

Turning duration and momentum into position and speed, with no second input axis

12 April 2027

Movement here isn’t a new capability — it’s an application of two you already have. Week 2’s hold-duration can map onto jump height; week 6’s momentum can map onto running speed. Week 7’s mode-switching decides which mapping is live when. The auto-run-plus-jump-height shape is the obvious version; the exercise asks you to justify your own choice of mapping instead of defaulting to it.

Before the session#

Bring your week 2 (hold) and week 6 (momentum) prototypes.

In the session#

Demo of the auto-run/jump-height shape as one worked example, then build time on your own spatial mapping.

Studio exercise#

Build a prototype where the single button controls both when something moves and how far or fast, using a continuous signal you’ve already built (hold-duration or momentum). Do not add a second input axis to make this easier — if you need one, the mapping is wrong, not the constraint.

By the end#

You can describe movement in this course as spatial mapping of an existing signal, not as a new input capability in its own right.