When I open https://a2ui-project.github.io/composer/, I see this:
This is fine if you're an experienced user doing development with a custom catalog. But for new or casual users, it's not very approachable. I think there is a use case like:
As a developer who is evaluating A2UI, I want to explore the available components and try generating some new layouts, to help me understand the capabilities of A2UI in my own problem domain
Currently, we have AG-UI's Composer at https://a2ui-composer.ag-ui.com/, which works out of the box, with no additional configuration. Of course, a Renderer URL is necessary to allow the composer to use custom catalog implementations, and this is one of the great advantages of the new composer. But it would be possible to get the new Composer to work with the basic catalog with no separate renderer process, by bundling in a basic catalog renderer.
So how about something like:
- If no renderer URL is set, the Composer uses a built-in basic catalog renderer, potentially without an iframe. There can be some menu item to connect to a custom renderer process as necessary.
- If API key is set, still display a gallery of components and layouts, like AG-UI's app does, and provide preview functionality, but request an API key if the user wants to generate layouts.
- [Future] Let users use the composer, at least with the basic catalog, for free without an API key. This probably involves some rearchitecture so that the LLM orchestration parts with the API key embedded can be optionally run as a Google-deployed server, to prevent people from abusing the Gemini quota in the GCP project we create. We should also estimate cost. I wonder if we could get it to work with flash-lite to make that less of an issue.
When I open https://a2ui-project.github.io/composer/, I see this:
This is fine if you're an experienced user doing development with a custom catalog. But for new or casual users, it's not very approachable. I think there is a use case like:
As a developer who is evaluating A2UI, I want to explore the available components and try generating some new layouts, to help me understand the capabilities of A2UI in my own problem domain
Currently, we have AG-UI's Composer at https://a2ui-composer.ag-ui.com/, which works out of the box, with no additional configuration. Of course, a Renderer URL is necessary to allow the composer to use custom catalog implementations, and this is one of the great advantages of the new composer. But it would be possible to get the new Composer to work with the basic catalog with no separate renderer process, by bundling in a basic catalog renderer.
So how about something like: