UI5 apps for ABAP,
built by the team you already have
Your ABAP developers build browser apps for the desktop, the tablet and the handheld scanner, in the SAP system you already run. The business logic and the data stay in SAP. You need no JavaScript team, no extra platform and no license fee. Open source since 2023, in production on the desktop and on the warehouse floor.

- 0 €license fees, for any number of users, systems and apps
- 1 classper app, written in ABAP and handled like any other ABAP code
- 7.02 → Cloudcloud ready: every SAP release, from one source
- 2,900+systems pulled it from GitHub in two weeks, November 2026
- Since 2023open source on GitHub, MIT, every release listed
- 25+contributors, from several companies
What you can build
Every process in SAP that needs a screen
Whatever runs on paper, in Excel or in SAP GUI today becomes a browser app. Each card opens a running example.

Warehouse & logistics
Goods receipt, picking, stock transfers and counts on scanners, handhelds and tablets.
See the example app
Maintenance & service
Work orders, notifications and checklists for technicians, in the workshop or at the machine.
See the example app
Production & shop floor
Confirmations, quality inspections, shift plans and the special processes the standard never covered.
See the example app
Approvals & workflows
Purchase requisitions, invoices, leave and master-data requests: approve in one click, in the launchpad, in Teams or on the phone.
See the example app
Cockpits & dashboards
KPIs, charts and monitors for one team or one process, live from SAP, without a data warehouse or a BI tool.
See the example app
Paper & Excel replaced
Forms, checklists and spreadsheets that live outside SAP become apps that write straight into it.
See the example app
SAP GUI modernized
Reports, lists and transactions turn into browser apps one at a time, with the logic behind them unchanged.
See the example app
Mobile, without an app store
Every app runs in the browser on iOS and Android, so there is no app store and no rollout.
See the example appOne app, every device
The same app, opened on a phone, a tablet and a desktop. It runs in the browser on iOS, Android and Windows, on rugged industrial handhelds too, and the layout adapts on its own.



→ Browse the example apps for the screen closest to yours: hundreds of them, each running in the browser. Or read In a Nutshell for how it works.
Compared with the market
Where it is the shorter path, and where it is not
Four ways to get a UI5 app on SAP, next to abap2UI5. No vendor is named, because offers and prices change; each column describes what you would buy.
✓abap2UI5 is ahead–abap2UI5 is not ahead
| abap2UI5 | RAP + Fiori Elements | Custom SAPUI5 app | Low-code builder in your SAP system | Low-code platform beside SAP | |
|---|---|---|---|---|---|
| License cost | None: MIT, for any number of users, systems and apps | Part of the SAP license | Part of the SAP license | Subscription per user, device or developer, often with a minimum term and a setup fee | Subscription per user or app, plus the tenant |
| Who builds the apps | Your ABAP developers | ABAP plus CDS, RAP and annotation skills | JavaScript / UI5 developers | The ABAP team, in the vendor's designer, after its training | Citizen developers, or developers trained on the platform |
| What an app is | One ABAP class | CDS views, behavior definitions, a service binding and a generated UI5 project | A UI5 project and an OData service | Entries in the designer's tables, built into a UI5 app per screen | A model on the platform |
| Where the business logic lives | In ABAP, next to the data, as it does today | In ABAP, behind CDS and annotations | Split: JavaScript in the browser, a service in ABAP | In ABAP classes bound to the designer's views; the screen in the vendor's tables | On the platform; SAP is reached over connectors |
| SAP releases | NetWeaver 7.02 up to ABAP Cloud, one source | 7.5x and later | Yes, with OData effort per release | Depends on the vendor: some from NetWeaver 7.x, some S/4HANA only | Any, over the connector |
| Extra infrastructure and deployment | None: one endpoint on your SAP system, and the system serves the screen | Fiori frontend server; a deployment per app and version | A frontend deployment (BSP, BTP or web server) | The vendor's add-on or transport, a license key per system, the designer's build per app | The platform's server or cloud tenant |
| Lock-in | Low: apps are plain ABAP classes written against one interface, and the framework stays in your system | SAP's programming model | Low | Screens live in the vendor's tables and run only on its runtime; leaving means rebuilding | Apps live on the platform |
| Support | In the open: Slack and GitHub issues, for anyone at any time; more by mail. No SLA in a contract | SAP support | SAP support for UI5; your app is yours | The vendor's SLA, in the contract | The platform's SLA, in the contract |
8 more rows: speed, UI freedom, designer, offline, certification
| abap2UI5 | RAP + Fiori Elements | Custom SAPUI5 app | Low-code builder in your SAP system | Low-code platform beside SAP | |
|---|---|---|---|---|---|
| Time to the first screen | Minutes; hours to the first app. An ABAP developer learns UI5's controls from the examples, not a new language | After the model, the service, the project and a deployment | After the project setup, the tool chain and a deployment | After the add-on is installed and licensed; the vendors say days to the first app | After the tenant and the connectors are set up |
| Freedom of the UI | Every UI5 control, any layout | SAP's floorplans and their extension points | Every UI5 control | The components the designer offers | The platform's widgets; a Fiori look where the vendor offers one |
| Performance: what a click costs | One plain HTTP request carrying only what changed; no app code and no logic in the browser | OData calls with metadata, batch and draft handling, and the Fiori Elements runtime in the browser | OData calls and an app bundle per app, logic in the browser | A generated UI5 app per screen, with the vendor's runtime in the browser | A round trip through the platform and its connector |
| Source code | Open, every line, on GitHub | Closed | UI5 open, your app yours | Closed; some vendors export the generated app | Closed |
| Click-together designer | None: an app is code, with hundreds of examples to start from and an AI builder that writes the class | None: annotations, in ADT | None: code | Yes: drag-and-drop, templates, versions, for people who do not write code | Yes |
| Standard transactional apps | Possible, but hand-built; the standard route is RAP | Its home ground: list report and object page from annotations | Hand-built | From the vendor's templates | From the platform's templates |
| Offline and a native client | Not built for it: a browser app with its connection to SAP | Offline with extra tooling | Possible, with effort | Some vendors ship a client of their own, with offline | Usually a native client, offline possible |
| SAP certification, add-on delivery | Not on offer: no company behind it. The source, the public tests and the review pack instead | SAP's own | Yours to certify | Often SAP-certified, delivered as an add-on or a transport | A certified integration, beside SAP |
What each column stands for
- RAP + Fiori Elements
- SAP's standard route: a list report or an object page generated from CDS annotations on a RAP service. Part of the SAP license, supported by SAP.
- Custom SAPUI5 app
- A JavaScript project with its own OData service, built in Business Application Studio or VS Code and deployed to the system or to BTP. What a UI5 agency delivers.
- Low-code builder in your SAP system
- A vendor's designer, installed as an add-on or a transport: screens are clicked together, stored in the vendor's tables and built into UI5 apps by its runtime. Licensed per user, device or developer. Several vendors sell one.
- Low-code platform beside SAP
- A server or cloud tenant of its own, reaching SAP over connectors; built for citizen developers, SAP is one of many backends. General-purpose platforms and SAP's own no-code builder belong here.
Where teams choose abap2UI5
- The team is ABAP.An app is one class in ADT or SE80: debugged, checked by ATC, transported and unit-tested like any other. What developers still learn is UI5's controls, from the examples; it is not a new language.
- The system is older than RAP.NetWeaver 7.02 to 7.4x have no RAP and a Fiori stack that is expensive to add. An app written there moves to S/4HANA unchanged.
- The screen is yours, not SAP's.Tools, cockpits, monitors, admin consoles, anything that used to be a report. Where a Fiori Elements template becomes the thing you fight, this is the shorter path.
- Performance where users notice it.The browser holds one generic shell, loaded once, and every click is one plain HTTP request with the changed data only. The work runs on the ABAP stack, next to the data.
- Your Fiori apps and your logic stay.abap2UI5 apps are tiles in the same launchpad. A report, a BAPI, a function module: an app calls it as it is.
Where something else fits better
- You want the SAP standard transactional app.A list report with an object page on S/4HANA, from a released CDS model: RAP and Fiori Elements are the shorter path, and the one SAP supports.
- The app must work offline.Every click is one request to the SAP system, so the device needs a connection.
- Your guideline mandates SAP's programming model.abap2UI5 is clean core in the technical sense, but it is not RAP. The usual outcome is a scope, not a replacement.
- You want the transaction as it is, in a browser.SAP GUI for HTML and Screen Personas keep the transaction and change its look. abap2UI5 builds a new screen on the same logic. If the screen may stay, SAP's own route is shorter.
- The business should click its screens together itself.abap2UI5 is a tool for the ABAP team: an app is code, reviewed and transported as code. Where a department is to build screens without a developer, a low-code designer is the tool. What abap2UI5 offers that department is the AI App Builder, which writes a first version from a description; the review stays with a developer.
- Your rules need an SLA on paper.Support happens in the open, in Slack and on GitHub, and more can be planned with the maintainers by mail. What is not on offer is an SLA in a contract.
→ On-Stack or Side-by-Side and One App, Many Systems are the deployment scenarios in detail.
Enterprise readiness
Enterprise ready: your security, your process, your release cycle
Logon, authorizations and data stay SAP's, and the logic stays in ABAP. No part of an app runs in the browser, so there is no client logic to secure. Every rule that applies to ABAP, from code review to the four-eyes principle on transports, applies to an app unchanged.
| abap2UI5 | A low-code builder in your SAP system | |
|---|---|---|
| What an app is | An ABAP class | Entries in the tool's tables, read by its runtime |
| Where a change is made | In the development system, in the ABAP tools | Wherever the tool's designer is open, possibly production |
| How a change travels | A transport, like any class | The tool's own export, or a customizing transport |
| What happens if the tool goes away | The classes stay; they are plain ABAP in your system | The apps go with it |
- Logon is SAP'sA request that reaches an app has passed SAP logon. The framework has no user store, token or session of its own.
- Authorizations are SAP'sThe authorization on the service endpoint, and the app's own checks in its code, as a transaction does them.
- Data changes are your code'sAn app posts through the same BAPIs, function modules or RAP actions as any program, so change documents and application logs apply unchanged.
- Data stays on your systemThe app's data never leaves the SAP system. Between two clicks the framework keeps the app's state in one table on that system, deleted after four hours by default.
- Tested on every releaseEvery change is tested on NetWeaver 7.02, Standard ABAP and ABAP Cloud, and in the browser on the oldest and the newest supported UI5. A system or UI5 upgrade does not break an app.
- Security reviewed in the openA strict browser security policy, automated code scanning, a weekly dependency audit and a bill of materials (SBOM) with every release. The published security model is where a review starts.
- Clean coreReleased APIs only, passes the ABAP Cloud checks, modifies nothing in the standard.
More: request logging and accessibility
- Every request can be loggedA monitor records user, app, event, timings and errors per request. It is off until an installation switches it on.
- AccessibleViews are standard UI5 views, so every control is as accessible as UI5 makes it. A change can be announced to a screen reader, and a high-contrast theme is one switch away.
No shadow IT. Every app is a class under your existing development rules, and no click-together designer bypasses them.
→ The review pack: everything a review board asks for, each line with the place that proves it. In detail: Security, Authorization, the security model, Accessibility and Verified on.
What it costs
No license fee, now or later. The bill is your developer's time.
- No license key, no subscription, no fee per user, system or app
A low-code builder bills per user, device or developer, often with a minimum term and a setup fee. Here the line that grows with adoption is zero.
- Nothing to sign up forThe examples run in the browser without an account, and the framework is one abapGit pull.
- Free to leaveThe apps stay plain ABAP classes, and the skill your team builds is ABAP. A build renamed into your own namespace is one workflow run.
Where it runs
On the SAP system you already have, and nowhere else
The browser loads the standard UI5 library. The app, its logic and its data stay on your SAP system, with no middleware, extra server or frontend deployment.
- Every SAP operating model, from one source
ABAP Cloud clean core, released APIs only: abap2UI5 passes the checks
- SAP S/4HANA Cloud Public EditionClean core is mandatory; the same class runs, no rewrite on the way up.
- SAP BTP ABAP EnvironmentThe standalone ABAP system on BTP, also usable as the side-by-side system.
- S/4HANA Private Cloud and on-premise, in ABAP CloudThe ABAP Cloud language version on a RISE or on-premise system: abap2UI5 fits the clean-core tier there too.
Standard ABAP the classic language version, every release
- SAP S/4HANA Cloud Private EditionRISE with SAP.
- SAP S/4HANA on-premiseYour own data centre or a hoster.
- SAP ECC and NetWeaver 7.02 to 7.5xWhere RAP and a Fiori stack are out of reach, and an app written today moves to S/4HANA unchanged.
What installation takes
- Pull the package with abapGit, as for any open-source ABAP
- Create one service endpoint and put an authorization on it
- Set the four production defaults: UI5 source, error details, content security policy, endpoint authorization
No job to schedule, no extra server, no schema to migrate on upgrade.
- Two ways to deploy
- On-stackabap2UI5 on the system where the data and the logic live. An app calls BAPIs, function modules or RAP actions directly, as any program there does. The usual setup, one abapGit pull.
- Side-by-sideabap2UI5 on a separate ABAP system, the BTP ABAP Environment or a hub, and the apps reach the core over RFC or HTTP. For a core kept clean of custom UI, or one UI layer in front of several systems.
- Where an app appears
- Browser tab
- Fiori launchpad tile
- SAP Build Work Zone
- Microsoft Teams
- Microsoft Excel
- iOS & Android
- Inside your own UI5 app
- Without internet access
- A productive installation serves UI5 from the system itself, so nothing is loaded from outside (SAP Note 2943781).
→ Productive Usage, UI5 Versions and Integration.
AI
One class is the easiest thing for an AI to write and for your team to check
Your developers describe the screen, the AI writes one ABAP class, and your rules review and transport it like any other code.
- One app, one fileThe whole app is one file, so there is no service, frontend project or deployment to generate and keep in sync.
- In the tools your team usesPlugins for Claude Code and GitHub Copilot, skills for any agent, and an AI App Builder in the browser that builds an app from a description.
- Checked before anyone looksThe abap2UI5 linter tests every class the AI writes, and the AI fixes what it broke before a developer reviews it.
No AI lock-in either. Claude, ChatGPT, Copilot or a local model, with your own key.
→ Try the AI App Builder, or read Developing with AI.
Who runs it
In production, in the open, since 2023
Two companies run it in production and say so here; one offers training. Far more systems use it than the list shows.
- EmineoIn productionApps for warehouse management and production, on desktop and mobile devices
- Swiss KronoIn productionApps for warehouse management, on mobile devices
- Logali GroupTrainingWebinars and certifications for abap2UI5
- Your company hereAdd a rowRunning abap2UI5? Add your row with one short form on GitHub.
- 2,900+ systems in two weekspulled the framework from GitHub, 23 October to 5 November 2026; every abapGit pull is one clone, each system counted once
- 25+ contributorsfrom several companies, every change public
- Release 1.149November 2026; a release most months, each one listed
- Every release testedon NetWeaver 7.02, Standard ABAP and ABAP Cloud, on the oldest and the newest UI5
Talks, articles and videos
- Field Service Management Mobile Logging using abap2UI5Decabase Blog
- Fiori-type Apps built 100% with ABAPLogali Group
- Featured on SAP Developer NewsYouTube
16 more, 2023 to 2026
- Highlighted in the Boring Enterprise NerdletterYouTube
- Showcased at SAP TechEd 2023YouTube
- Part of the SAP Developer Code ChallengeSAP Community
- UI5 in ABAP Cloud (without RAP or Fiori Elements)Decabase Blog
- Webinar on Launchpad IntegrationYouTube
- Webinar on creating UI5 interfaces from ABAP using abap2UI5YouTube
- Webinar on developing UI5 apps with abap2UI5YouTube
- Featured on SAP Developer NewsYouTube
- Cust&Code Videos featuring abap2UI5YouTube
- Running abap2UI5 Backend in BrowserLinkedIn
- Highlighted in the Boring Enterprise NerdcastYouTube
- Featured on SAP Developer NewsYouTube
- Join the Advent of Code 2023 with abap2UI5SAP Community
- Highlighted in the Boring Enterprise NerdletterYouTube
- Featured on SAP Developer NewsYouTube
- See abap2UI5 on ABAP Open Source Projectsdotabap.org
→ The figures: the repository and its releases.
Get started
One real screen, one week, your own team
Decide from a screen your team built, not from a slide.
- Pick one real screenOne your team has to build this quarter, not a demo.
- Build it in a development systemWith the people who will maintain it, in the tools they use today.
- Review it like any ABAPRead the class, transport it, run the code checks, check the authorizations it asks for.
- Compare and decideHold the time and the systems it needed against any alternative or vendor quote.