Week 2 Session: Hold
Duration becomes information — what a button can tell you before you let go of it
Last week’s press was instant — it happened, and it was over. This week adds duration: a continuous value, measured from the moment of press to right now, that exists before release. Nothing is decided yet by letting go; that’s next week. This week is only about isolating the signal.
Before the session#
Bring one of your week 1 prototypes. You’ll be adding to it, not starting over.
In the session#
Short demo of hold-duration as a readout (a bar filling, a number climbing, a pitch rising), then build time extending your own prototype.
Studio exercise#
Take a week 1 prototype and add a visible readout driven purely by how long the button has been held. No release logic — the outcome doesn’t change when you let go, only the readout while you’re still holding.
By the end#
Hold-duration now reads as a continuous channel layered on top of last week’s discrete event — not a new kind of input, just a new way of reading the old one.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- one of your week 1 prototypes now shows a value that changes for as long as the button is held down
- you can say, in one sentence, what that growing value represents
Teaching team
- Idris Fenn — tutor