131–140 of 285 posts
I'm on Android Firefox.
As soon as I tapped into this site, the browser's back button got hijacked and half of the features don't work. This is why (imo) PWAs should not try to replicate native app functionality, but instead recognize the web for what it is and play to its strengths.
Earlier quoted context omitted.
> Progressive enhancement, API detection, and polyfilling are all common strategies that can be used to mitigate almost all device differences. Keyword being "almost", and that in some cases if the platform doesn't support your feature, you're shit outta luck. By far the thing that prevented PWAs from bigger uptake earlier was Apple dragging their feet on push notifications support on iOS. There was simply no workaro…
> By far the thing that prevented PWAs from bigger uptake earlier was Apple dragging their feet on push notifications support on iOS. Is there any evidence that this moved the PWA needle at all, he said hopefully? I would've predicted no effect on PWA adoption. > …last I checked the "install to home screen" on iOS Safari was still a horrible user experience (the actions is hidden under the "share" menu, which makes n…
Earlier quoted context omitted.
Some of the functionality listed on this site is not part of the web platform, but rather Blink-only APIs Google implemented unilaterally that have been explicitly rejected by Mozilla and Apple.
Apple wants to keep in control with the app store. PWAs threaten that control. So much so apple doesn't allow other browsers.
Earlier quoted context omitted.
What's with the FUD. What else besides PWAs promise to free everyone from app store rent and anticompetitive policies? PWAs would also open the doors to new mobile OSs beyond Google or apple control.
> What else besides PWAs promise to free everyone from app store rent and anticompetitive policies? I don't know... laws? > PWAs would also open the doors to new mobile OSs beyond Google or apple control. Or force everyone into ChromeOS once and for all.
Maybe. I am not impressed so far, though.
>Or force everyone into ChromeOS once and for all.
I don't see that happening on iOS.
I tried two of the features at random (face detection and vibration). Face detection told me my device wasn't supported, and vibration just straight up didn't work. Then I tried to back out of the website and it wouldn't let me. I'm on Android Firefox.
Earlier quoted context omitted.
Doesn't https://caniuse.com already fill this need? This article is just evangelism, if you want technical sources the community has had you covered for a long time.
Sure you can look things up but it would be nice to look at this evangelism site and tell at a glance that Bluetooth isn’t supported everywhere the way playing a sound is.
And that kind of ambiguity is why you need to be using a rigorous source like caniuse and not just looking at summary statements for this kind of information.