Skip to main content
Knowledge mapUnderstand neighboring approachesIndustry concepts and standards

You are here. See how this question connects to other ideas.

Select a node to open its page · Expand to read within the map

Knowledge mapFollow a connection. Understand a question.
← AFS and interfaces

Learning path

Understand neighboring approaches

Put protocols, SDKs, hosts and design tools in their respective places.

For readers familiar with AFS-UI and AUP who want to understand neighboring generative UI projects.

Read the overview, then explore A2UI, MCP Apps, MCP-UI, AG-UI, Flutter GenUI and Stitch. Finish by examining what a path actually means.

You should be able to take one task and identify each approach’s structure, state and operation boundaries. This path supplies a learning framework, not a checkbox verdict on technology selection.

Also explore OpenAI Intelligent UI, which brings the question into everyday answers. Examine the product interaction, then distinguish published contracts from implementation details.

Along this path

  1. How should generative UI approaches be compared?

    Compare responsibilities, addresses, state and interaction contracts.

  2. What does A2UI solve?

    Render agent-provided interface descriptions through client-supported components.

  3. What are MCP Apps?

    Bring interactive HTML interfaces from MCP tools into supporting hosts.

  4. How do MCP-UI and MCP Apps relate?

    Separate the standard from implementation tooling and legacy compatibility.

  5. Are AG-UI and A2UI the same layer?

    Agent–application event exchange differs from interface description.

  6. Is Flutter GenUI SDK another protocol?

    It provides implementation tools for generative interfaces in Flutter.

  7. Where does Google Stitch fit?

    Compare its design workflow separately from runtime protocols.

  8. Does every path address the same kind of thing?

    Compare scope, resolution and available operations.

  9. What is OpenAI Intelligent UI?

    Interactive answers, streamable components and the boundaries to examine alongside AFS-UI.

Check your understanding

Do similar names imply direct substitutes?

Not necessarily. They may occupy different layers or have protocol–implementation and complementary relationships.

Referenced here

Terms

  • AFS UI

    AFS-UI builds interfaces over the addressable resources of AFS. People use a rendered interface; agents can inspect and operate its exposed structure through paths. AUP describes the interface and its interactions, while a UI device such as Web Device renders it.