←back to thread

428 points coronadisaster | 1 comments | | HN request time: 0.233s | 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 #
Abishek_Muthian ◴[] 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 ◴[] 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 #
the_gipsy ◴[] No.23681669[source]
Why on earth would I use a native app for twitter? It's all static content browsing, this has been solved decades ago with the web.

The occasional tweet I may send is just an input field and a file upload maybe.

replies(3): >>23681798 #>>23686410 #>>23689695 #
Longhanks ◴[] No.23681798[source]
This is a perfect example of a HN reader being out of touch with what the vast majority of users actually want. There are plenty of reasons people want a native twitter app: state restoration, integration with system services, push notifications, better user experience, better accessibility, fewer ways to track the user, better permission model, ...
replies(4): >>23682319 #>>23682546 #>>23683027 #>>23683355 #
1. mypalmike ◴[] No.23683355[source]
"Out of touch" is an unfair characterization. Not everyone wants what you think they want.

I specifically do not want push notifications from Twitter or almost any other app aside from calendars and alarms. Having Twitter notify me about every stupid online interaction was causing my life to be buried in constant distraction. Without a doubt, my life is better without it, and I don't think that's an unusual perspective.

Also, I would be curious about your reasoning that running an app gives fewer ways to track the user. I would tend to believe the opposite.

*Edit: 1 minor typo