GenUI SDK v1.3.0 Decouples Core, Adds Pluggable UI Materials and React Support
Generative UI tooling that couples rendering to a single component library forces teams into all-or-nothing adoption. Decoupling the core from the materials and adding React support lowers the integration cost for shops that already standardize on Element Plus, Ant Design, or a custom design system.
The OpenTiny team released GenUI SDK v1.3.0, a generative UI toolkit that now ships its core capabilities—protocol definitions, prompt generation, streaming schema parsing, and JSON repair—as an independent npm package. Renderers no longer bundle a fixed component library; instead, a provider injects material configs, with official packs for OpenTiny, Element Plus, and Ant Design (React alpha).
Renderer improvements target production gaps: default props prevent crashes during streaming renders, a new refs system lets schemas call component instance methods directly, and async custom actions with return values enable multi-step backend validation flows. Lifecycle hooks onMounted and onUnmounted fire once after the full schema arrives, so AI-generated pages can fetch business data and clean up listeners.
The playground adds one-click Vue/Angular switching within the same session, A2A v1.0 with automatic protocol fallback, OpenAPI-to-tool conversion, schema version history with diff view, and bilingual UI. A React renderer alpha with Ant Design materials is available for early testing.
Pulling core protocol and parsing logic into a standalone package signals that generative UI runtimes are maturing into composable layers rather than monolithic chat widgets.
Default props as a streaming fallback is a pragmatic fix: most component libraries were never designed for incremental schema delivery, so the SDK absorbs that impedance mismatch rather than forcing library rewrites.
Adding refs and async actions with return values pushes the schema format past static layout into genuine application logic, blurring the line between a UI description language and a low-code runtime.
Lifecycle hooks that wait for the complete schema before firing acknowledge a real constraint of streaming—partial schemas can't reliably trigger side effects—and solve it with a simple gate rather than complex state machines.
Offering Mini and Standard prompt versions is a cost lever: teams can trade component richness for lower token spend without changing the SDK, which matters when running against paid model APIs.