We have a large, enterprise app that is currently deployed as an APK. It uses on-device storage to read and write data while the user is offline in remote locations, and then the user uploads the data collected when they reconnect to the internet again. If we deployed our app as a web app, would the data still be written to an on-device storage location? How will our app’s offline-capable flows behave?
1 Like
I would assume it would be stored to local memory based on browser settings. Im sure you could add a toast message to display the location when the data is displayed to test this. Below is a video that may help, but doesnt cover this exaclty.
Did you try it out? And if so, what is your experience? I have the same issue.
I’d be grateful if you would let me know if you have any relevant information.
Thanks!
lol, it would be too easy oif things just worked, wouldn´t it 
This relates to an older post, are these problems still existing?
I wonder where the data are kept and if they will be accessible continuously. What if you have a browser update, or a system clean up, will all data be deleted?
Exactly why I was asking, I am wondering the same thing how it will behave.
Hi guys,
For WEB APPs during preview and also upon deployed,
you can view & access the On-Device Storage data and also the Set/Get Item to Storage data in the browser developer tools.
Go to ‘Application’ tab then ‘Local Storage’.
From the attached screenshot,
- Blue dash square shows the ‘On-Device Storage’ records.
- and Red dash squares shows ‘Set/Get Item to Storage’ records.
Hence, data will be deleted once the browser data was cleared or the browser uninstalled.
Please refer to local storage documentation here: Window: localStorage property - Web APIs | MDN
A browser localStorage persists even when the browser is closed and reopened. Stores data with no expiration date , and gets cleared only through JavaScript, or clearing the Browser cache / Locally Stored Data.
My understanding is that Device LocalStorage interface from Appgyver is local storage abstraction across all supported devices (including a web device);
Thus, in case a device is a web browser, it is, most likely, merely a wrapper over the Web Storage API here: Using the Web Storage API - Web APIs | MDN and an example here: Using the Web Storage API - Web APIs | MDN
Appgyver also provides Firebase storage interface as described here: Firebase storage. Thus you may want to consider using a Firebase persistency for periodic backups of the local storage content. That’s pretty much what you would be doing anyway with an app running on a physical device…
I hope that helps…
PS. From the AG marketplace:
