I know I'm in the minority, but I'm glad this change is happening. I simply don't trust large tech companies to keep user privacy a top priority, and in my mind, this outweighs whatever UX niceties an honest company may provide.
Private client-side-only PWAs are hard, but now Apple made them impossible
791–800 of 927 posts
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#792I know I'm in the minority, but I'm glad this change is happening. I simply don't trust large tech companies to keep user privacy a top priority, and in my mind, this outweighs whatever UX niceties an honest company may provide.
The solution could be to give that option to users; a way to mark a website or app as trusted or not. Apple's approach on the other hand really sets the web apps back, which I (as a privacy concious individual) am more comfortable using compared to apps.
If this encourages more apps to go the native route, we've done more harm than good. Apps can gather a lot more data than websites, such as the dreaded contact list access.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#793Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#794I ported Polar ( https://getpolarized.io/ ) over to a PWA about a year ago. It's kind of a nightmare due to both Google and Apple messing things up. PWAs could be an amazing platform but both companies are really messing it up. Apple is trying to kill them by giving plausible explanations as to why they can't have PWAs. Security this, blah blah blah. There's no reason they can't have PWAs work well in Safari other th…
> ... Consumers are another problem. ... You blame Apple, Google and your consumers, instead of just making native apps. Why?
As an iOS and Android developer myself, this doesn't effect me but I still think Apple and Google making things harder for PWA is bad because Apple and Google are the gate keepers for what goes on their native app stores. I can cut some slack for Google as they at least allow third party app stores but Apple doesn't.
Either Apple should stop being the gate keeper or stop making life harder for web devs.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#795Earlier quoted context omitted.
> ... Consumers are another problem. ... You blame Apple, Google and your consumers, instead of just making native apps. Why?
Yep. Just because "PWA"-geek niche at HN wants to go back to shitty UX from 2004 it doesn't mean all tech companies or consumers want to. I hope Apple keeps restricting this in the future too so that iOS app ecosystem won't turn in to a turkish fruit market full of crap like Android.
You’re getting downvoted, but I agree. Enough with shitty UX’s already!
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#796Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#797Earlier quoted context omitted.
Yeah so maybe try making a real native app instead of trying to hackaround with web sites? Apple isn't obligated to implement every single "this is now cool on web"-thing on it's platform to satisfy small niche of people who will find value in them.
Are you an Apple employee? If not, as a consumer or developer why are you not talking from the consumer's point of view? I don't want to install each and every native app. As a developer, I don't want to write and maintain completely separate native apps.
As an iOS user, I’d like you to do both!
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#798Earlier quoted context omitted.
So, make 3 apps instead of 1? This was the whole idea behind PWA.
Yes, that's the whole idea behind having different devices and operating systems with different capabilities. Why should users suffer the lowest common denominator because of lazy developers?
I wouldn't attribute it to laziness. Quality can really suffer when you need to maintain so many code bases. Not all teams have those kinds of resources.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#799Earlier quoted context omitted.
I've considered just not supporting iOS.
IMO it is completely unacceptable to have a persistent permanent non-expiring store in the browser. The potential for abuse is too high.
Then why are first-party cookies okay? FTA:
> It is not the intention of Intelligent Tracking Prevention to delete website data for first parties in web applications.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#800I ported Polar ( https://getpolarized.io/ ) over to a PWA about a year ago. It's kind of a nightmare due to both Google and Apple messing things up. PWAs could be an amazing platform but both companies are really messing it up. Apple is trying to kill them by giving plausible explanations as to why they can't have PWAs. Security this, blah blah blah. There's no reason they can't have PWAs work well in Safari other th…
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…
Well, it would have been helpful to provide a simple example of a working pwa.
The example at
https://codelabs.developers.google.com/codelabs/your-first-p...
was way too complicated as a first example, if all I wanted to know was how to make my app installable and is also broken as it uses some outdated tools. (don't remember the details)
Also, it could have been mentioned somewhere, that when you serve from localhost, you do not need SSL to install it. Knowing that, would have saved me the trouble of messing with apaches config and certificates.
So that was very frustrating as a start.
Much more helpful was a very simple hello world pwa which was barely installable. But it worked. And from there it was easy.
https://medium.com/james-johnson/a-simple-progressive-web-ap...