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.
I want to pin the app, not share.
That seems purposefully misplaced. As usual with malicious compliance.
In Android: Menu > Install and create shortcut. Much cleaner, intentional, and visible with a single click for me.
I just asked my colleague and they had no clue how to do it in their iPhone. I guess a win for Apple.
The claim wasn’t that Apple put it in a poorly named menu, or that the share menu is bad UX in general. The claim was that iOS users can’t pin web apps because Apple made it “exceedingly difficult” to do so. A 3 click navigation through the standard menus that has been consistent for multiple generations and is documented in the on-device help doesn’t qualify as “exceedingly difficult”
https://developer.mozilla.org/en-US/docs/Web/API/Window/befo...
“Add to Home Screen” living on the share menu is as insane as “Find on Page” living there. Which both do. And I don’t think there’s a master plan behind “find on page” being tucked away bafflingly on the share button.
It’s just bad UX. No conspiracy here.
If this was some grand plan to stop the few hundred PWAs out there entirely, one would think they would have removed the PWA functionality in other less hostile jurisdictions where no law makers were looking to force a change. I could absolutely believe that the security risks were overblown, but if the assertion is Apple is trying to suppress PWAs, they’re doing a pretty bad job of it given they could just turn it off in the US and no one would blink an eye.
If they wanted to make it “exceedingly difficult” they could be disabling it in all jurisdictions, or hide it behind layers of developer mode dialogs and warnings. They could remove the instructions for how to do so from the on device help. They could require you to re-pin it every 3 days like they do for self loaded apps. They could stop adding support for newer PWA APIs as new ones get standardized and they could deprecate and remove APIs that already exist. We all know Apple isn’t precious about backwards compatibility.
If the goal is to make using a PWA “exceedingly difficult” Apple is failing miserably despite being very successful at making side-loading apps “exceedingly difficult”
Who are you quoting?
But sure call me crazy for thinking it's user hostile to put install / add to home 5 taps deep into the menu. That has nothing to do with supporting a 2015 web API. They would go on to add smart app banners to promote native app store apps instead.
Edit: didn't realize smart app banner was 2012
But I still disagree that it is “difficult” or “user hostile” to put the command to add a web app to your Home Screen 3 (not 5) taps away. Menu -> submenu -> command is not user hostile or difficult. The command is in the same place as all the other “do something with this page” commands. It’s not hidden behind toggles, it’s not buried in submenus away from other similar actions, it’s not in its own menu or an activity you have to leave safari for and initiate from the Home Screen instead. It takes just as many taps to change to a specific tab as it does to save a PWA