Private client-side-only PWAs are hard, but now Apple made them impossible

Post by diegoperini » Wed, Mar 25, 2020, 1:58 PM UTC

vbezhenar wrote: post #42

yohannparis wrote: post #14

Earlier quoted context omitted.

Webkit's website says: "[..] deleting all of a website’s script-writable storage after seven days of Safari use without user interaction on the site." It is not clear that a user coming to your website before the 7 days, even offline, is exempt of it.

User not coming to website 7 days can't be invalid use-case. Losing important data simply because someone went on vacation is unacceptable.

Post by IggleSniggle » Wed, Mar 25, 2020, 2:00 PM UTC

megous wrote: post #80

arghwhat wrote: post #4

Better 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, make a native app (with or without web technologies). How's installing a native app better for a random user privacy or security wise, exactly?

Post by kkarakk » Wed, Mar 25, 2020, 2:00 PM UTC

JumpCrisscross wrote: post #99

codesections wrote: post #30

Earlier quoted context omitted.

> Apple restricts tracking by limiting browser storage But the argument that this will protect privacy in the first place seems really weak. Before this change in Apple's policy, an app could store my config data on my PC. After this change, they'd need to have me log in and send the config data to their servers. That seems like I've lost privacy, not gained it.

> they'd need to have me log in and send the config data to their servers You'd have to log in. That's a hurdle that involves implicit consent.

Post by coffeefirst » Wed, Mar 25, 2020, 2:03 PM UTC

Post by _0w8t » Wed, Mar 25, 2020, 2:04 PM UTC

cageface wrote: post #89

robenkleene wrote: post #60

I’m guessing that Apple will start hindering web apps because the new mouse support in iPadOS is going to be such a boon to web apps. Because of sandboxing, web apps are the only cross-platform apps that can run in their full versions on iPadOS. I wrote a quick summary of the situation[0]. Therefore, since native apps are more of a platform differentiator than web apps, moving forward we can expect Apple to start sys…

moving forward we can expect Apple to start systemically hindering web apps They have been doing this for quite some time now. Always ostensibly to protect users but always also conveniently putting webapps at a permanent disadvantage to native apps. For my part I'm not interested in being a user of a platform so hostile to the web that it disallows any third party browsers.