UX & Fiori at SAP – is it the same thing?

It seems there is a lot of confusion related to UX within SAP. Many think that UX is just about Fiori, while thinking very different things about what Fiori is. I’ve met people who think that UX in SAP is just about standard Fiori apps that we deploy during S/4HANA implementations. I’ve met people who think Fiori is a programming language and therefore anything that is built using it has great UX. Allow me to share what I was taught and what I’ve been telling customers so far about what UX means at SAP.

User Experience is a general term for how an end-users interact with a piece of software and the feeling they get from using it. Foundation of the UX in SAP is built upon SAP Fiori – a design system that specifies the look & feel, controls, floorplans and common functions, and includes guidelines and stencils for designers and developers.

Fiori starts with core values, principles and practices. Practices ensure adherence to the user centered design process; thus we do user research, define personas, provide guidelines etc. Fiori has these five design principles, which have been stable from the beginning:


However just because an application is built using SAP UI5 it doesn’t mean it follows Fiori standards properly. I call these apps “Fiori-like” as they are built with the Fiori controls but often break the Fiori principles and guidelines and therefore do not provide the best UX to the customers. Here is a very simple made-up example:


Let’s have a look at how Fiori is misapplied in this screenshot:

  • Incorrect button placement. “Save” button should always be in a footer toolbar in the edit mode of an object. Having finalizing buttons at the bottom right of the screen ensures consistency between all Fiori applications and builds a pattern of use.
  • Breaking the pattern for object editing. You should not have editable fields in the object header – it snaps on scroll, so this key information (which is the only data recommended to be in the object header to avoid clutter) could be easily missed by a user.
  • Colors abuse. You should also avoid using too many accent colors. Having only some things highlighted will allow users to quickly understand what requires user’s attention.
  • Markup violation. Forms used in the content area should all be aligned between each other – this way user can concentrate on the content itself and not the way it’s distributed over the screen, which supports consistency and usability.

Nevertheless, the app in the picture could be built with SAP UI5 and be presented as a Fiori application. It creates the impression of Fiori UX while not adhering to Fiori design principles – thus completely undermining Fiori UX. Try to avoid that and be mindful to the UX you’re creating.

If we want to provide the best user experience to our customers not only do we need to implement standard Fiori applications and use SAP UI5 to build new ones, we need to follow the Fiori system guidelines while doing that (I will dive into this in my next post dedicated to UX designer role – stay tuned!) We are also responsible for the overall user experience of the system – how people are accessing it, if they need to switch between systems while working (and ensure we make it seamless), how their launchpads are set up and much more.

The distinction between consumer and enterprise products from an experience point of view is narrowing quickly. Regardless of context, users expect and demand well designed, intuitive products. Indeed, it might be more important in an enterprise context because if users are frustrated by poor usability and overall experience, it’s much harder for them to be as efficient or productive as they could.

Understanding how to apply the Fiori design guidelines correctly with the help of a UX designer can ensure you deliver quality products with the customer in mind. If we can meet and even exceed the expectations, our users and customers will not only be more effective in their respective roles, but happier and more willing to use SAP products down the line.