←back to thread

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.638s | 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 #
Abishek_Muthian ◴[29 Jun 20 17:54 UTC] No.23680171[source]▶
If PWAs die, we will be struck with this duopoly in smartphone OS for foreseeable future as native apps are the ones which help them retain their position.

If we want upcoming pure Linux smartphone OS, Sailfish or any other platform which protect the mobile computing from becoming proprietary; we need web apps & PWAs to grow and capture significant market.

Apple's treatment towards PWAs has been well known as PWAs are the only threat for its Appstore monopoly in iOS.

replies(4): >>23680351 #>>23680700 #>>23681129 #>>23687251 #
spideymans ◴[29 Jun 20 18:30 UTC] No.23680700[source]▶
From a developer's point of view, I can see the value in PWAs (for them), but as an end user, I really don't see the benefit of PWAs over native apps. The UX is almost always severely degraded when compared to their native counterparts (even if the feature set is ostensibly identical). Why would I use a Twitter PWA, when the native app provides a much better UX?
replies(9): >>23680899 #>>23681495 #>>23681521 #>>23681562 #>>23681669 #>>23681934 #>>23685628 #>>23685736 #>>23695045 #
1. z3t4 ◴[30 Jun 20 21:32 UTC] No.23695045[source]▶
Mobile apps are designed to be used on mobiles. But what about web apps? You need many versions of the app, from smart-watches to desktop monitors and smart TV's. And then they will be crippled by the web chrome/shell, so we are stuck with Electron/NW.js apps if you want it to blend in to the OS. What's nice with web apps though is that they are sand-boxed, compared to Electron/NW.js apps that get full system access. What needs to be done is to give better design/layout possibilities for web apps once they are installed on the "shelf/desktop", for example transparency, able to design the top bar, able to have a window menu. Or maybe the future is UI toolkits like Flutter and React Native ?