Appearance
Frontend
The frontend in the AI-Driven Development Model is built on React + TypeScript. The component layer depends on the design requirement:
| React & shadcn/ui | UI5 Web Components | |
|---|---|---|
| When | Default for modern product-style apps | Only when SAP Fiori design compliance is strictly required |
| Components | shadcn/ui on Base UI + Tailwind CSS | UI5 Web Components for React |
| Look & feel | Custom, product-style | SAP Fiori design language |
Decision
Default to React & shadcn/ui. Switch the component layer to UI5 Web Components only when Fiori design compliance is mandated — the React + TypeScript + Vite foundation and the typed OData v4 data-access layer stay the same either way.
Not classic Fiori
UI5 Web Components ≠ SAP Fiori elements / classic UI5 apps. We stay on React and adopt only the UI5 Web Components for Fiori-compliant styling — not the Fiori Elements / freestyle UI5 application stack.
Fiori floorplans without UI5
Even on the default React & shadcn/ui path you get annotation-driven Fiori floorplans (list report, object page, value helps) via the React Fiori building blocks, fed by CAP's Fiori annotations. Reach for UI5 Web Components only when the actual Fiori design language is mandated — the floorplan productivity itself does not require UI5.