The Disappearing Interface
When agents handle the long tail of features, a product can gain capabilities without making its human interface harder to use.
Emlyn O'Regan
A familiar problem in interface design is that successful applications tend to become harder to use. Each new capability needs a button, menu item, dialog, settings panel or workflow. Eventually the interface becomes a record of everything the product has learned to do.
Agents offer a way out. Capability and human interface complexity no longer have to grow together.
Leave the long tail to agents
Consider settings pages. Most options matter only occasionally; many are touched once, or never. They are meaningful system operations, but they need not all be permanent human controls. “Turn on dark mode for me” can be a request to an agent invoking a machine interface.
The human-facing application can concentrate on what benefits from direct interaction: viewing, exploring, selecting, manipulating and judging. A volume slider, waveform, map or visual editor can be better than conversation, especially when feedback needs to be immediate.
This is not the abolition of interfaces. It is an argument for giving humans the interfaces they actually benefit from, rather than graphical access to every capability.
The different 10% problem
A product can have hundreds of features even when each person uses only a small subset. The complication is that different people use different subsets. Removing the “unused” features for one person removes essential features for someone else.
An agent could make those less common features available on demand, without demanding permanent space in everyone's interface. Eventually it might even compose the relevant capabilities from separate suppliers, rather than relying on one large application.
From simplified to generated interfaces
There is a further possibility. Once interfaces are separated into small, comprehensible pieces, why must every piece be designed and shipped in advance? An agent might generate a temporary control or panel, keep it while useful, then replace or discard it.
A person could ask for a small audio-export panel with their preferred presets. The agent might construct it from existing operations, rather than send the person through a large settings dialog.
Some structures should remain stable: familiar navigation, accessibility, predictable behaviour and safety-critical controls are valuable. But an interface can have a stable centre and a fluid edge.
This points to a different principle for product design: expose what people want to manipulate; make the rest available as capabilities.
Further reading: The UI complexity trap · The different 10% problem · Software slivers.