Earlier quoted context omitted.
Is Twitter really a PWA or just a nicely done responsive website? At this point the boundary is a unclear. Beside Twitter rely on server side storage and pretty much only store session token in the PWA "local storage" (largely speaking). And as a user I rather installed iOS native App to keep finer grained control on permissions. (I also use multi accounts not sure the PWA Handel that?)
This highlights a longstanding issue of PWA definition and how to position it against modern web practices and features. What is a PWA? Why is it even a thing?
Private client-side-only PWAs are hard, but now Apple made them impossible
861–870 of 927 posts
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#862I remember when Edge/IE was crap, I put up a couple of banners that Firefox/Chrome/Safari are officially supported browsers and people did move away from Edge. Had <1% of traffic from there.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#863Gaia is one example: https://github.com/blockstack/gaia (I've worked on Gaia so I'm biased but there are other such decentralized options as well.)
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#864This is really in response to the irresponsible use of APIs for trackers. Evercookie is a stunning example of how far it can go... From their repo: - Standard HTTP Cookies - Flash Local Shared Objects - Silverlight Isolated Storage - CSS History Knocking - Storing cookies in HTTP ETags (Backend server required) - Storing cookies in Web cache (Backend server required) - HTTP Strict Transport Security (HSTS) Pinning (w…
“... abusing over a dozen technologies...” is this a proof-of-concept or a real thing ? It just seems too horrendous to be real. I think your comment really hits the nail on the head, IMHO the frustration shouldn’t be directed toward Apple but more toward the groups who have pushed the tracking practice so far to necessitate such draconian measures.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#865The source clarifies that this only applies to websites run within the Safari browser.[1] PWAs added to the home screen aren't affected. > As mentioned, the seven-day cap on script-writable storage is gated on "after seven days of Safari use without user interaction on the site." That is the case in Safari. Web applications added to the home screen are not part of Safari and thus have their own counter of days of use…
Ok but OTOH Apple is not helping PWAs by hiding the "Add to home screen" in submenus and not having an official API to show a banner like Chrome has on Android. Edit: Also what about desktop?
From Apple's standpoint, when you put yourself on the user's homescreen, that is a deep connection between that app and the user. Apple spends billions in each finding new ways to enhance and enrich that connection. IMO, their _belief_ is that building a native app to take advantage of all these rich and engaging ways is the best way to build deep connections with your (developer's) users.
Being an icon on the user's home screen is where deep connection begins, not ends. You might add a today widget, you might want to send notifications, you might want to add AR experiences. You might want a Tablet experience and allow hand off between these devices. Apple is invested in becoming a deep level of importance in a user's life. They want to share as large of surface area with 3rd party developers as they can. It would be irresponsible to promote an API that made developers have to start from scratch when they decide they want to go deeper.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#866Earlier quoted context omitted.
Hi there, I'm the product manager for PWAs on the Chrome team. Very interested in hearing about pain points you've had building out PWAs, especially if there's features you were keen on that haven't been released. Easiest way to reach me is on Twitter: https://twitter.com/b1tr0t Fully agree with you that docs are all over the place. We've started to consolidate docs under web.dev, and the PWA section launched recentl…
Please consider contributing to MDN. It's the best source for web development and it would be great to keep everything there, properly cross-referenced, etc.
Blog post of the announcement: https://blog.chromium.org/2017/10/building-unified-documenta...
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#867Earlier quoted context omitted.
Heh, you're asking a googler who's basically responsible for some of the actions Google is taking with Chrome, trying to make the web only browseable via Chrome and centralizing information under their own Google brand, to contribute to a cross-company/community effort (Mozilla + Microsoft + open source hackers)? While noble, I can only wish you good luck. I think the sail has long sailed for asking Chrome/Google to…
Just want to note that you specifically mentioned Microsoft working with open source hackers in this comment saying that the ship has long since sailed on Chrome/Google contributing to the open web. I don't know, never say never I guess. I'm certainly not going to defend Google's track record on openness and privacy -- there have been, under even the most generous of interpretations, huge missteps, and I don't think…
Color me surprised when I discovered that also Google is mentioned there! Here is the announcement: https://blog.mozilla.org/blog/2017/10/18/mozilla-brings-micr...
Reading that announcement makes b1tr0t's statement "We've started to consolidate docs under web.dev" even worse, as they previously said they are gonna contribute to MDN, but now they have turned and use their own shit anyways.
Screw you Google.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#868Earlier quoted context omitted.
Please consider contributing to MDN. It's the best source for web development and it would be great to keep everything there, properly cross-referenced, etc.
Don't they already do that? They are part of the MDN Product Advisory Board since 2017. Blog post of the announcement: https://blog.chromium.org/2017/10/building-unified-documenta...
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#869I 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'…
CouchDB and Amplify Datastore do delta syncs, should this get around the problem? 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
#870The source clarifies that this only applies to websites run within the Safari browser.[1] PWAs added to the home screen aren't affected. > As mentioned, the seven-day cap on script-writable storage is gated on "after seven days of Safari use without user interaction on the site." That is the case in Safari. Web applications added to the home screen are not part of Safari and thus have their own counter of days of use…
I don't think that's actually what it clarifies. Or at the very least it's very confusing. > have their own counter of days of use. Their days of use will match actual use of the web application which resets the timer. This makes it sound very much like homescreen apps will have their data wiped after 7 days of non-use. > We do not expect the first-party in such a web application to have its website data deleted. And…
Data isn’t deleted after 7 days for home screen web apps.