Earlier quoted context omitted.
PWAs can't use WebAssembly?
Perhaps, but WASM isn't ready yet.
Microsoft and Google collaborate to make PWAs better
121–130 of 198 posts
Re: Microsoft and Google collaborate to make PWAs better
#122I have a feeling that Microsoft is going to launch an "Edgebook" competitor to Chromebook in the the future using Windows 10X. This obviously is good for the ecosystem all around, for tablets, phones, desktop, etc.
Isn't this Windows RT?
https://www.microsoft.com/en-us/p/surface-pro-x/8vdnrp2m6hhc...
https://www.samsung.com/us/computing/windows-laptops/galaxy-...
Re: Microsoft and Google collaborate to make PWAs better
#123Earlier quoted context omitted.
Yes, would be cool. Firefox is currently unusable on mobile :/
I'm going to guess you're on iOS where you don't actually have Firefox (or any other actual browsers besides Safari). Firefox on iOS (like all iOS browsers) is required by App store rules to basically just skin Safari. On Android, Firefox is the MOST usable browser.
Re: Microsoft and Google collaborate to make PWAs better
#124I miss Chrome apps. What was wrong with them? Genuine question.
They were proprietary; only worked in chrome. Progressive webapps are built out of open standards, and will ideally eventually work everywhere.
Open standards are meaningless when only one cares about them.
Re: Microsoft and Google collaborate to make PWAs better
#125Earlier quoted context omitted.
The caring for privacy is only lip service. Consider that on iOS, you cannot get your location without also sending that location to Apple. You cannot install an app without telling Apple what you installed. You cannot install your own app on your device in a usable manner without giving banking details to Apple. You cannot subscribe to a service that has an associated app from that app without telling Apple that you…
This is a bad-faith distraction from the topic at hand. The privacy work that Apple has done on the web is real and significant. We know because ad pricing for Safari users has dropped 60%, while for Chrome users it's increased. That means tracking is working on Chrome and not Safari.
As far as ad prices, you are citing a report from 2019. Since then, Safari ITP has been thoroughly compromised to the point where it leaks more information when it's on than when it's off. Meanwhile, Chrome supports uBlock Origin, just like Firefox (and unlike Safari).
Re: Microsoft and Google collaborate to make PWAs better
#126Earlier quoted context omitted.
I agree. Apple is stifling innovation by not supporting certain APIs. They need to stop doing this, or they will hurt themselves in the long run. As it is, most people use Safari on iOS because they are forced to - all other browsers on iOS are forced to use WKWebView, which basically means they are wrappers around Safari's view. To this day, I can't understand why their users stand for this. In this regard, Apple re…
Apple is making the right decision here. My iOS device has never once shown me "this website requires Chrome." I get to use the mobile web without needing Google. And Apple is the only reason why. Maybe some day, web apps will become so undeniably awesome that Safari's position is untenable. But the agitation is not coming from iOS users missing out on awesome PWAs. Instead it's web developers, who are just annoyed t…
As an end user, I dread the days PWAs ever go mainstream. They’re horribly inefficient from a power and performance point of view, and never have I come across a PWA with a user experience half as good as native apps (especially on mobile). Until they’re indistinguishable from native apps in terms of user experience, I want nothing to do with them. Beyond that, there’s some very serious privacy concerns as well with PWAs, especially with developers abusing APIs for fingerprinting
Re: Microsoft and Google collaborate to make PWAs better
#127Earlier quoted context omitted.
Apple is making the right decision here. My iOS device has never once shown me "this website requires Chrome." I get to use the mobile web without needing Google. And Apple is the only reason why. Maybe some day, web apps will become so undeniably awesome that Safari's position is untenable. But the agitation is not coming from iOS users missing out on awesome PWAs. Instead it's web developers, who are just annoyed t…
>My iOS device has never once shown me "this website requires Chrome." Why would any PWA say that, if Safari had proper support for PWA? >Instead it's web developers, who are just annoyed that they have to actually respect the conventions of the platform they're building for. Say the developer is from a village in India or Nigeria who has just a Raspberry Pi to develop apps - •What if the developer didn't have thousa…
For the same reason that far too many desktop websites say that today.
> Say the developer is from a village in India or Nigeria who has just a Raspberry Pi to develop apps
Apple is not catering to this developer demographic.
> For all the times Apple uses 'Equality' in its marketing, the Apple platform & ecosystem restrictions clearly seems to be aimed at the privileged
You're conflating developers with users. What fraction of iPhone users are writing apps? If you wanted to prioritize users, there's much tougher questions you could ask.
Re: Microsoft and Google collaborate to make PWAs better
#128Re: Microsoft and Google collaborate to make PWAs better
#129This article used the term "PWA" 24 times without defining it once. I assume the WA part means Web App but it's the "P" for "portable" , "Pocket" or something else?
Re: Microsoft and Google collaborate to make PWAs better
#130This article used the term "PWA" 24 times without defining it once. I assume the WA part means Web App but it's the "P" for "portable" , "Pocket" or something else?