First look into SAP Build & SAP Build Apps – QA
It might be a bit confusing for the developers to understand what SAP Build actually is, so I would like to bring some light to the topic, based on my experiences from sessions on SAP TechEd 2022.
In this blog I would like to answer basic technical questions related to SAP Build & SAP Build Apps.
Is SAP Build related to the old Build prototyping tool for Fiori?
No, it’s not. Former build.me (SAP Build Classic) is in sunset. See an update here.
A preffered tool for SAP Fiori apps sketching is Figma.
What SAP Build actually is?
SAP Build is a set of tools combining:
- SAP Build Apps (formerly SAP AppGyver)
- SAP Build Process Automation (formerly SAP Process Automation)
- SAP Build Work Zone standard edition (formerly Launchpad Service)
- SAP Build Work Zone advanced edition (formerly WorkZone)
In general SAP Build is a low-code solution portfolio and re-branding around AppGyver, which seems to be heart of the concept. See a nice overview here.
SAP Build Apps is an evolution of AppGyver. SAP Build Apps adds additional application-building capabilities such as authentication, data integration, or lifecycle management.
Is SAP Build Apps (former AppGyver) available free-tier?
Yes, it is. See the prerequisites and subscription guide here.
Can I build UI5 prototypes with SAP Build Apps?
No, it’s not possible to create UI5 protoypes using this tool. It’s a no-code tool enabling users to create business apps without requiring programming skills.
What I can build using SAP Build Apps?
SAP Build Apps can be used to develop desktop, web-based, and mobile applications.
Can I use my old AppGyver projects in SAP Build Apps?
Yes, it is possible to reach existing AppGyver projects in a new tool. The new backend functionality works together with what was formerly called SAP AppGyver.
Can we include SAP Build Apps apps in a Launchpad Service, so they can be accessed via browser or Mobile Start?
Yes, it is possible.
Can I create my own themes for apps?
Yes, you can create your own themes via Theme Variables, so it’s ready to be consumed in the projects.
How can I consume data in my apps?
You can use OData Services and BTP Destinations or create entities using Visual Cloud Functions. Visual Cloud Functions is a persistency layer for SAP Build Apps, so think it’s a database (based on postgres db running on SAP BTP).
How can we compare SAP Build Apps with SAP Mobile Services Mobile Development Kit?
MDK is a pro-code offering, while SAP Build Apps is a no-code citizen dev tool. Both can be used to develop mobile Android and iOS applications. MDK supports offline scenarios.
Can I use offline for my OData in SAP Build Apps?
As of now offline is not supported with SAP Build Apps.
How can we distribute SAP Build Apps and handle different tenants (Development, Quality, Production)? Is there any app versioning?
Once the apps design is completed, it is needed to build the project. If you build the project as MTAR type, you can use Transport Management Service to deploy the app to different subaccounts. There’s also a history functionality available, that allows you to review previous states of the app. Release management is a built-in feature too.
Can we create roles for the apps and restrict access based on them?
It’s not yet supported. You can share your app with other stakeholders, who can work as admins, developers or viewers, but it’s not possible to restrict the access wth so-called role concept.
Is there an option to create custom components for SAP Build Apps?
Currently, you cannot create own components, but it’s in the roadmap for 2023.
How can we collaborate on the projects?
There’s a project sharing feature in the lobby, enabling real-time collaboration on SAP Build Apps projects.
SAP Build is a new brand SAP’s offering, collecting existing SAP BTP Services and bundling them together. It provides some confusion with Services renaming, but I hope this article makes things clearer.
Meanwhile, SAP Build Apps seems to be an interesting tool, becoming more and more powerful with the time. Looks like it still has some weaker points (no offline or role concept), but might become a strong development tool in the near future.