Drive your Compose design system without a release.
Ship new flows, A/B tests, and AI copilot screens without an app store release. Add @SduiComponent to the Composables you already have—AnySDUI generates the renderer, strict JSON schema, and Google A2UI v1.0 catalog at compile time across Android, iOS, Windows, Linux, macOS, Web (Wasm & JS), and Android XR / Spatial 3D.
Invoices
3 overduePaid this month
One server push. Every OS & XR viewport in <50ms.
Step through how an annotated Kotlin Composable compiles once and renders simultaneously across Android, iOS, Windows, Linux, macOS, WebAssembly, and spatial 3D/XR—plus direct Figma frame push and self-healing AI agent repair.
Your components, driven from anywhere
Server-driven UI means the server decides what a screen contains, and the app draws it with its own native components. AnySDUI is a Kotlin Multiplatform framework that does this for Compose. It generates all the glue code at compile time, so you never write a JSON parser by hand.
Annotate
Add @SduiComponent to the composables in your design system. Your KDoc comments become the descriptions that agents read.
Generate
At compile time, a processor writes two things: a catalog that describes your components to servers and agents, and the Kotlin code that draws them.
Drive
A server or an agent sends A2UI messages over WebSocket or A2A. Your app draws them with your own native components.
Stop waiting 2 weeks for App Store reviews to ship a screen
No release for UI changes
Layouts, copy, design tokens and multi-screen flows come from the server. Only brand-new components need an app update.
See the features →Keep your design system
Annotate the composables you already have. No rewrite, and no second component library to maintain.
Read the 52-component study →Safe for AI agents
Agents build screens from your catalog. Every message is checked in STRICT mode before it is drawn, and mistakes return with JSON Pointer repair hints.
Every OS + Spatial XR
Android, pure Android AAR wrappers, iOS, Windows, Linux, macOS, Web (Wasm & JS), and Android XR / 3D—all from the same Kotlin code.
Compare with Google A2UI →Built so Staff Engineers and InfoSec say yes
Declarative JSON only, never executable code. Zero runtime reflection, fail-closed STRICT validation, and proven on a 52-component production design system.
Questions engineering & product leads ask first
Can we use it in production pilots today?
Yes—for internal tools, AI copilot surfaces, design-to-device review flows, and scoped feature screens. Core wire protocol and strict validation are verified against 400 of 409 upstream Google A2UI v1.0 conformance tests in CI today. While 1.0.0-alpha01 APIs may evolve before the stable 1.0.0 (Maven Central + binary compatibility guarantee), Founding Design Partners receive hands-on migration support and binary AAR/iOS onboarding. See the roadmap.
Do we have to rewrite our components?
No. You add @SduiComponent to the composables you already have, and binary AAR design systems can be wrapped with a thin function. The fediim design system exposed 52 components this way without changing its core library.
What still needs an app release?
Only brand-new components, because they are compiled code and ship with a new version of your library. Anything built from components already in the app, including layouts, copy, design tokens and flows, changes from the server.
Are we locked in?
No. The wire format is Google's open A2UI v1.0 protocol, so any A2UI agent or server can drive your screens. The framework is open source under the Apache 2.0 license.
How do AI agents fit in?
Every catalog comes with generated skills for Claude Code, Gemini CLI and ADK, and a Kotlin agent SDK. Each screen an agent sends is validated, and errors go back to the model with a hint so it can fix them. More on agents.
What does it cost?
The core compiler, runtime, and all 8 built-in catalogs are 100% free and open source under Apache 2.0. Paid Team and Enterprise plans, for hosted multi-screen flow rooms, signed stakeholder links, Figma cloud push and self-hosted governance, are coming soon. See the plans and the ROI calculator.
Start with one screen
Add three dependencies to your design system module, annotate a component, and render it from a server—or ask our team to build a 2-week PoC with your design system.
implementation("dev.fediim:anysdui-annotations:1.0.0-alpha01")
api("dev.fediim:anysdui-runtime:1.0.0-alpha01")
add("kspCommonMainMetadata", "dev.fediim:anysdui-processor:1.0.0-alpha01")