Concept card

AI-native UX in SAP — the compositional design system, SAP Fiori elements and Joule Work

As of 2026-10-16

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is AI-native UX in SAP?

SAP describes a compositional design system that lets AI assemble enterprise UI at runtime from vetted primitives, composites and design knowledge; SAP says it already powers Joule Work (Sapphire, May 2026). Ten SAP TechEd 2026 sessions (27-29 Oct) cover it, AI-native UX and SAP Fiori elements with AI tooling. GA, pricing and customer authoring are not published.

Status first: a mix of documented design pages and catalogue descriptions

Two kinds of source stand behind this card. SAP's design site publishes pages on the compositional design system (read through search excerpts on 16 October 2026, because sap.com refused direct retrieval). The SAP TechEd 2026 catalogue lists ten sessions about it, about AI-native user experience and about SAP Fiori elements in the age of AI. Catalogue entries are descriptions, not product announcements. Where the design pages and the catalogue say nothing (names, GA dates, pricing, APIs), this card writes "not published".

What SAP describes: a design system that AI can read

A classic design system documents how components look. SAP's page "The Compositional Design System" argues that this is not enough once AI, not a person, assembles the screen: the system must also say which combinations are valid. SAP therefore describes an extension of its existing design system with relationship logic, structured metadata and guardrails, so that generative AI produces a coherent interface rather than parts that only work one by one. The catalogue names the building blocks of the TechEd sessions: primitives, composites and design knowledge (JW129). Per SAP's get-started page, the output is a technology-agnostic composition blueprint that a renderer can turn into UI in any front-end technology. SAP's own words for JW129: a "brand-safe, enterprise-quality, generative UI engine that powers experiences like Joule Work".

Why it matters

Joule Work, Spaces and generated workspaces change what a Fiori app is for: the UI may be assembled per user and task, so your OData services, annotations and authorisations become the real contract.
The status is split: SAP's design pages say the system is used in Joule Work, while the roadmap says only generation is live and intent and context detection come later. Proposals must say which.
Ten TechEd sessions give one week to learn the stack end to end, from UX strategy (ST116) to hands-on authoring (JW161); the answers on openness, licence and audit only come after 30 October.

Key points

SAP describes the compositional design system as an extension of its design system with relationship logic, structured metadata and guardrails, so AI composes coherent UI (SAP design pages, via search excerpts).
Building blocks named in the catalogue (JW129): primitives, composites and design knowledge; output is a technology-agnostic composition blueprint.
SAP says it is used in Joule Work, announced at SAP Sapphire in May 2026; Spaces generates workspaces on the fly (SAP design page; SAPinsider).
Roadmap (via excerpts): phase one is generation; intent and context detection are not yet active.
Fiori elements remains the declarative route; JW213 and JW811 stress annotations, OData and 'intent- and action-ready semantics'.
The Fiori MCP server (npm, stdio, nine tools) generates and modifies Fiori apps from OData or CAP services; no release status is stated on its page.
No GA date, price, public API or customer-authoring rule is published as of 16 October 2026.

Terms used on this page

Compositional design system: SAP's design system extended with relationship logic, metadata and guardrails so AI can assemble UI.
Primitive: Smallest vetted UI building block in the catalogue wording (JW129).
Composite: Reusable arrangement of primitives that the AI can place; authored in JW161.
Design knowledge: Machine-readable rules on which compositions are valid and brand-safe.
Composition blueprint: The technology-agnostic description of a UI that a renderer draws (SAP get-started page).
Spaces: Joule Work feature that generates workspaces on the fly, per SAPinsider and the TechEd abstracts.
SAP Fiori elements: Framework that builds Fiori apps from OData services and annotations without free UI coding.
Fiori MCP server: npm package @sap-ux/fiori-mcp-server giving AI coding assistants tools to create and edit Fiori apps.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →