One description, four renderers. That is the whole argument in a picture.Every assistant draws its own way, and the bill lands on the people who already maintain your button component. This is a call to arms to fix this.Connecting was the easy part and the plumbing is close to settled for MCP Servers, which followed the lead of HTTP dressed up for the AI era.What isn’t is what each client does when your agent needs a date picker on screen: which components exist, who owns the rendering, what it looks like when it shows up on a screen.There are four ways a client can do it, and every product you care about sits in one of them. Nobody publishes that comparison, so sorting out which client does which took four specifications, a protocol proposal and a Google engineering post, and none of them agree on what to call any of it.Google’s trying to create that standard — A2UI. It’s short for...