Why 7 days though? Why not 30 or 3? What are Apple basing this number on?
Private client-side-only PWAs are hard, but now Apple made them impossible
681–690 of 927 posts
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#682Not on the main topic, but since OP mentioned CORS being a pain: is there a reason the browser doesn't let sites do cross-origin requests, but just without any cookies etc.? Either through a separate API or just the default behavior in the absence of CORS headers, is there a reason for that not being a thing? I can't imagine nobody has thought of it?
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#683Earlier quoted context omitted.
That’s a very rosy way of looking at it. iOS has had bugs with its “add to home screen” webapps that kicked around literally for years . If they were being “user first” they’d support it fully or not support it at all. Instead they implemented then neglected it.
Probably because Apple giving a crap about web apps was depreciated with the release of iPhone OS 2.0 and the App Store over a decade ago. I'd bet few users even use the "add to home screen" button outside of corporate environments that want to add a shortcut to internal sites.
Facebook messenger is good use case for web app, but zuck want's to track you so you need to install app instead...
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#684Earlier quoted context omitted.
> Without it it could be just Blink everywhere at this point. In what reality-distortioned universe is that worse than having a crippled web?
Please don't call anything that's not Blink "a crippled web".
I believe that OP is saying it would be preferable to have blink-everywhere than to have a deliberately-crippled Apple web browser with all other choices banned.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#685Earlier quoted context omitted.
I'm the OP, I use a lot of PWAs. My main machine is a Surface Pro X and I don't have native apps (as in native aarch64 binaries) for many of the things I'd like to use. So, I'm using PWAs for Instagram, Twitter, Kindle, Pinafore (mastodon client), Spotify, and some of my own. I was developing a feed reader that was supposed to be a client-side-only PWA but that's tricky.
Off topic, but how is this experience using the Surface Pro X as a PWA machine? Does Windows / PWAs work well in tablet form? I was thinking of switching to a similar setup and using it essentially as you describe. Seems like it could be a really lightweight and simple computing environment similar to Chromebooks but still allows you to run traditional Windows apps as well if you need.
I really like it but I wish Microsoft would support FOSS developers better and provide more support and incentive for them to port more developer tools. There are almost no native aarch64 programming languages for Windows 10. If you keep yourself inside WSL then you're good to go because Linux under aarch64 is quite complete. On the windows side of things you'll probably running a lot of 32bits x86 apps.
Which is one of the reasons I like PWAs, they are ISA independent and are working pretty well here. Unfortunately Firefox doesn't support an add to homescreen feature on the desktop, so I used Edge to do it for the apps I want to have a nice icon for (such as spotify).
If you're going to use it much like a chromebook then it might be a tad too expensive to be justifiable. I don't regret buying mine at all, I really like it, but I'm sure they'll release cheaper ARM64 Surfaces soon, I'm betting on a Surface Go with ARM64 at some point.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#686Earlier quoted context omitted.
> Always ostensibly to protect users but always also conveniently putting webapps at a permanent disadvantage to native apps. This isn't always a bad thing though. For example, Safari has prohibited some obnoxious behavior that Chrome has allowed: Autoplaying videos, tab suspension, push notifications. These hog CPU and destroy battery life, worsening the user experience. Remember, making everything a web app is Goog…
MacOS Safari autoplays YouTube videos with now way to disable...
Interesting. I can tell Safari to not autoplay videos on YouTube in its preferences, but that doesn't seem to do anything. Seems more like a bug on Safari's part and/or workaround on Google's part than anything deliberate.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#687Earlier quoted context omitted.
I'm the OP, I use a lot of PWAs. My main machine is a Surface Pro X and I don't have native apps (as in native aarch64 binaries) for many of the things I'd like to use. So, I'm using PWAs for Instagram, Twitter, Kindle, Pinafore (mastodon client), Spotify, and some of my own. I was developing a feed reader that was supposed to be a client-side-only PWA but that's tricky.
Do you know a PWA for Kindle? Their browser-based reader hasn't been updated for quite a while.
Their Kindle Cloud Reader is better than the native windows app IMO. I don't know when it was last updated, I first used it this year.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#688I 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…
> There's no reason they can't have PWAs work well in Safari other than they want you to port your app to the App Store and get locked into their native APIs. Is it possible they also want you to port your app to the App Store to prevent an explosion of garbage and malware that could happen if PWAs really took off?
I seriously doubt that. It's a lot more difficult to do horrible things with PWAs than it is with native apps. Apple has a history of doing everything they can to keep people inside their walled garden and this is just another instance of that.
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#689This can't be prosecuted as anti-competitive practice?
Re: Private client-side-only PWAs are hard, but now Apple made them impossible
#690Earlier quoted context omitted.
Please don't call anything that's not Blink "a crippled web".
I believe that OP is saying it would be preferable to have blink-everywhere than to have a deliberately-crippled Apple web browser with all other choices banned.
I'm the OP and I am a Mozilla volunteer. I prefer a web with many engines, I want it to have WebKit, Blink, Gecko and more.