HTML5 Application Repository

The repository separates where UI files are stored from what serves them:

1. A developer builds a SAPUI5 app, typically in SAP Business Application Studio, and packages it in a multitarget application.
2. At deployment, the HTML5 application deployer uploads the app's static files to a service instance of the app-host plan.
3. An application router bound to an app-runtime instance retrieves those files at runtime, authenticates the user and forwards data calls to backends through destinations.
4. SAP recommends the application router managed by SAP, which needs no runtime of its own; a self-run router is meant for advanced cases such as router extensions.

Because the files are decoupled from the router, a new app version goes live without restarting anything, and the service keeps versions and caches content. The HTML5 Application Repository is storage and delivery for UI files, not a runtime for business logic.

When a subaccount subscribes to SAP Build Work Zone, an HTML5 Apps content provider appears automatically in the Channel Manager. It reflects the apps deployed to that subaccount's repository. To show an app on a site:

1. Describe it in manifest.json: a unique app ID, a business service name (sap.cloud.service) and an inbound with semantic object and action.
2. Deploy it to the same subaccount as the SAP Build Work Zone subscription.
3. Update the HTML5 Apps content provider in the Channel Manager.
4. Add the app in the Content Explorer, then assign it to groups, catalogs and roles, and the roles to a site.

A frequent mistake is skipping step 3 and wondering why a new version is missing. The HTML5 Application Repository delivers the files, while SAP Build Work Zone decides who sees the tile.

Strengths

• Zero-downtime updates: content changes without restarting the application router.
• Serverless delivery: with the managed application router, a UI needs no running application instance.
• Sharing and versioning: public apps can be consumed by routers in other spaces, and content can be explored by version.

Where it stops

• Static content only. OData services, business logic and data live elsewhere, for example in CAP, RAP or SAP S/4HANA.
• Documented limits. SAP documents 100 MB per app-host instance and rate limits per subaccount for deployments and runtime requests.
• No personal data. Because content can be shared, SAP advises against storing personal data in it.
• Subaccount scope. Work Zone integration expects apps in the same subaccount as the subscription.

The HTML5 Application Repository answers where SAPUI5 files live on SAP BTP, not how the app behind them works.

SAP now also offers Application Frontend service, which hosts and serves frontend applications as a single entry point, with its own CLI, cockpit UI and multiple active versions. SAP positions it for new standalone, single-tenant apps that do not connect to other applications, and notes that productive use requires an SAP Build license.

SAP states that teams whose needs are met by the HTML5 Application Repository and the application router can keep using them. Apps deployed with Application Frontend service can also be added to SAP Build Work Zone, standard and advanced edition, either manually as URL apps or through a Common Data Model configuration.