Private client-side-only PWAs are hard, but now Apple made them impossible
1–10 of 927 posts
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#2[deleted]
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#3As the article explains, Offline Web App is being used to mean Progressive Web Application (the standard terminology).
(edit Turns out that's not quite right, see diggan's reply.)
From the article:
> You’d almost think they had an App Store to promote or something.
There's certainly a tension here. I'm still not sure why more vendors don't make iOS PWAs to get around the App Store payment rules.
Perhaps related: Very roughly a year ago, something changed in iOS that broke the 2048 PWA. Its swipe-detection no longer works. A pity.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#4Better title: Apple restricts tracking by limiting browser storage, which hurts my particular app.
Browsers need to be severely limited due to them running arbitrary code from the web. Doesn't matter if it's an offline web app. If you want more access, make a native app (with or without web technologies).
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#5I really appreciate this link. I would have never seen this otherwise. It's kind of a disappointment for us on the enterprise side. Our main offering is an offline app where people are disconnected from the internet for weeks and we use localStorage to validate who they are. It's a bit vague about how this affects apps that don't use safari. Nevertheless, we might have to start to really think about the user experience here now that this update is out.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#6I would be OK with 7 days being the default with a permission model where I can grant a website longer storage time.
Actually, I'd be even happier if any form of offline storage required explicit user permission anyway.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#7I have an app which isn't offline, but I wanted to make use of IndexedDB and LocalStorage to make things faster for users. Now I wonder if it's worth the effort to even try. I think this pretty much kills the utility of all local storage initiatives.
My app is an inventory control system used by businesses that build electronics (https://partsbox.com/). Deleting client-side data after 7 days is ridiculous. You can't assume that people will always log in every week, in small businesses or design/manufacturing companies there are times when 2-3 weeks can pass without building new hardware or touching inventory.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#8This is terrible...
I have a copy of my “DAT Shopping List” demo I last opened about 6 months ago saved to my iPhone home screen... I opened it, and the data was still there. I’ll be really sad when I open it again after iOS autoupdates and the data will be nuked.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#9>deleting all local storage (including Indexed DB, etc.) after 7 days
Evil company. How do we fix this? Shame users?
The problem is that the users are so brainwashed from decades of Marketing.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#10Better title: Apple restricts tracking by limiting browser storage, which hurts my particular app. Browsers need to be severely limited due to them running arbitrary code from the web. Doesn't matter if it's an offline web app. If you want more access, make a native app (with or without web technologies).
> If you want more access
which is somewhat ironic, because the goal of a web app is to break free of the walled garden and become OS-independant.