The End of the Static Screen: Architecting Intent-Driven UX — Gus Iwanaga, commercetools

A generated interface can adapt to each request while the product team still controls what appears on screen. In this commercetools talk, the team's first attempt gave a model a catalog of interface components and asked it to compose the experience. Asked four times for a Q1 sales report, it returned four different layouts, with different KPI cards, charts and amounts of text, and wording that drifted between runs. The speaker would not ship that.

The design they chose keeps the model out of layout composition. An orchestrator classifies the user's intent, calls tools and maps the results onto eligible components. A structured UI specification then renders as native components against a schema, so the output follows the design system. The talk places this between shipping one fixed component and letting a model emit arbitrary markup. It also names two open problems: something must still arrange the chosen components, which the team approached by teaching atomic design principles, and the component catalog becomes the contract between agent and interface, so every property in it matters. This rests on the talk's published description, not a transcript, and reports no usability results.