Offer offline functionality or, alternatively, provide an official way to influence requests.
@jnsttl is already working on this.
Since Feb 18, 2026.
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Why are you proposing this feature?
Browsers are gaining more and more native functions and can provide applications as PWAs. UI5 should also offer options to cover the connectivity aspect here. Especially in the area of keeping data local and synchronising it at a later point in time.
There is already a community extension for the PWA aspect: https://www.npmjs.com/package/ui5-task-pwa-enabler
How should a possible solution look like?
Ideally, there would be a native implementation based on localStorage and/or IndexedDB.
This would store data locally and synchronise it when connectivity is available or through manual action.
Alternatively, an official option to influence the sending and receiving of requests to the backend would be helpful.
In our company, for example, we have developed an extension that can keep the data local. Unfortunately, this is no longer functional with the latest revision of the oData v4 model. For example, we have hooked into sap/ui/model/odata/v4/lib/_Requestor, overwritten the send methods, and made this available as an extension for Freestyle and Fiori Elements apps.
Are there alternative approaches?
No response
Any further information you would like to share?
The function was also discussed at the Fiori Roundtable on 25 October.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.