# What this product does
# Why this matters
AI agents often need more than text. When the desired output is an interactive component—a grid, chart, form, or scheduler—producing a useful result requires choosing components, arranging layout, and iterating. Composer provides a visual, repeatable workflow for those iterations so the interface definition is reusable and inspectable before it appears in production.
# How the Composer workflow works
Describe: Write a natural-language prompt (for example, "Create an inventory dashboard with stock levels and alerts") or pick a starter template.
Preview: Composer renders a live preview using Syncfusion components so you can evaluate layout and interactions without writing framework-specific code.
Refine: Make changes through AI-assisted edits (ask Composer to modify the layout or components) or edit the A2UI JSON directly in the workspace.
Copy: Export or copy the resulting A2UI definition and use it in your application or bind it as the expected UI structure for an agent workflow.
# How Composer fits into the A2UI workflow
Syncfusion treats interface authoring and application rendering as two halves of the same process:
- Design time: A2UI Composer produces a reusable, structured interface definition.
- Runtime: Syncfusion A2UI Components and a renderer map A2UI messages or definitions to concrete controls inside React, Angular, Blazor, or.NET MAUI applications.
# What A2UI means technically
A2UI is a declarative representation of user interfaces expressed as structured data instead of framework-specific UI code. A renderer interprets that definition and maps descriptors (buttons, grids, events) to real components and interactions in the chosen platform.
# What you can build and where it runs
Composer helps you shape interfaces comprised of Syncfusion controls so the preview closely matches runtime behavior. The generated A2UI definitions are supported across React, Angular, Blazor, and.NET MAUI via Syncfusion A2UI Components and a renderer that performs the mapping at runtime.
# Practical steps to get started
- 1Draft a concise natural-language prompt describing the UI and key interactions.
- 2Generate the initial interface in Composer or pick a related template.
- 3Use the live preview to validate component choices and layout.
- 4Apply AI-assisted refinement or hand-edit the A2UI JSON until the structure fits requirements.
- 5Copy the final A2UI definition into your application and configure the renderer to map definition fields to runtime data and actions.
# When to use Composer
Use Composer when you want to prototype or lock down a UI structure before wiring it into application state and backend logic. If you prefer runtime-driven interfaces where agents emit UI messages on the fly, Composer is optional but still useful for defining expected surfaces or templates.
# Bottom line