← All IntelClip / Developer ToolsThe generative UI spectrum and A2UI interoperability
From MCP Apps: Extending the Frontier — Ido Salomon & Liad Yosef · ≈15:35
Places predefined iframe UI, declarative UI (JSON render, A2UI) and fully generative UI on one spectrum, with a published guide for shipping the same server to Gemini and ChatGPT.
What’s in it
- Places predefined iframe UI, declarative UI (JSON render, A2UI) and fully generative UI on one spectrum, with a published guide for shipping the same server to Gemini and ChatGPT.
Clip transcript
soon. And we're working on this generative UI spectrum where you have predefined UI. That's MCP apps. That's like the black box iframe that renders all trace UI in that example. But you also have other things on this spectrum like declarative UI like JSON render or A2UI. These specs that say yeah, the the app just returns an instructions on how to build the UI, but the chat will actually build the UI. And you have fully generative UI on the other end of the spectrum. And if you know cloud apps, yeah, MCP apps is agnostic to the way the UI is generated. And if you know cloud apps imagine feature where you can just ask cloud to generate a UI for you. That's actually based on MCP apps. So, this is an MCP app behind the scenes, but it supports generative UI. So, we're working on interoperability with those other standards. And actually just a few days ago we released a guide on how to do A2UI versus a generative UI standard and MCP apps which is the standard. How to do interoperability. How can a server can write A2UI and ship it to Gemini, but also wrap it as an MCP app to ship to ChatGPT and vice versa.
Comments
Sign in to comment.
Loading comments…