Earlier quoted context omitted.
> 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.
No way that's happening on iOS as long as Apple takes 30% off the top
Private client-side-only PWAs are hard, but now Apple made them impossible
31–40 of 927 posts
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#32Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#33Earlier 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.
Yea, we actually don't use safari at all in our app. So this might not have an effect but it's pretty vague.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#34As 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: Ver…
> I'm still not sure why more vendors don't make iOS PWAs to get around the App Store payment rules. Because users won't use them. For users that don't have a technical background: if it isn't in the app store then it essentially isn't an app. For techie users: lots of us don't want web apps because of the power, memory, and bandwidth usage is often higher than a well written native app. The fact that there's a gatek…
I'm not convinced of this. If it has an icon like proper apps, and feels like an app, I don't think users are going to mind if it came from the App Store.
The question is whether the unfamiliar 'installation' process is too fiddly for non-technical users. I don't think it is. I figure a 10 second How to install our app animation would do the job.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#35Better 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
#36I 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'…
If you put data in IDB, it will stay there for 7 days and then if it gets deleted the delta sync would just download it again.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#37I 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 experien…
Edit: getting downvoted without any reasoning provided, so I assume I'm incorrect, there are more/less ways of storing data in the future for Safari users?
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#38Safari already was lagging behind Chrome, Chrome forks and Firefox in a lot of feature adoption. This will only make it more of a "new Internet Explorer", a browser that sites recommend you NOT to use.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#39Better 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.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#40>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.
> The problem is that the users are so brainwashed from decades of Marketing. Is there any other device or ecosystem of devices where my parents can fix their problems by turning it off and on? The fact that I have 80 years old grandparents who can’t read English using iPads and iPhones is not just marketing, that’s “not having to google and download malware bytes and ccleaner and go into regedit” to maybe fix issues…
I've had to aid my parents using Apple devices just as much as Android (father likes iPhone, mother prefers Samsung Galaxy).
edit: so much for anecdotes...