In late 2023, we introduced OpenUI5 2.x with a clear goal: renew the UI5 framework by removing deprecated libraries and functionality, making it leaner, faster, and future-proof. Since then, the UI5 team has made significant progress towards this legacy-free vision — from cleaning up the core to providing tooling that helps you modernize your applications. This post is an update on where we stand with SAPUI5 / OpenUI5 2.x and what it means for you.
SAPUI5 / OpenUI5 2.x delivery is on hold
UI5 2.x is currently on hold from a delivery perspective. The technical work is largely done. We have cleaned up the framework, removed synchronous APIs, eliminated globals, and followed internally the same rules we ask you to follow externally. The migration tooling achieves a very high percentage of automatic conversion rates for application code. From a pure readiness standpoint, we could ship.
However, the rapid evolution of AI has fundamentally changed the questions we need to answer. What does the future programming model look like for an AI-native user experience? How should application design evolve? How do we best address the challenges and opportunities that AI brings to UI development? UI5 2.x is legacy-free, and that has clear advantages — but it is not fundamentally different from the current stack. From an AI perspective, it would not solve additional problems compared to what UI5 1.x already provides today. If we want to bring something genuinely new, addressing different problems, we likely need to do more than what version 2.x set out to do.
We have therefore decided to put the delivery on hold and use this opportunity to explore how the UI5 framework can be positioned to play a best-in-class role in an AI-driven environment.
SAPUI5 remains SAP’s strategic UI technology for building applications. We want to make sure it continues to play a key role in the AI age.
The foundational work pays off
While the delivery of SAPUI5 2.x as a separate version is on hold, the foundational work we have done is far from wasted — it is already paying off today.
Legacy-free cleanup across the stack. We have cleaned up the UI5 core, synchronous module loading (to the extent possible in a compatible way) and globals, and deprecating non-compliant APIs. The basic UI5 libraries are legacy-free, the SAP Fiori launchpad provides a new sandbox with async services, and the SAP Fiori elements cleanup is underway.
UI5 linter. With a single command, you get an audit of your application that that tells you what needs to be corrected to comply with UI5 best practices. The linter also includes an autofix capability for deterministic fixes.
UI5 Modernization AI skills. What the linter cannot fix automatically, AI takes further. The UI5 Modernization Plugin for coding agents (e.g. for Claude Code or GitHub Copilot) run the linter, scan for solutions, and execute code changes to clean up your codebase. Together with the UI5 Linter autofix option, this achieves a very high percentage of automated migrations to legacy-free best practices. While manual testing is still required, we continue to close the remaining gaps.
These tools and the cleaned-up codebase benefit you regardless of how the UI5 versioning evolves. Following UI5 best practices — TypeScript first, asynchronous loading, no globals — makes your applications better, future-proof and ready for what comes next.
What you should do
The message is clear: keep modernizing your applications. The foundational work towards legacy-free is valuable today and will carry forward.
Follow UI5 best practices: TypeScript first, asynchronous loading, no globals, no deprecated APIs.
Use the UI5 linter to audit your applications against UI5 best practices.
Use the UI5 Modernization Plugin with your coding agent to automate the migration to best-practice-compliant code.
Everything you do to modernize your applications today benefits you now — cleaner code, better performance, improved security, easier updates — and prepares you for the future.
Stay informed
This blog post is the official communication channel for updates on SAPUI5 / OpenUI5 2.x. When there is news to share, the UI5 team will add updates here. Subscribing to this blog post is sufficient to stay informed.
In late 2023, we introduced OpenUI5 2.x with a clear goal: renew the UI5 framework by removing deprecated libraries and functionality, making it leaner, faster, and future-proof. Since then, the UI5 team has made significant progress towards this legacy-free vision — from cleaning up the core to providing tooling that helps you modernize your applications. This post is an update on where we stand with SAPUI5 / OpenUI5 2.x and what it means for you. SAPUI5 / OpenUI5 2.x delivery is on holdUI5 2.x is currently on hold from a delivery perspective. The technical work is largely done. We have cleaned up the framework, removed synchronous APIs, eliminated globals, and followed internally the same rules we ask you to follow externally. The migration tooling achieves a very high percentage of automatic conversion rates for application code. From a pure readiness standpoint, we could ship.However, the rapid evolution of AI has fundamentally changed the questions we need to answer. What does the future programming model look like for an AI-native user experience? How should application design evolve? How do we best address the challenges and opportunities that AI brings to UI development? UI5 2.x is legacy-free, and that has clear advantages — but it is not fundamentally different from the current stack. From an AI perspective, it would not solve additional problems compared to what UI5 1.x already provides today. If we want to bring something genuinely new, addressing different problems, we likely need to do more than what version 2.x set out to do.We have therefore decided to put the delivery on hold and use this opportunity to explore how the UI5 framework can be positioned to play a best-in-class role in an AI-driven environment.SAPUI5 remains SAP’s strategic UI technology for building applications. We want to make sure it continues to play a key role in the AI age.The foundational work pays offWhile the delivery of SAPUI5 2.x as a separate version is on hold, the foundational work we have done is far from wasted — it is already paying off today.Legacy-free cleanup across the stack. We have cleaned up the UI5 core, synchronous module loading (to the extent possible in a compatible way) and globals, and deprecating non-compliant APIs. The basic UI5 libraries are legacy-free, the SAP Fiori launchpad provides a new sandbox with async services, and the SAP Fiori elements cleanup is underway.UI5 linter. With a single command, you get an audit of your application that that tells you what needs to be corrected to comply with UI5 best practices. The linter also includes an autofix capability for deterministic fixes.UI5 Modernization AI skills. What the linter cannot fix automatically, AI takes further. The UI5 Modernization Plugin for coding agents (e.g. for Claude Code or GitHub Copilot) run the linter, scan for solutions, and execute code changes to clean up your codebase. Together with the UI5 Linter autofix option, this achieves a very high percentage of automated migrations to legacy-free best practices. While manual testing is still required, we continue to close the remaining gaps.These tools and the cleaned-up codebase benefit you regardless of how the UI5 versioning evolves. Following UI5 best practices — TypeScript first, asynchronous loading, no globals — makes your applications better, future-proof and ready for what comes next.What you should doThe message is clear: keep modernizing your applications. The foundational work towards legacy-free is valuable today and will carry forward.Follow UI5 best practices: TypeScript first, asynchronous loading, no globals, no deprecated APIs.Use the UI5 linter to audit your applications against UI5 best practices.Use the UI5 Modernization Plugin with your coding agent to automate the migration to best-practice-compliant code.Everything you do to modernize your applications today benefits you now — cleaner code, better performance, improved security, easier updates — and prepares you for the future.Stay informedThis blog post is the official communication channel for updates on SAPUI5 / OpenUI5 2.x. When there is news to share, the UI5 team will add updates here. Subscribing to this blog post is sufficient to stay informed. Read More Technology Blog Posts by SAP articles
