{"path":"/beyond-the-application/the-disappearing-interface/dynamically-generated-interfaces","content":{"title":"From Static to Generated Interfaces","summary":"Small, composable UI pieces may increasingly be generated, adapted and discarded by agents as needs change.","body":"We generally treat a human interface as something designed in advance and shipped with a product. Even configurable interfaces are usually arrangements of controls the developer already anticipated.\n\nOnce software capabilities are separately accessible to agents, another possibility emerges: **the human interface becomes a composition too**.\n\nSuppose someone repeatedly exports audio into three particular formats. Instead of navigating a comprehensive export dialog, they ask their agent for a tiny panel containing those three actions. The agent constructs the controls, connects them to the underlying operations and keeps the panel available. Later it can revise or discard it.\n\nThe interface is generated for a particular purpose, not permanently added to the product for everybody.\n\n## Why decomposition matters\n\nSmall interface pieces are easier to specify, generate, test, replace and discard than an entire application interface. A single control or task panel has limited state and a small behavioural contract. It can be recreated when a dependency changes.\n\nThis suggests a gradual move from **static, vendor-designed screens** to mixtures of stable interface foundations and dynamic, agent-generated components.\n\nThe agent might also construct a new capability behind the control, rather than only expose an existing one. That connects generated interfaces with [de novo capability construction](/beyond-the-application/the-disaggregation-of-software/de-novo-capability-construction).\n\n## Fluid does not mean arbitrary\n\nUsers benefit from muscle memory, consistency and the ability to understand what software will do. Generated components therefore need constraints: accessibility, clear permissions, reliable binding to operations, safe defaults and stable behaviour where stability matters.\n\nA useful division may be a durable visual workspace surrounded by more disposable controls for specialised tasks.\n\nThe result is not necessarily a screen that changes every time someone looks at it. It's an interface that **can evolve when needs change**, without waiting for a product release.\n\nRelated: [The Disappearing Interface](/beyond-the-application/the-disappearing-interface) · [Hybrid Human–Agent Software](/beyond-the-application/three-models-of-software/hybrid-human-agent-software) · [The Disaggregation of Software](/beyond-the-application/the-disaggregation-of-software)."}}