Origins
Early interfaces were instruments before they were screens: panels of switches and dials where every control mapped to one machine state.1 The operator held the model in their head.
The shift toward metaphor began when displays became cheap enough to show a representation of state rather than the state itself.
The metaphor era
The desktop metaphor made the computer legible to non-specialists by borrowing objects people already understood — documents, folders, a trash can.2
Metaphor traded fidelity for familiarity. It is widely held that the desktop metaphor was the decisive factor in personal-computer adoption — a claim worth examining, since timing and price fell at once.3
Direct manipulation
Direct manipulation replaced commands with continuous, reversible action on visible objects: drag, drop, resize, undo.4
Its cost is that everything must be on screen to be actuated. As systems grew, the operator's mental model returned — now as navigation rather than memorized commands.
Relational interfaces
A document is a tree, but meaning is a graph: a citation relates to a source, a claim to its evidence, a control to the thing it changes. Interfaces have mostly represented those relations passively, as links to click.
A relational interface treats them as live structure — visible, weighted, inspectable — without abandoning direct manipulation or semantic HTML.
Evidence
Claims are bodies; sources bind to them. A claim with a contradiction reads as contested; one with only support reads as supported. Hover a claim to thread it to its sources.
The desktop metaphor caused personal-computer adoption. contested
Direct manipulation reduces error rates for visible tasks. supported
Sources
- Licklider, “Man-Computer Symbiosis” (1960)
- Smith et al., “Designing the Star User Interface” (1982)
- Norman, “The Design of Everyday Things” (1988)
- Shneiderman, “Direct Manipulation” (1983)