Beyond SAP Build

SAP Build's missing value proposition: No low-code development approach for everyone

Efficient software application development is critical in the digital business world. A detailed look at the benefits, challenges, and limitations of SAP Build and their impact on app development reveals the extent to which SAP can live up to its value proposition, particularly with regard to the low-code approach.

SAP Build promises companies a user-friendly environment in which apps can be developed without programming knowledge. The platform is based on software from Appgyver, which was acquired by SAP in 2021. It offers powerful prototyping and design tools that enable developers to quickly create interactive user interfaces. Early user involvement and continuous feedback are designed to optimize apps for an optimal user experience.

A major advantage of Build, as with any low-code platform, is that it accelerates the development of applications. To this end, the platform offers pre-built UI components and templates that make the development process more efficient. By reusing existing components, development times can be significantly reduced, resulting in faster time-to-market for applications.

Effective collaboration and communication are critical to the success of development projects. SAP Build therefore also provides features such as comments, notifications, and draft sharing to support seamless collaboration between developers, designers, and users. This enables the exchange of feedback and collaborative work on improvements to develop applications that meet user expectations.

Programming skills in demand

However, despite the advantages, there are also several challenges to using Build in the development process. While the advantages are that user-centric applications can be developed quickly and effectively, the limitations are mainly in the use of low-code development for app builders without programming skills.

In practice, it becomes apparent that this platform actually requires considerable programming knowledge. Thus, intensive familiarization with the platform through training is required, especially for users, developers and designers who are not familiar with the platform. The diverse functions and possibilities of SAP Build require appropriate training in order to exploit the full potential of the platform.

Another problem of Build is the lack of internationalization of the Wysiwyg editor. While the content of the apps created can be translated into different languages, the tool itself remains exclusively in English. This is a hurdle especially for companies in non-English speaking countries and makes it difficult to use the platform.

One of the main problems is the limited export function of SAP Build. Although the platform promises the creation of mobile apps, currently only the generation of web apps is possible. In other words, it is currently not possible to develop native iOS or Android apps directly with Build.

Exporting apps to a web application also takes an unusually long time and the announced e-mail notification upon completion is missing. The generated web apps are also not based on SAP's in-house UI5 framework, but use React Native. This creates a dependency that SAP cannot control and makes it difficult to edit and reuse the code, as Build lacks the familiar SAP Fiori design language. While integration with SAP mobile services may be possible in the future, there are currently no clear indications of this in SAP Build's documentation or roadmap.

The integration of Build into existing enterprise landscapes is also a major challenge. Although the platform is designed as a low/no-code solution, the back-end connection is complex and thus particularly affects the Citizen Developer aspect. It becomes clear that the data binding and processing that are common in the SAP environment are not for the Citizen Developer.

Knowledge about OData

To connect and display data from enterprise systems such as S/4 Hana Cloud or On-premises, specific knowledge about the OData protocol, mapping of variables and their integration into the app lifecycle is required. The mechanisms and formula editor provided go beyond the concept of low code or no code. This makes it difficult for Citizen Developers to make such connections and create complex formulas without extensive knowledge.

Seamless connection to S/4 Hana cloud or on-premises data therefore remains a challenge within the build platform. Authentication, authorization, and data source connectivity are also immature and offer limited options for professional developers. Role assignments and a comprehensive roles and rights system are also lacking.

Enterprise application scalability and performance are critical. When using Build, it is important to thoroughly review the architecture, develop efficient code, and perform real-world testing to identify and resolve bottlenecks or performance issues early.

Security and data protection

Security and data protection are other important aspects of enterprise application development. When using Build, companies must ensure that all data protection and data security requirements are met, especially when sensitive company data is processed.

One of the main disadvantages for IT teams and professional SAP developers is that building with SAP Build is not as flexible as programming in Abap, for example. Abap allows developers to implement highly complex business logic and address specific requirements. With the low-code SAP Build platform, it is difficult to implement such complex logics and request additional customizations or workarounds.

A not insignificant factor is also the acceptance within the SAP community, which is known for its powerful programming language Abap. However, various approaches in the area of low-code/no-code development have also been discussed within the community. Various collaborations and acquisitions by SAP in the near past in the area of low and no code have been pushed strongly, but have not really been convincing within the SAP community so far. The SAP community has developed a certain skepticism when it comes to low code/no code platforms.

One aspect that has caused discussion in the SAP community in this context is the cancellation of a cooperation with Microsoft and the Power Apps product. Many members of the SAP community were disappointed, as Power Apps has a large and active community. However, this cancellation also meant that other low/no-code platform vendors such as Simplifier now have the chance to win over existing SAP customers and partners by convincingly presenting the added value of their solutions for SAP-centric application development. 

It is therefore worthwhile for companies to take a look at leaner and more flexible low-code alternatives such as Simplifier with SAP users and development teams in order to match their own requirements with the capabilities and functionalities of the platforms, and ultimately find a suitable low-code technology that meets their own requirements.

Overall, it can be stated that SAP Build cannot keep its promise as a low-code development platform. There are various limitations and shortcomings for both business users and pro-code developers. The platform is not yet mature enough and does not offer a comprehensive and, above all, uniform solution approach for the development of enterprise applications. Originally, SAP Build was touted as a solution that would allow companies to create their own apps and processes without programming skills. But in practice, it turns out that this platform actually requires considerable programming skills.

Slim alternative

Simplifier is a low-code provider that is now known in the SAP world as a "lean alternative to SAP Build" and has won over many companies that have reached their limits with the SAP and BTP toolchain. With its modern technology based on the UI5 framework popular in the SAP community, the low-code platform has won over many SAP and Abap developers. The advantages of using Simplifier include the versatile standardized integration options, the most flexible UI for app use on all end devices (incl. wearables), a high degree of reusability for all created and existing content, and a lean operational concept when rolling out and using apps and mobile apps.