←back to thread

428 points coronadisaster | 1 comments | | HN request time: 0s | source
Show context
msoad ◴[] 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 #
untog ◴[] No.23679848[source]
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.

replies(3): >>23680051 #>>23680053 #>>23680192 #
coliveira ◴[] No.23680192[source]
Native apps are not handling my bank account passwords. They're also not collecting data about my consumer behavior with the goal of displaying more ads. This is a big difference.
replies(2): >>23680437 #>>23680484 #
1. CaveTech ◴[] No.23680437[source]
> Native apps are not handling my bank account passwords.

You're conflating browsers (Chrome, Firefox, etc) with user applications. User applications are still not handling your bank passwords.

> They're also not collecting data about my consumer behavior with the goal of displaying more ads.

lol? Absolutely wrong here.