Use cases

What teams build with AnySDUI

Four interactive use cases with their Kotlin code and wire messages, then two case studies from the fediim design system.

Real-world use cases & implementation

See what AnySDUI builds in production

From AI copilots that mix standard Google A2UI components with live charts and subtree themes, to multi-screen checkout flows and brownfield enterprise AAR wrappers. Pick a use case to inspect the Kotlin implementation, wire payload and live interactive preview.

a2ui v1.0 · updateComponents · fediim + charts + foundation ThemeScope
{ "version": "v1.0", "updateComponents": {
  "surfaceId": "finops_copilot",
  "components": [
    { "id": "root", "component": "Card", "title": "Cloud spend and forecast",
      "content": ["spend_chart", "approval"] },
    { "id": "spend_chart", "component": "BarChart",
      "catalogId": "urn:anysdui:compose-charts:1.0.0",
      "label": "Monthly cloud spend",
      "categories": { "@path": "/finops/months" },
      "series": { "@path": "/finops/series" } },
    // Subtree theme: only the approval banner turns light
    { "id": "approval", "component": "ThemeScope",
      "catalogId": "urn:anysdui:compose-foundation:1.12.0",
      "theme": { "mode": "light" }, "child": "payout" },
    { "id": "payout", "component": "Banner", "tone": "warning",
      "title": "Pending payout: €12,500", "actionLabel": "Approve",
      "onAction": { "event": { "name": "approvePayout" } } }
  ]
} }
a2ui v1.0 · updateDataModel · live

            
interactive preview · click quarter or approve

Cloud spend and forecast

Jul
Aug
Sep
Pending payout: €12,500 €48,200 · Q3 Variance -4.2%
Ready · bound to /finops/quarter and /finops/series
Case study · Design system

The fediim design system, server-driven

fediim's design system is a Compose Multiplatform library used across its products. Its components already existed. A small bridge module wraps each one with an annotation, so the core library does not depend on AnySDUI at all.

52components exposed to the server
3showcase targets: Desktop, Android, Wasm
1bridge module, components-sdui
  • Catalog published as urn:fediim:fds:0.1.0, versioned with the library.
  • Every component has an A2UI v1.0 sample message, from Button and Table to DiffViewer and PromptComposer.
  • The showcase switches theme palettes at run time and shows the JSON behind each screen.
components-sdui/build.gradle.kts
api(project(":components"))   // the untouched design system
implementation(libs.anysdui.annotations)
api(libs.anysdui.runtime)

ksp {
    arg("anysdui.catalogId", "urn:fediim:fds")
    arg("anysdui.libraryVersion", "0.1.0")
}

dependencies { add("kspCommonMainMetadata", libs.anysdui.processor) }
SduiActions.kt
@SduiComponent
@Composable
fun Button(
    @SduiUserGesture onClick: () -> Unit,
    variant: ButtonVariant,
    modifier: Modifier = Modifier,
    @SduiDefault("ButtonSize.Medium") size: ButtonSize = ButtonSize.Medium,
    @SduiDefault("true") enabled: Boolean = true,
    @SduiDefault("null") @SduiChild icon: (@Composable () -> Unit)? = null,
    @SduiDefault("null") text: String? = null,
    @SduiChildren content: @Composable RowScope.() -> Unit,
)
Case study · Design to ship

From a Figma frame to a shipped screen

One new component, six steps, most of them automated. AnySDUI handles the parts in the middle and at the end. The rest is tooling many teams already have. Each step says who provides it.

1
Designer

Design

The component is drawn in Figma. Its colours, type and spacing are exported as W3C design tokens, and frames push directly to AnySDUI servers.

AnySDUI: token import & Figma push pipeline (RFC-0012)
2
Coding agent

Build

An agent writes the component in Compose from the design spec and tokens, then annotates it so it joins the catalog.

Your coding agent
3
CI

Verify

Screenshot tests render it in light and dark and fail the build when a pixel changes. New shots are reviewed against the design reference.

Your CI
4
Maintainer

Release

A new version of the design system library is published. The catalog is regenerated with it, so servers and agents learn the component at once.

AnySDUI: catalog generation, today
5
Copywriter

Translate

Copywriters edit the strings in Translatio and watch them change on the real screen, in every language.

Translatio: today
6
Server or agent

Ship

Screens and multi-screen flows are composed from the catalog, shared via instant web links, and rendered natively across all 4 platforms.

AnySDUI: flows & share links, today

What still needs an app update. A brand-new component is compiled code, so apps pick it up with the new library version. Everything built from components already in the app, plus tokens, layouts and copy, changes from the server.