Candidate Pattern / 3 REAL CASES
Shared Object
Many visitors change or explore the same persistent artifact.
On this page
01 / DEFINITION
The mechanism
Many visitors change or explore the same persistent artifact.
02 / ASSUMPTION
The default
Each visitor gets a private copy of the experience.
03 / THE TURN
The shift
One shared state holds the traces left by multiple people.
04 / REAL EXAMPLES
Cases behind it
One Million Checkboxes
One million simple controls became a shared global canvas.
diiverge.co
A single picture branches into a persistent world that visitors shape.
Internet Makes Music
Strangers place sound-making pixels on one shared public canvas.
05 / VARIATION
Different implementations
Checkboxes share a live state; diiverge keeps branches created from a seeded image; Internet Makes Music shares a sound grid.
06 / EXPLANATION
Why it can work
A later visitor can see consequences of earlier actions, which gives simple interactions social meaning.
07 / BOUNDARY
Where it fails
Shared state also invites vandalism, moderation work, or uncontrolled generation costs.
08 / BUSINESS
Commercial implications
A shared experience alone is not a revenue model.
09 / BUILD
Technical implications
Persistence, concurrent edits, abuse controls, and cost caps matter more than visual polish.
10 / TAKE THE QUESTIONS
Questions to borrow
- What becomes different for visitor two because visitor one came first?
- How will the shared object handle unwanted contributions?
11 / TRACE IT BACK