In our previous articles, we looked at the transition from SAP ECC to S/4HANA mainly from the perspective of data, architecture, and business readiness. But as the transformation moves closer to end users, another important question comes into play:
How should SAP applications be designed so that they are fast to develop, easy to use, and do not create unnecessary technical debt?
In new UX/UI projects, the decision often comes down to two options: using Fiori Elements or building a custom application with Freestyle SAPUI5. Both can be the right choice. The difference lies in how much flexibility the project needs and how much custom code you want to create and maintain over the long term.
Two Different Development Approaches
Fiori Elements is based on the principle that a large part of the application is generated automatically from metadata. The developer defines the data model using CDS and OData services and uses annotations to determine how the application should look and behave.
The user interface is then created from standard templates, known as floorplans, such as List Report, Object Page, Overview Page, Analytical List Page, or Worklist.
The advantage is that the resulting application is responsive from the start, follows SAP Fiori design standards, and does not require a large amount of custom code.
Freestyle Fiori works in the opposite way. The developer builds the application manually in SAPUI5, creating custom XML views, controllers, and application logic.
This approach provides maximum freedom when designing screens and application behavior. At the same time, it means more development work, more custom code, and greater responsibility for future maintenance.
When Should You Use Fiori Elements?
Fiori Elements is an ideal choice for many standard enterprise scenarios. Typical examples include applications for displaying and managing orders, invoices, materials, customers, or approval processes.
Simply put, it works well wherever users work with a list of data, open a detail view, and perform standard actions.
If the required process can reasonably be built using standard Fiori patterns and annotations, Fiori Elements can offer several practical advantages:
- faster development,
- a more consistent user interface,
- less custom code,
- easier maintenance,
- and less dependency on the individual implementation decisions of a specific developer.
The last point is particularly important for companies. The application is not built solely around the way one particular team designed it. A larger part of its behavior remains within the standard SAP approach.
This is why Fiori Elements is now the preferred option for a large share of enterprise applications.
When Does Freestyle Fiori Make Sense?
Freestyle Fiori has its place where standard templates are not enough. Freestyle SAPUI5 becomes more suitable when the way users work requires an unusual UI or more complex interactions.
Examples may include:
- highly specific workflow scenarios,
- screens that change significantly depending on context,
- complex drag-and-drop interactions,
- visualizations or controls that are not covered by standard floorplans,
- applications with a very specific user flow,
- or solutions that behave more like specialized working tools than traditional enterprise applications.
In these situations, trying to force the requirements into Fiori Elements can become counterproductive.
The most expensive option is often the one that starts as a standard solution and ends up with a large number of workarounds.
If the standard starts creating more limitations than value, Freestyle may be the cleaner solution.
It Does Not Have to Be an Either-Or Decision
In practice, it is not always necessary to choose only one approach.
Fiori Elements supports extensions such as custom actions, additional sections, or custom UI fragments. This means a company can start with a standard application and add custom code only where it is genuinely needed.
This combined approach is often the most efficient. The company benefits from the advantages of the standard while still retaining the flexibility to adapt critical parts to its own needs.
A practical rule is therefore to start with Fiori Elements and move to Freestyle only when the project requirements genuinely go beyond what the standard templates can support.
Fiori Elements vs. Freestyle Fiori
When to use which approach
What Should a Company Consider Before Making a Decision?
Before choosing an approach, it is worth asking a few practical questions:
- Can the user process be built using standard Fiori floorplans?
- Is the required UI genuinely specific, or simply different from what the team is used to?
- How much custom logic will need to be developed?
- Who will maintain the application after go-live?
- How frequently are changes expected?
- How important is a consistent user experience across SAP applications?
- And does the custom UI provide enough business value to justify the higher development and maintenance costs?
For most enterprise applications, it makes sense to first check whether Fiori Elements can cover the requirement.
If Fiori Elements supports the process without unnecessary compromises, the company benefits from faster development and less custom code to maintain. If the requirements go beyond the standard, Freestyle provides the flexibility that is needed.
If you are planning a new SAP application or modernizing an existing one, talk to our SAP experts.
We can help you choose the right approach and design a solution that works today and remains sustainable in the future.
Schedule Your ConsultationContinue the Series
SAP ECC End of Support 2027 (2030)
What the end of SAP ECC support means and why it is important for CTOs to preserve enough time for decision-making.
Data Migration to SAP S/4HANA
Why it is worth addressing data quality and ownership before the migration itself begins.
SAP Datasphere
How to connect SAP and non-SAP data without unnecessary duplication and how to think about the data layer in a modern architecture.
