Which SAP UI Approach Fits Your Scenario?

Choosing an SAP UI approach means matching the task, the users and the available standard content to the right option: a standard SAP Fiori app, a custom app built with SAP Fiori elements, a freestyle SAPUI5 app, SAP Build Apps, or SAP GUI. For multi-role processes, deciding where the process logic lives comes first.

How do you choose between SAP Fiori elements, freestyle SAPUI5 and SAP GUI?

Question 1

What does the user mainly need to do?

Directional guidance for typical scenarios. It is not a product evaluation, sizing or licensing assessment.

Which UI approach fits which scenario?

Legend:Strong fitPossible fitWeak fitNot applicable

  • Approve documents on desktop and mobile

    Standard SAP Fiori app
    Strong fit
    Custom app with SAP Fiori elements
    Possible fit
    Freestyle SAPUI5
    Possible fit
    SAP Build Apps
    Possible fit
    SAP GUI / SAP GUI for HTML
    Weak fit
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: Whether SAP delivers an approval app and workflow scenario for the document

  • High-volume entry or mass changes by expert users

    Standard SAP Fiori app
    Possible fit
    Custom app with SAP Fiori elements
    Possible fit
    Freestyle SAPUI5
    Possible fit
    SAP Build Apps
    Weak fit
    SAP GUI / SAP GUI for HTML
    Strong fit
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: Keystroke speed and data density, validated with daily users

  • Find, filter and act on many business objects

    Standard SAP Fiori app
    Strong fit
    Custom app with SAP Fiori elements
    Strong fit
    Freestyle SAPUI5
    Possible fit
    SAP Build Apps
    Weak fit
    SAP GUI / SAP GUI for HTML
    Possible fit
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: If no standard app fits, List Report + Object Page is the default pattern

  • Occasional users and self-service requests

    Standard SAP Fiori app
    Strong fit
    Custom app with SAP Fiori elements
    Strong fit
    Freestyle SAPUI5
    Strong fit
    SAP Build Apps
    Possible fit
    SAP GUI / SAP GUI for HTML
    Weak fit
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: Guidance and simplicity matter more than density

  • Guided multi-step entry with custom validation

    Standard SAP Fiori app
    Possible fit
    Custom app with SAP Fiori elements
    Possible fit
    Freestyle SAPUI5
    Strong fit
    SAP Build Apps
    Possible fit
    SAP GUI / SAP GUI for HTML
    Weak fit
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: Whether the steps fit a floorplan or need a custom journey

  • Monitor KPIs and drill into exceptions

    Standard SAP Fiori app
    Strong fit
    Custom app with SAP Fiori elements
    Strong fit
    Freestyle SAPUI5
    Possible fit
    SAP Build Apps
    Weak fit
    SAP GUI / SAP GUI for HTML
    Weak fit
    Analytics (embedded or SAP Analytics Cloud)
    Strong fit

    Deciding factor: Single SAP S/4HANA source (embedded) vs. multiple sources (SAP Analytics Cloud)

  • Technical administration and configuration

    Standard SAP Fiori app
    Weak fit
    Custom app with SAP Fiori elements
    Weak fit
    Freestyle SAPUI5
    Weak fit
    SAP Build Apps
    Weak fit
    SAP GUI / SAP GUI for HTML
    Strong fit
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: Most administration still runs in SAP GUI and specialized tools

  • Transaction with no SAP Fiori equivalent, needed in the launchpad

    Standard SAP Fiori app
    Not applicable
    Custom app with SAP Fiori elements
    Possible fit
    Freestyle SAPUI5
    Possible fit
    SAP Build Apps
    Weak fit
    SAP GUI / SAP GUI for HTML
    Strong fit
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: SAP GUI for HTML is the fastest bridge; redesign only when the task justifies it

  • Add a few fields or rules to a standard app

    Standard SAP Fiori app
    Strong fit
    Custom app with SAP Fiori elements
    Possible fit
    Freestyle SAPUI5
    Weak fit
    SAP Build Apps
    Weak fit
    SAP GUI / SAP GUI for HTML
    Not applicable
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: Stay within key user extensibility before copying apps

  • Field work with poor or no connectivity

    Standard SAP Fiori app
    Weak fit
    Custom app with SAP Fiori elements
    Weak fit
    Freestyle SAPUI5
    Weak fit
    SAP Build Apps
    Weak fit
    SAP GUI / SAP GUI for HTML
    Weak fit
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: Browser-based UIs assume connectivity; offline work usually needs a native mobile approach

  • Multi-step process across roles with business-specific rules

    Standard SAP Fiori app
    Possible fit
    Custom app with SAP Fiori elements
    Weak fit
    Freestyle SAPUI5
    Weak fit
    SAP Build Apps
    Possible fit
    SAP GUI / SAP GUI for HTML
    Weak fit
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: The UI is the smaller decision: first decide where the process logic lives, then choose the screens

  • Process spanning SAP and non-SAP systems

    Standard SAP Fiori app
    Weak fit
    Custom app with SAP Fiori elements
    Weak fit
    Freestyle SAPUI5
    Weak fit
    SAP Build Apps
    Possible fit
    SAP GUI / SAP GUI for HTML
    Weak fit
    Analytics (embedded or SAP Analytics Cloud)
    Not applicable

    Deciding factor: Needs orchestration and integration across systems; no single SAP UI holds this logic

Fit ratings are directional editorial guidance for typical scenarios, not a product evaluation, sizing or licensing assessment. Validate with your release, licenses and users.

What are all the possible outcomes?

Use the standard SAP Fiori app

A standard app that real users can complete the task in is the lowest-cost, upgrade-safe option. The work shifts to role design, catalog assignment and adoption.

Watch out for

  • Validate with daily users, not only in a demo system.
  • Check required business roles, catalogs and OData services in the Reference Library.

Related entriesSAP Fiori Apps Reference Library · Business Role · Rapid Content Activation (STC01 Task Lists)

Go deeperWhen the Standard Fiori App Covers 80% — and the Missing 20% Kills Adoption

Standard app + key user extensibility

When gaps are fields, simple rules or layout, key user extensibility closes them without copying the app, so SAP updates keep flowing.

Watch out for

  • Stop if the extension starts to reshape the flow — that is a different app.
  • Document every adaptation; they accumulate quietly.

Related entriesKey User Extensibility · UI Adaptation (Adapt UI) · Clean Core

Go deeperWhen the Standard Fiori App Covers 80% — and the Missing 20% Kills Adoption

Build a custom app with SAP Fiori elements

If the task fits a floorplan, SAP Fiori elements generates most of the UI from a RAP or CAP service and annotations, keeping the app consistent with SAP's own apps.

Watch out for

  • Service and annotation design become the main effort.
  • Use the flexible programming model for gaps before switching to freestyle.

Related entriesSAP Fiori Elements · ABAP RESTful Application Programming Model (RAP) · SAP Cloud Application Programming Model (CAP) · UI Annotations · Flexible Programming Model

Go deeperDoes Fiori Elements Replace UI5 Developers?

Build a freestyle SAPUI5 app

Freestyle SAPUI5 gives full control over complex interactions and guided journeys, at the cost of more code to build, test and maintain.

Watch out for

  • Plan ownership and an upgrade-testing budget before the first line of code.
  • Keep business rules in the service layer, not in the UI.

Related entriesFreestyle SAPUI5 App · SAPUI5 · Custom Apps (Z-Apps)

Go deeperDoes Fiori Elements Replace UI5 Developers?

Consider SAP Build Apps — with governance

For simple forms and lists with limited logic, a low-code builder on SAP BTP can deliver faster, if data access, ownership and lifecycle are governed from day one.

Watch out for

  • Check licensing and SAP BTP prerequisites.
  • Define who maintains the app when the builder moves on.

Related entriesSAP Build Apps · Destinations (SAP BTP) · SAP Business Technology Platform (SAP BTP)

Keep SAP GUI (or SAP GUI for HTML in the launchpad) for now

For expert, high-volume work in dense transactions, SAP GUI often remains the faster tool. SAP GUI for HTML can place the transaction in the launchpad without a redesign.

Watch out for

  • Revisit when SAP delivers a native app with equivalent coverage.
  • In SAP S/4HANA Cloud Public Edition, plan around SAP-delivered apps only.

Related entriesSAP GUI for HTML (Web GUI) · Target Mapping

Go deeperWhen Should You Keep SAP GUI Instead of Moving to Fiori? · SAP Fiori vs HTML GUI: Why Not Every Tile Is a Native Fiori App · SAP Fiori for Power Users: Why Adoption Is Harder Than It Looks

My Inbox + flexible workflow

For delivered document scenarios, key users configure approvals in flexible workflow and approvers act in My Inbox — no custom UI needed.

Watch out for

  • Agree on the approval policy before configuring conditions.
  • Use roles or responsibility teams, not named users, as recipients.

Related entriesFlexible Workflow · My Inbox · Responsibility Management

Decide the process layer before the UI

When an approval or task spans roles, documents or systems, the main question is where the process rules will live and who will change them. Options include flexible workflow for delivered scenarios, SAP Business Workflow in the backend, SAP Build Process Automation on SAP BTP, or an existing workflow layer in the landscape. Choose the screens after that decision.

Watch out for

  • Map the process — roles, decisions, exceptions, hand-offs — before choosing any tool.
  • Ask who will change the rules next year, and how fast.

Related entriesFlexible Workflow · SAP Business Workflow · SAP Build Process Automation · My Inbox

Go deeperProcess Complexity Is Now the #1 Barrier to SAP Process Automation

See where workflow logic can live on the architecture map →

Embedded analytics: KPI tiles, analytical list page or overview page

For operational KPIs on SAP S/4HANA data, embedded analytical apps work on live CDS-based data inside the launchpad, close to the transactions users act on.

Watch out for

  • Performance depends on the underlying CDS views.
  • Check standard analytical apps before building.

Related entriesAnalytical Apps · Analytical List Page (ALP) · Overview Page (OVP) · SAP Smart Business KPIs

SAP Analytics Cloud

When data comes from several systems or planning is required, a dedicated analytics platform fits better than embedded apps.

Watch out for

  • Separate licensing and data-integration effort.

Related entriesAnalytical Apps · SAP Business Technology Platform (SAP BTP)

SAP GUI and specialized administration tools

Most technical administration and Customizing remain in SAP GUI and dedicated tools. SAP Fiori covers selected admin tasks, not the whole discipline.

Watch out for

  • Do not force admin work into launchpad tiles for consistency's sake.

Related entriesPFCG and SAP Fiori Roles · /IWFND/MAINT_SERVICE · Launchpad Content Manager

Go deeperWhen Should You Keep SAP GUI Instead of Moving to Fiori?

What should you validate before deciding?

  • Has the standard app been tested with daily users, not only demoed?
  • Which business roles, catalogs and services does it require (SAP Fiori Apps Reference Library)?
  • Who owns a custom app after go-live, and who pays for upgrade testing?
  • Which licenses and SAP BTP services does the option require?
  • Where will business rules live, and who can change them?
  • What are the performance expectations for the busiest users?

Why is a process question different from a UI question?

A UI decision answers how one person performs one task. A process decision answers how work moves between people, systems and rules over time: who acts next, under which conditions, within which deadline, and what happens on exceptions. A screen can be replaced without changing the process, and a process can change without touching any screen. Treating the two as one decision is a common source of rework in SAP Fiori projects.

FAQ

Should we build custom SAP Fiori apps or use standard ones?

Start with standard apps, validated with daily users, and extend them with key user tools where gaps are small. Build custom apps only when the task, users or flow differ in ways standard apps and extensions cannot cover, and only with a clear owner.

Is SAP Fiori elements always better than freestyle SAPUI5?

No. SAP Fiori elements is faster and more consistent when a task fits a supported floorplan. Freestyle SAPUI5 is the better fit for complex interactions or guided journeys that floorplans cannot express.

When should we keep SAP GUI?

Keep SAP GUI for expert, high-volume work in dense transactions and for technical administration, where it is often faster. Revisit when SAP delivers a native app with equivalent coverage and the users confirm it works for them.

Is SAP Build Apps a replacement for SAPUI5 development?

No. SAP Build Apps suits simple forms and lists built quickly by business technologists. Complex, long-lived or performance-critical apps usually still call for SAPUI5 or SAP Fiori elements.

Who should own custom SAP Fiori apps after go-live?

A named team with budget for maintenance and upgrade testing. Custom apps without an owner become blockers at the next SAP S/4HANA upgrade.

SAP, SAP Fiori, SAPUI5, SAP S/4HANA, SAP BTP and other SAP products and services mentioned are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. This guide is independent and is not affiliated with, sponsored or endorsed by SAP SE.