At SAP TechEd Berlin 2025, we had the opportunity to present “The Art and Science of SAPUI5 in SAP Build.” The deep dive session explores how SAPUI5, SAP’s strategic UI framework, is transforming user experiences and developer efficiency across SAP. This blog post shares key takeaways from the session and questions from the audience.
If you’ve missed it, watch the session recording in AD106v | The art and science of SAPUI5 in SAP Build.

The Art of SAPUI5 in SAP Fiori User Experience

SAP’s approach to user experience (UX) centers on making applications easier and more enjoyable to use, helping users accomplish their tasks with greater efficiency and satisfaction. The framework enables the SAP Fiori design system to evolve seamlessly across SAP solutions, providing flexible tools for developers to efficiently build apps using SAP Build Code.

SAP Web Components: Bridging Frameworks and Enhancing Extensibility

SAP Web Components extend the capabilities of SAPUI5, to other programming model, such as Angular, React, or Vue. This interoperability supports a consistent and streamlined UX throughout the SAP portfolio. SAP Web Components can now also be easily consumed in SAPUI5 apps just like regular controls. Going forward, SAP plans to provide new UI elements as SAP Web Components, minimizing the effort required for adopting new standards and ensuring compliance with SAP guidelines and modern Web standards.

SAPUI5 is leading is the Way in Accessibility

SAPUI5 is at the forefront of accessibility, with recent implementations (SAPUI5 1.136 and UI5 Web Components 2.9.0) aligned to the latest Web Content Accessibility Guidelines (WCAG) 2.2. This commitment ensures that applications built with SAPUI5 are inclusive and accessible to users worldwide, meeting diverse needs and regulatory requirements.

The Science of SAPUI5 in SAP Build

SAP Build is SAP’s unified solution to build apps and extensions, automations, agents and digital workspaces. SAP Build helps to increase developer productivity and to future-proof IT investments by leveraging proven technologies like SAPUI5, SAP Fiori elements, CAP and ABAP Cloud.

Extending SAP standard apps with SAPUI5 flexibility and Clean Core

SAPUI5 flexibility enables upgrade-safe, clean core extensions with intuitive low-code/no-code tools for different personas: end users, key users, and developers. New capabilities include consistent text changes for field labels and a “What’s New” / “UI Adaptation Tour” for key users. Developers creating adaptation projects benefit from a “Replace original tile option and coding efficiency with TypeScript and Joule.

The new SAPUI5 runtime repository accelerates patch updates, improves startup performance, and supports zero-downtime deployments.

Future-Proofing apps with UI5 best practices and UI5 linter

Technical debt and legacy code can slow down innovation within SAP Fiori projects. Here the UI5 linter helps finding and fixing the usage of deprecated APIs and making your code is ready for upcoming SAPUI5 versions. The new SAPUI5 / OpenUI5 legacy-free version helps validating how compliant your code is to UI5 best practices, i.e. ensuring your code is state of the art and future-proof.

AI-Powered Development: Joule Copilot and MCP server

AI is revolutionizing SAPUI5 development. The Joule copilot accelerates app creation, view and control addition, code formatting, migration to TypeScript and much more. The UI5 MCP server enables agentic AI app development in SAP Build, combining generative AI with algorithmic logic if the UI5 linter.

Key Takeaways

SAPUI5 delivers a streamlined, consistent UX across SAP Business Suite, driving both user satisfaction and business outcomes.SAP Build and SAPUI5 flexibility empower organizations to extend SAP standard apps efficiently, future-proofing their investments.AI-powered tools accelerate development and let you future-proof your apps with UI5 best practices.

Selected questions from the audience

Q: Is Using VS code still recommended or the SAP Build for development

A:  In addition to the turnkey solution of SAP Build running on SAP BTP, SAP plans to focus on releasing development tools on the VS Code marketplace. VS Code is the number-one IDE worldwide, especially among web, cloud, and full-stack developers. Investing more in VS Code helps SAP meet developers where they are, making it easier for new developers to adopt SAP technologies (such as CAP, SAP BTP, SAPUI5, ABAP Cloud).

Q: New controls will be components from now on?

A: Exactly, SAP plans to deliver most new UI components as Web Components, which can be use across any Web framework, including SAPUI5.

Q: How AI compatibilities work in more complex application

A: Beyond Generative AI capabilities, agentic development tool (e.g. with the UI5 MCP server) offer impressive results for developing complex (fullstack) apps, from design up to deployment. You might want to check out Inside Joule: Lessons from building an AI coding assistant for SAP Build for an inside view.

Q: What is the benefit of using the Web Components from the example compared to sap.m.Input?

A: Please continue using SAPUI5 controls if they fulfil your needs. There is no change to that. Most upcoming, new UI elements will be provided as Web Component, serving *all* technology stacks, including SAPUI5.

Q: What are Components bringing when compared to Classic controls if we are using UI5 only approach

A: see above

Q: how will be the future scope of Fiori elements applications over ui5, do both will have same scope

A: SAP Fiori elements is an option to develop SAPUI5 app more efficiently. SAP recommends using as much SAP Fiori elements as possible and as much freestyle SAPUI5 as needed. This is what we do in SAP as well. Check out the SAP Fiori Development Portal on more details.

Q: What would be best approach to extend freestyle standard Fiori apps? Also, will adaptation projects have more extension powers?

A: SAPUI5 flexibility to the strategic way to extend/adapt SAPUI5 apps. The UI5 team continues to invest a lot in this area, as it is top priority for many partners/customers. SAPUI5 flexibility covers freestyle SAPUI5 as well as apps built with SAP Fiori elements. Adaptation projects offer best capabilities to create future-proof app extensions.

Q: Will the Build Code Joule CoPilot also support the Vibe Coding with MCP in the future?

A: Yes, SAP plans for vibe coding tools (incl. MCP servers) in SAP Build to empower business users to create application prototypes and start new SAP solutions without heavy coding knowledge.

Q: SAP develops SAPUI5 while promoting low-code tools like RAP, CAP, and key user adaptations. Isn’t it inconsistent to advance the core framework while encouraging less direct UI5 development?

A: Key user adaptation as well as metadata- / annotation-driven apps on RAP/CAP (using SAP Fiori elements) all use SAPUI5 as their UI technology. Innovations ‘in the UI’ are built in SAPUI5, benefitting all these models. Also, there remains a strong use case for a freestyle SAPUI5 implementation approach for apps which cannot follow the patterns of SAP Fiori elements.

Q: As a partner, if we build an SAPUI5 application and deploy it to customer systems, can SAPUI5 flexibility be used to create customer specific adaption projects for it?

A: This is planned for Q4/2025: Developer adaptation: enabling customer and partner applications for adaptation projects (As always with forward-looking statements, this is subject to change.)

Q: The build errors just prove you are really building live and not faking it. 🙂

A: Right. Not sure though whether Tommy enjoyed the moment 😉

Q: Now that CDS support UI annotations will UI5 become obsolete?

A: Definitely not. SAPUI5 remains SAP’s strategic UI framework. SAP Fiori elements with its annotations is built on SAPUI5. The annotations control what SAPUI5 is showing.

​ At SAP TechEd Berlin 2025, we had the opportunity to present “The Art and Science of SAPUI5 in SAP Build.” The deep dive session explores how SAPUI5, SAP’s strategic UI framework, is transforming user experiences and developer efficiency across SAP. This blog post shares key takeaways from the session and questions from the audience.If you’ve missed it, watch the session recording in AD106v | The art and science of SAPUI5 in SAP Build.The Art of SAPUI5 in SAP Fiori User ExperienceSAP’s approach to user experience (UX) centers on making applications easier and more enjoyable to use, helping users accomplish their tasks with greater efficiency and satisfaction. The framework enables the SAP Fiori design system to evolve seamlessly across SAP solutions, providing flexible tools for developers to efficiently build apps using SAP Build Code.SAP Web Components: Bridging Frameworks and Enhancing ExtensibilitySAP Web Components extend the capabilities of SAPUI5, to other programming model, such as Angular, React, or Vue. This interoperability supports a consistent and streamlined UX throughout the SAP portfolio. SAP Web Components can now also be easily consumed in SAPUI5 apps just like regular controls. Going forward, SAP plans to provide new UI elements as SAP Web Components, minimizing the effort required for adopting new standards and ensuring compliance with SAP guidelines and modern Web standards.SAPUI5 is leading is the Way in AccessibilitySAPUI5 is at the forefront of accessibility, with recent implementations (SAPUI5 1.136 and UI5 Web Components 2.9.0) aligned to the latest Web Content Accessibility Guidelines (WCAG) 2.2. This commitment ensures that applications built with SAPUI5 are inclusive and accessible to users worldwide, meeting diverse needs and regulatory requirements.The Science of SAPUI5 in SAP BuildSAP Build is SAP’s unified solution to build apps and extensions, automations, agents and digital workspaces. SAP Build helps to increase developer productivity and to future-proof IT investments by leveraging proven technologies like SAPUI5, SAP Fiori elements, CAP and ABAP Cloud.Extending SAP standard apps with SAPUI5 flexibility and Clean CoreSAPUI5 flexibility enables upgrade-safe, clean core extensions with intuitive low-code/no-code tools for different personas: end users, key users, and developers. New capabilities include consistent text changes for field labels and a “What’s New” / “UI Adaptation Tour” for key users. Developers creating adaptation projects benefit from a “Replace original tile option and coding efficiency with TypeScript and Joule.The new SAPUI5 runtime repository accelerates patch updates, improves startup performance, and supports zero-downtime deployments.Future-Proofing apps with UI5 best practices and UI5 linterTechnical debt and legacy code can slow down innovation within SAP Fiori projects. Here the UI5 linter helps finding and fixing the usage of deprecated APIs and making your code is ready for upcoming SAPUI5 versions. The new SAPUI5 / OpenUI5 legacy-free version helps validating how compliant your code is to UI5 best practices, i.e. ensuring your code is state of the art and future-proof.AI-Powered Development: Joule Copilot and MCP server AI is revolutionizing SAPUI5 development. The Joule copilot accelerates app creation, view and control addition, code formatting, migration to TypeScript and much more. The UI5 MCP server enables agentic AI app development in SAP Build, combining generative AI with algorithmic logic if the UI5 linter.Key TakeawaysSAPUI5 delivers a streamlined, consistent UX across SAP Business Suite, driving both user satisfaction and business outcomes.SAP Build and SAPUI5 flexibility empower organizations to extend SAP standard apps efficiently, future-proofing their investments.AI-powered tools accelerate development and let you future-proof your apps with UI5 best practices. Selected questions from the audienceQ: Is Using VS code still recommended or the SAP Build for developmentA:  In addition to the turnkey solution of SAP Build running on SAP BTP, SAP plans to focus on releasing development tools on the VS Code marketplace. VS Code is the number-one IDE worldwide, especially among web, cloud, and full-stack developers. Investing more in VS Code helps SAP meet developers where they are, making it easier for new developers to adopt SAP technologies (such as CAP, SAP BTP, SAPUI5, ABAP Cloud).Q: New controls will be components from now on?A: Exactly, SAP plans to deliver most new UI components as Web Components, which can be use across any Web framework, including SAPUI5.Q: How AI compatibilities work in more complex applicationA: Beyond Generative AI capabilities, agentic development tool (e.g. with the UI5 MCP server) offer impressive results for developing complex (fullstack) apps, from design up to deployment. You might want to check out Inside Joule: Lessons from building an AI coding assistant for SAP Build for an inside view.Q: What is the benefit of using the Web Components from the example compared to sap.m.Input?A: Please continue using SAPUI5 controls if they fulfil your needs. There is no change to that. Most upcoming, new UI elements will be provided as Web Component, serving *all* technology stacks, including SAPUI5.Q: What are Components bringing when compared to Classic controls if we are using UI5 only approachA: see aboveQ: how will be the future scope of Fiori elements applications over ui5, do both will have same scopeA: SAP Fiori elements is an option to develop SAPUI5 app more efficiently. SAP recommends using as much SAP Fiori elements as possible and as much freestyle SAPUI5 as needed. This is what we do in SAP as well. Check out the SAP Fiori Development Portal on more details.Q: What would be best approach to extend freestyle standard Fiori apps? Also, will adaptation projects have more extension powers?A: SAPUI5 flexibility to the strategic way to extend/adapt SAPUI5 apps. The UI5 team continues to invest a lot in this area, as it is top priority for many partners/customers. SAPUI5 flexibility covers freestyle SAPUI5 as well as apps built with SAP Fiori elements. Adaptation projects offer best capabilities to create future-proof app extensions.Q: Will the Build Code Joule CoPilot also support the Vibe Coding with MCP in the future?A: Yes, SAP plans for vibe coding tools (incl. MCP servers) in SAP Build to empower business users to create application prototypes and start new SAP solutions without heavy coding knowledge.Q: SAP develops SAPUI5 while promoting low-code tools like RAP, CAP, and key user adaptations. Isn’t it inconsistent to advance the core framework while encouraging less direct UI5 development?A: Key user adaptation as well as metadata- / annotation-driven apps on RAP/CAP (using SAP Fiori elements) all use SAPUI5 as their UI technology. Innovations ‘in the UI’ are built in SAPUI5, benefitting all these models. Also, there remains a strong use case for a freestyle SAPUI5 implementation approach for apps which cannot follow the patterns of SAP Fiori elements.Q: As a partner, if we build an SAPUI5 application and deploy it to customer systems, can SAPUI5 flexibility be used to create customer specific adaption projects for it?A: This is planned for Q4/2025: Developer adaptation: enabling customer and partner applications for adaptation projects (As always with forward-looking statements, this is subject to change.)Q: The build errors just prove you are really building live and not faking it. 🙂A: Right. Not sure though whether Tommy enjoyed the moment 😉Q: Now that CDS support UI annotations will UI5 become obsolete?A: Definitely not. SAPUI5 remains SAP’s strategic UI framework. SAP Fiori elements with its annotations is built on SAPUI5. The annotations control what SAPUI5 is showing.   Read More Technology Blog Posts by SAP articles 

#SAP

#SAPTechnologyblog