Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Active Participant

We know that SAP Fiori is a design language for enterprise apps that creates exceptional user experiences. SAP offer design solutions that are usable, robust, scalable, and of enterprise-grade quality – implemented in several reference technologies. It also offers SAP FIORI design guidelines and a guide.

Why we need a Design Guidelines?

SAP Fiori is part of the SAPUI5 front-end library, which includes numerous UI controls and various layout options. That makes SAP Fiori applications have the same layout, control behavior and visual appearance. The SAP Fiori Design Guidelines provide a single reference point for anyone working on SAP Fiori apps.

In addition, this system brings many advantages.
You'll have had an easy and reliable design that gives your users a consistent appearance and experience across all of your apps, consistent design and experience.
Easier, faster and more secure  build. Rather than needing to start from scratch, you may use a tried-and-true method with pre-built building blocks. This ensures that new applications are built faster!
Testing will be easier.


The SAP Fiori design system operates on two levels:

  • Universal values, principles, and practices apply across all technology platforms.

  • SAP Fiori design languages provide standardized design guidance across multiple platforms.



Consistency : Offer design solutions that can be adopted by all UI technologies and scenarios across the entire range of the SAP portfolio, leveraging the expertise of the entire SAP design community.

Integration : Provide solutions to integrate different independent products and technologies into an environment that is coherent and easy to use.

Intelligence : Establish machine learning and artificial intelligence as an integral part of the user experience, with a focus on enabling the user rather than taking away control.


Design Principles

The design concept of SAP Fiori is primarily built on five key principles. SAP Fiori provides a role-based, adaptive, easy, cohesive, and enjoyable user experience.

  • Role-Based
    Provide the right information at the right time. SAP Fiori is tailored to your industry, needs, and working style. It is based on our extensive knowledge of today's workforce's many facets. SAP Fiori gives you the correct information promptly and reflects how you operate in real life.

  • Adaptive
    SAP Fiori gives you the freedom to operate where and how you desire, no matter what device you're using. It also delivers essential data that enables immediate understanding.

  • Simple
    Help users focus on what is important. You can perform your task fast and naturally with SAP Fiori. SAP Fiori allows you to find the most suitable essential - core functionalities that are simple to use, and you can customize the experiences to concentrate on the tasks and activities that matter most to you.

  • Coherent
    Provide the same intuitive and consistent experience across the enterprise. SAP Fiori follows a uniform interface and visual design language, whether you're fulfilling a sales order, review your newest KPIs, or managing leave requests. You have the same intuitive experience throughout the company.

  • Delightful
    Enrich the user’s work experience. SAP Fiori increases your professional efficiency by making you easily do your job, in addition to making you work smarter.



Design-led development : Put user experience at the heart of the product lifecycle.



The phases of SAP Design Thinking

Discover   -   Design   -    Deliver


Scope :  At the beginning of a project, the customer's problems and project requirements are identified, understood and documented in a project plan. On the one hand, it contains the needs and challenges of the project. On the other hand, it forms the basis for the further phases of design thinking with a target-oriented question.


360° Research :The needs, expectations and behavior of the end user in their work environment are then observed and documented on the basis of the project requirements created. The design thinking team should become experts with detailed research and aim to obtain a comprehensive 360-degree view of the end user's work situation, define stakeholders and place a qualitative focus on observation. Through interviews, the design thinking teams can put themselves in the shoes of the end users and understand their motivation and roles in the work environment. Direct contact with the end users is very important in this phase, since the needs and behaviors can only be determined by closely observing and empathetically interacting with the end users.


Synthesize: In the third phase, the entire design thinking team gathers and brings together the observations and results from the previous phase. The collected findings are evaluated, interpreted and weighted. The goal is to create a common knowledge base to check whether all information for the further design thinking process has been recorded.


Ideate: the design team, together with the customer, generates and collects different ideas for the implementation of the project requirements defined in the design challenge, based on the created customer journey. At the beginning, all ideas are generated and documented together using various methods, such as brainstorming, without evaluating them. "In order to have a good idea, you first have to have a lot of ideas." The best ideas are then selected by majority vote based on factors such as attractiveness, feasibility and cost-effectiveness.


Prototype: the ideas are implemented with the development of a prototype. The goal of prototyping is not to create a working model. Rather, the ideas are to be given a form and an appearance from which strengths and weaknesses can be recognized and improved through iterative phases. With the prototypes, the ideas should also be made visible and communicable to customers as early as possible. This allows them to test the ideas or at least give feedback at an early stage.


Validate: the developed prototypes are tested and evaluated. It is important that not only the entire design thinking team is present, but also the relevant customers and end users. This is the only way to ensure practical results and evaluations. The aim of this joint test phase is to identify the strengths and weaknesses of the prototypes and to use appropriate measures to set the direction for further development.


Implement: Based on the previously created prototype, the application is developed by the development team.

Test: the developed application is examined for malfunctions using standardized test procedures.

Deploy: the deployment is done and the application is implemented on the customer system.




Labels in this area