An interface shows a system to one who does not yet know it. A shortcut withdraws it from one who knows it too well. The website exposes the procedure. Page. Menu. Form. Field. Validation. Error return. Confirmation. It gives action a visible surface, sometimes slow, sometimes redundant, but readable. The user sees the path because the system requires that he traverse it.
The bot reduces this path to a sentence. The macro reduces it to a recorded sequence. The Stream Deck reduces it to a key. The API reduces it to a call. The action does not disappear. It ceases to show its articulations.
The interface does not disappear. It withdraws into the command.
This withdrawal is only possible after stabilization. A short command supposes a world already carved up: known actions, expected parameters, assigned rights, anticipated errors, admissible outputs. The single button contains the former form. The macro contains the menu. The bot contains the tree structure. The shortcut contains the procedure it renders invisible.
The surface is useful as long as the gesture remains uncertain. It shows what can be done. It limits, names, orders, confirms. It gives the novice a map of the system. But repeated usage transforms the map into obstacle. What guided becomes friction. What explained slows down.
The advanced user no longer asks the system to present itself. He asks for an entry point.
The direct command is this reduction. It does not make the system simpler. It makes its complexity less apparent. A Telegram bot that replaces an administrative interface does not suppress permissions, states, validations, errors, databases. It concentrates them behind a conversation. A programmable key does not simplify the software. It buries a chain of operations in a gesture.
A macro is an interface that has ceased to explain itself.
This disappearance has a cost. When the surface disappears, the limits disappear with it. The user no longer sees neighboring options, alternative paths, intermediate states, possible refusals. He receives the action as if it were simple. It is not. It has simply become compact.
The graphical interface had a defect: it showed too much. The condensed command has the inverse defect: it no longer shows enough.
The efficient system therefore becomes double. For learning, it keeps a surface. For stabilized usage, it produces shortcuts. For automation, it withdraws almost everything. The same action can exist as page, as button, as command, as macro, as invisible call.
The difference is not only technical. It is ontological.
A system is not the same depending on whether it appears as space to traverse or as order to execute. In the first case, the user inhabits an interface. In the second, he triggers a procedure. The command replaces navigation.
The surface disappears when the system no longer needs to be understood to be activated.
Doctrine
The interface does not only make an action possible. It decides which part of the action must remain visible.
When usage stabilizes, the interface tends to contract. It leaves the surface and lodges itself in the shortcut, the macro, the bot, the call. Efficiency does not suppress mediation. It makes it less perceptible.
Open vector
Conversational agents promise the disappearance of the interface. They replace the menu with declared intention. But an interpreted intention remains an interface. It contains rights, assumptions, refusals, implicit parameters, invisible actions.
When the surface disappears, where do the limits of action hide?
