Components → Conversations

Design systems are organized around UI primitives. A button, a card, a dialog, a table. You compose them into screens, and the screens are what users see.

AI interfaces aren’t organized around screens. They’re organized around turns.

The Shift

The user says something. The system processes it — visibly, because invisible processing feels like a hang. The system responds, maybe in a stream, maybe all at once. The user confirms, rejects, or refines. That cycle — input, processing, response, confirmation — is the fundamental unit, not the button.

No major design system ships conversation choreography as a first-class primitive. Every team building a chat interface, a copilot sidebar, or an AI assistant invents this layer from scratch: how does “thinking” look? What happens when a stream is interrupted? How do suggested actions appear alongside generated text? How does the UI handle a response that’s three words versus three paragraphs? These are component-level decisions being made ad hoc by hundreds of product teams who would rather not reinvent them. The design system could own this. None of them do yet.

And conversations won’t stay in chat boxes forever. We’re already seeing interfaces that surface recent activity, anticipated actions, and contextual information without requiring a prompt — dashboards that rearrange around what the AI thinks you need, cards that appear because the system noticed something relevant, summaries that write themselves before you ask. The turn-based conversation is the first pattern. The ambient, anticipatory interface is the next one. Design systems need to handle both — the explicit back-and-forth and the proactive surface that shows you what matters before you ask for it.

Where Systems Stand Today

Fluent UI has Spinner, Toast, and MessageBar — discrete feedback components with no conversation model. Material Design 3 Expressive ships five new components built for conversational flows (Button Groups, FAB Menu, Loading Indicator, Split Button, Toolbars), but only on Jetpack Compose. On the web — where most AI interfaces actually live — neither system has streaming content components, typing indicators, or progressive block rendering. See the Fluent UI and Material Design system pages for the full analysis.

What Pushes a Score Up

If your system has a Spinner and a Toast, you’re at a 2. If it has compositional primitives for the input → processing → response → confirmation cycle — streaming content components, typing indicators, progressive block rendering — you’re at a 5+. A 7 means conversation choreography is a first-class design concern, not something each product team invents.