Similar Product but for React/ Next only

[gauravfs-14]

Today, I came across this project and found the design direction interesting. Some of the core ideas overlap with a library we built independently last October, including predefined UI components, a JSON-based registry for configuration, and a TypeScript-first implementation targeting React and Next.js.

While the implementations differ in structure and goals, the conceptual overlap caught my attention, particularly around component registries and predefined components.

If useful for discussion or comparison, our implementation is here: https://github.com/gauravfs-14/adaptly

I would be interested in hearing how others think about the tradeoffs between different registry designs, typing strategies, or framework integration approaches.

[dmandar]

Thanks for sharing Adaptly—it’s validating to see parallel thinking around component registries. For A2UI, we’ve aimed to push that utility further by building a universal toolkit on top of A2A that lets agents drive UI on any platform, regardless of the framework. We’d love your perspective on standardizing these schema definitions, so please feel free to browse and provide feedback!

[gauravfs-14]

Thanks for the thoughtful response. It’s genuinely great to see similar ideas converging from different directions. The way you’re positioning A2UI as a framework-agnostic, agent-driven layer on top of A2A is particularly interesting, especially around schema design and cross-platform control.

I’ve been browsing the code, and it’s exciting to see how these ideas are taking shape. Glad to continue the conversation and exchange perspectives as things evolve.