4 ms·
That's not it. It's Apple. They are crippling the web on purpose. We can't even have haptic vibration on Safari. And when we did for a little while earlier thi
by davidmurdoch 29d ago
That's not it. It's Apple. They are crippling the web on purpose.
We can't even have haptic vibration on Safari. And when we did for a little while earlier this year, it was because of a "bug" that that they promptly fixed.
Apple is not interested in making with apps as seamless and integrated as native because: money.
- afavour 29d agoI agree that Apple has been awful here. But there are countries deeply dominated by Android that still heavily use apps when they could be using PWAs. I don’t mean to let Apple off the hook but I also don’t think they’re the only ones to blame.
- jen20 29d agoAs an iPhone user: good. There is no good that can come from some dipshit website product manager being able to make my phone vibrate on a website. None at all.
- afavour 29d agoIs there any good that can come from a dipshit mobile product manager being able to make your phone vibrate on an app? Is there actually a meaningful difference?
- jen20 29d agoGames are the usual reason in an app. Being able to do it as a “drive by” on a website though: absolutely hell no.
- afavour 29d agoSounds like it would be ideal to add it to Home Screen webapps only, just like web notifications. And yet…
- aetch 29d agoYes, because visiting a website is much easier to do even unintentionally. The last thing I want is my phone to vibrate as I scroll past an ad
- afavour 29d agoWhich is why things like permission prompts exist.
- dymk 29d agoParent comment is talking about PWA APIs that only show up when the PWA is added to the Home Screen, not via safari.
- davidmurdoch 29d agoAn installed PWA should be able to do all the same things an installed app should do. The general web should not, and no one is arguing for that.