zlacker

What if you store the data in a back-end, just like native mobile apps?

>>pprota+(OP)
Many (most?) native apps also have a local store which is essential to how they function. Having to rely on stable internet for your app to work is annoying for lots of types of apps.

>>pprota+(OP)
Somebody has to pay for that backend, making it hard to build free apps.

It also impacts the UX of the app with more complex caching or having to load things over the network as you use it.

>>martin+p5
I'm excited because if Nostr for this reason: it can be used as a general storage for small data.

It's not good for storing media, but for other things it can be used as a backup and communication tool for web apps.

>>mtomwe+F
Do you really believe most apps rely on local storage? What if I remove the app from my phone and reinstall it later? All my data is gone?

I am pretty sure most apps use AT LEAST iCloud to store data

>>mtomwe+F
Example?

>>pprota+T41
Oh come on, relying on local storage is not the same as not having a backup.

Modern web apps can cache all the files they need to function. They can work offline. So when iOS deletes a web app's data, it doesn't just delete some content and maybe a few settings. It's basically like it deletes the entire app and you have to reinstall it (by opening the web app and re-download all assets that make it work). Sure, the icon is still on your home screen, but the entire app behind it is gone.

It'll also delete things like your login status/tokens/etc, so you have to log in again, maybe the web app has settings that it doesn't want to sync across devices, etc.

I assume that when Web Push hits iOS, notifications will only work as long as you open the web app often enough.

>>intras+0k1
Any app you install downloads megabytes worth of code, assets, etc. That's all local storage.

>>rejhga+6t1
Oh okay I didn’t realize we were talking about the actual application code being stored in local data. I thought they meant stuff like user data or application state, which is often handled by the back-end instead of client-side. Makes sense now, and I can see how removing that ability from webapps makes offline functionality impossible.

>>rejhga+st1
And your browser will cache those assets. I, for one, prefer that approach. And I can clear my cache when I want.