An interactive garden that remembers each visit
Design a small artwork that accumulates participant actions over time, separating its persistent structure from its temporary response so the history remains meaningful and manageable.
An artwork can remember through accumulation
An interactive work can remember through accumulation. Each action adds a mark, a leaf, or a small change to a shared structure. The challenge is deciding what persists and what fades. Without that decision, an inviting first encounter can become an unreadable pile after repeated use.
Store each contribution with stable attributes
Start with a single action that adds one visible element. Store the new element's position and a few stable attributes. Draw the stored collection each frame rather than regenerating it randomly. Define a clear limit, a reset method, and the intended lifespan of the accumulated state.
Write down the current setting for maximum stored contributions before making a second interpretation of the idea. Keep the ordinary state beside the most extreme intended state. The useful boundary is where the relationship remains understandable, rather than where the tool stops allowing a larger value. Check both ends before filling the middle. A useful acceptance check is whether the accumulated history stays readable as new actions arrive. Judge that at the intended viewing size or working distance, where tiny construction mistakes and exaggerated effects can have very different consequences.
Find redraws that regenerate the history
If the garden changes unexpectedly on every redraw, inspect whether attributes are being chosen again instead of stored. If it becomes crowded, revise the growth rule or make older contributions quieter. More space alone may only postpone the same problem.
To locate a fault, inspect the part of the result most directly affected by maximum stored contributions. Try an ordinary action, an incomplete action, and two actions in quick succession. Watch whether the piece acknowledges each input and returns to a usable state afterward.
Simulate five, twenty, and a hundred actions
Simulate five, twenty, and a hundred actions without waiting for actual visitors. Compare how the piece changes at each stage. Decide which features should remain legible and whether a mature state needs a different growth behavior.
Arrange a small experiment with a small cluster, a full patch, and a deliberately crowded field, keeping its other decisions consistent. Predict one consequence before each trial, then compare that prediction with the actual result. Record a surprise in plain language and identify the part of the construction that could explain it. This turns a set of variations into information you can use in a later, more ambitious piece.
Separate durable marks from temporary feedback
Store lily leaves and ripples in different collections. A leaf persists for the planned session; a ripple has an age and disappears after a short interval. Clear both deliberately when resetting, or preserve leaves if that is the stated behavior. If storage lasts only while the page remains open, describe that limit accurately. A work can remember within one session without pretending to retain a permanent history across reloads.
A pond with persistent lily leaves
Make a small digital pond where each click adds a lily leaf near an existing one. Limit the addition to open areas and let a brief ripple acknowledge the action. The ripple disappears while the leaf remains, distinguishing the immediate response from the growing history.
References & further reading
Examples and exercises in this guide are original teaching scenarios.
