Apple declined to implement 16 Web APIs in Safari due to privacy concerns

Google's developer relations team have done a good job convincing web devs that those APIs are pushed by Google to enable "Amazing PWAs", yet we haven't seen them used by any major app. People are choosing to download native apps for more sophisticated applications.

However Google is pushing those APIs because they know tracking people without cookies in future is a big challenge for them and they need new ways of tracking people.

So sad that Google has taken over the web. From the most used browser (Chrome) to the content hijacking (AMP) to the standards (PWA). All to sell you to advertisers.

You have to build these APIs before people use them, and a lot of what Google has been building into Chrome is stuff native apps can do, so the use-case is clearly there.

IMO native apps are capable of far more invasive privacy violations than the web is. But for some reason they're given a very free pass by comparison.

They're given a very free pass because it's incredibly easy to block a native app from sending data back or even connecting to the internet at all.

You have a lot more control over something that's running locally than something running serverside that simply using the client to harvest data.

It's even easier to block a web app - just don't visit its web address.

A native app sits on your device, executing all kinds of code, sometimes without your knowledge. With PWAs, the code is more or less open source - all the JS is there for you to inspect - even after obfuscation, you can see the network requests being made in the dev tools of any browser.