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

(www.zdnet.com)

428 points coronadisaster | 1 comments | 29 Jun 20 10:16 UTC | HN request time: 0.001s | source

Show context

msoad ◴[29 Jun 20 17:15 UTC] No.23679601[source]▶

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.

replies(6): >>23679828 #>>23679848 #>>23680171 #>>23680533 #>>23681627 #>>23684654 #

nojito ◴[29 Jun 20 17:28 UTC] No.23679828[source]▶

>>23679601 #

Rhe fact that people don't realize PWAs are the next push by Google to regain control is shocking.

The number of hackernews threads calling out Apple for not supporting PWAs is just as insane.

replies(2): >>23680016 #>>23680817 #

1. spideymans ◴[29 Jun 20 18:38 UTC] No.23680817[source]▶

>>23679828 #

Interesting thought. I wonder if there's a genuine threat of google "AMP-ifying" PWAs. And by that, I essentially mean Google using their properties to exert control over PWAs, just as they have with web articles and other content. Given Google's virtual stronghold over the web, I'd assume so.

↑