SAP Fiori

Overview

What problem does it solve?

SAP Fiori organizes complex business work around five published principles: role-based, adaptive, simple, coherent, and delightful. Reusable floorplans connect information architecture to implementation.

What the system documents

• Use role-based, adaptive, simple, coherent, and delightful as the overarching design principles.Supporting reference: SAP Fiori principles
• Choose a standard floorplan when it fits the business-object task; predefined structures improve consistency but intentionally constrain unsupported layouts.Supporting reference: Layouts and floorplans
• Accessibility responsibilities are shared: frameworks supply capabilities while application teams still define meaningful structure, labels, text, and context.Supporting reference: SAP Fiori for Web

Why this system is worth studying

Fiori is one of the strongest systems to study for enterprise information architecture. Its floorplans make the relationship between shell, page, business object, table, action placement, draft handling, and message handling unusually explicit.

Consistent analysis model

System architecture at a glance

Target environmentNot publicly documented

SAP business applications and role-based enterprise workflowsCompare this dimension

Platform strategyNot publicly documented

Fiori design language across SAPUI5, Fiori elements, and SAP Web ComponentsCompare this dimension

FoundationsAnalysis

Semantic color, typography, icons, spacing, themes, interaction states, and business-data conventionsEvidence: SAP Fiori principlesCompare this dimension

Token maturityNot publicly documented

Themeable implementation through SAP UI technologies and semantic design valuesCompare this dimension

Component architectureAnalysis

UI elements compose into layouts and task-specific floorplans, with SAPUI5 and Web Component implementationsEvidence: Layouts and floorplansCompare this dimension

Interaction patternsAnalysis

Object handling, draft handling, message handling, action placement, navigation, and searchEvidence: Layouts and floorplansCompare this dimension

AccessibilityAnalysis

Framework capabilities support semantics and keyboard use; app teams remain responsible for structure, labels, and understandable messagesEvidence: SAP Fiori for WebCompare this dimension

Responsiveness / adaptivityAnalysis

Dynamic pages, flexible columns, responsive spacing, compact/cozy density, and action overflowEvidence: SAP Fiori for WebCompare this dimension

Content guidanceAnalysis

Dedicated Fiori UI text guidance covers recurring terminology and floorplan-specific writing decisionsEvidence: SAP Fiori for WebCompare this dimension

Documentation qualityAnalysis

Extensive guidelines connect principles, floorplans, controls, interaction, responsiveness, and developer hintsEvidence: OpenUI5Compare this dimension

GovernanceAnalysis

SAP maintains guideline versions and implementation frameworks across product releasesEvidence: OpenUI5Compare this dimension

Design-to-codeAnalysis

Fiori elements, SAPUI5, Web Components, stencils, and explicit developer hintsEvidence: OpenUI5Compare this dimension

Best learning valueNot publicly documented

Floorplans, dense business objects, and adaptive enterprise workflowsCompare this dimension

Notable tradeoffAnalysis

Fiori’s vocabulary and page structures are tightly connected to SAP application architecture. For unconstrained consumer products, Material or native platform guidance offers a more transferable starting point.Evidence: SAP Fiori for WebCompare this dimension

What to study

Take these ideas into your own system

Primary references

Evidence and verification scope

Checked September 4, 2026: Design principles, floorplans, web components, interaction patterns, and accessibility responsibilities. UXD Systems explains and compares; these sources remain the authority for current implementation details.