Topic

Server-Driven UI

1 post about Server-Driven UI. Every summary links to the original.

See the idea

Server-Driven UI explainers

Loading AG-UI as the Agent–UI Contract Layer image
Architecture A2UI AG-UI AI Agents Human-in-the-Loop Server-Driven UI Streaming
AG-UI as the Agent–UI Contract Layer
AG-UI is a typed event contract between an agent backend and a frontend, turning streamed agent state into UI. This diagram maps the layers and shows where human review plugs in.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Yelp
The making of the Yelp Assistant UI
Yelp Assistant is the first large-scale consumer LLM product at Yelp, connecting users with local professionals via chat. To iterate quickly across iOS, Android, and web while avoiding long app-store update cycles, the team chose a hybrid architecture: the top bar and input bar are native, while the chat content area is server-driven using Yelp’s CHAOS framework. The view and data are separated — the client fetches a CHAOS view template once, then conversation data hydrates that template on each turn. The backend sends MessageEvent objects, quick replies, and client actions (such as DisableChat) to control the UI. This hybrid approach enabled rapid iteration, but required building new CHAOS components for text input and network requests, and posed cross-platform consistency challenges.

The best engineering reads, once a week.

Topic

1 post about Server-Driven UI. Every summary links to the original.

See the idea

Loading AG-UI as the Agent–UI Contract Layer image
Architecture A2UI AG-UI AI Agents Human-in-the-Loop Server-Driven UI Streaming
AG-UI as the Agent–UI Contract Layer
AG-UI is a typed event contract between an agent backend and a frontend, turning streamed agent state into UI. This diagram maps the layers and shows where human review plugs in.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Yelp
The making of the Yelp Assistant UI
Yelp Assistant is the first large-scale consumer LLM product at Yelp, connecting users with local professionals via chat. To iterate quickly across iOS, Android, and web while avoiding long app-store update cycles, the team chose a hybrid architecture: the top bar and input bar are native, while the chat content area is server-driven using Yelp’s CHAOS framework. The view and data are separated — the client fetches a CHAOS view template once, then conversation data hydrates that template on each turn. The backend sends MessageEvent objects, quick replies, and client actions (such as DisableChat) to control the UI. This hybrid approach enabled rapid iteration, but required building new CHAOS components for text input and network requests, and posed cross-platform consistency challenges.

The best engineering reads, once a week.