Ah.. well, ok, but this is pure nonsense. First of all, the various kinds of browser local storage have always been volatile. It has always been a bad idea to

Ah.. well, ok, but this is pure nonsense. First of all, the various kinds of browser local storage have always been volatile. It has always been a bad idea to treat it as permanent storage. Maybe it's a little more obvious now? Not exactly a bad thing. > the PWAs I was building here might just be dead for iOS users If so, it was already dead for your users, whether you realized it or not. I guess you were going to implicitly promise something you could not deliver: that your PWA would keep track of the feeds the user was subscribed to (and perhaps also keep track of what had been read, and other user state). But you were going to screw your users, because a PWA without external persistent storage could not do that reliably. It's really luck for your users that this caught your attention and has you rethinking your app. A partial list of things completely external to your app (not including this change) that could cause your users to lose things important to them that you stored in various local storage... * user switches browser * user has multiple devices * user upgrades phone (or tablet, or workstation, or laptop) * phone (or other device) goes in for repair or upgrade * major change to browser (like Edge moving to chromium) * some OS updates * user clears browser data (as innumerable troubleshooting processes suggest) It's wrong to think browser-based storage used to be stable but now isn't. It never was. Browser-based storage was never going to be a good place to store your user's important, persistent data.