2 ms·

Thanks for the info, charrondev and coder543 I still don’t see why “then the mechanism that let's websites prompts to install apps should be removed so apps ar

Thanks for the info, charrondev and coder543 I still don’t see why “then the mechanism that let's websites prompts to install apps should be removed so apps are on the same level as web apps. Otherwise, the situation is part of the anti-competitive lock-in.”. Web sites drive this, and can choose whether they let iOS show a “download the app” or a “install on home screen” option. It’s not Apple making that choice.

coder543 4y ago
I’m fairly sure most people would prefer that Apple offers a version of the Smart App Banner that gives users a simpler install experience for PWAs. I think saurik was just humoring yamtaddle‘s perspective that PWAs should not be able to prompt for installation ever, and pointing out that it would only be fair to apply their restriction to websites offering native apps too. Right now, the install process for PWAs is needlessly obtuse compared to what users experience with a Smart App Banner. I saw someone elsewhere comment on the number of taps required with both methods, and I would point out that not all taps are equal. The simple, guided flow that the Smart App Banner gives users is tremendously easier for users to figure out than the “Add to Home Screen” flow that currently exists.
jsnell 4y ago
It'd be Apple artificially giving native apps a boost / penalizing PWAs, like they've been doing for 15 years. Sites want to get on the home screen. If the only viable way to get to the home screen is to make a native app, the site will either be forced to implement a native app for no reason or be at a disadvantage. Apple pretty obviously can support a similar UI for PWAs as for native apps. If they don't, it's just them doing the bare minimum required by regulators while still keeping PWAs as an uncompetitive second class citizen. And if the argument is that these banners are bad UX and will be abused (because that's always Apple's argument for why something should not be allowed in browsers), then they should own up to it being bad UX for native apps too and remove it.

coder543 4y ago

I’m fairly sure most people would prefer that Apple offers a version of the Smart App Banner that gives users a simpler install experience for PWAs. I think saurik was just humoring yamtaddle‘s perspective that PWAs should not be able to prompt for installation ever, and pointing out that it would only be fair to apply their restriction to websites offering native apps too. Right now, the install process for PWAs is needlessly obtuse compared to what users experience with a Smart App Banner. I saw someone elsewhere comment on the number of taps required with both methods, and I would point out that not all taps are equal. The simple, guided flow that the Smart App Banner gives users is tremendously easier for users to figure out than the “Add to Home Screen” flow that currently exists.

jsnell 4y ago

It'd be Apple artificially giving native apps a boost / penalizing PWAs, like they've been doing for 15 years. Sites want to get on the home screen. If the only viable way to get to the home screen is to make a native app, the site will either be forced to implement a native app for no reason or be at a disadvantage. Apple pretty obviously can support a similar UI for PWAs as for native apps. If they don't, it's just them doing the bare minimum required by regulators while still keeping PWAs as an uncompetitive second class citizen. And if the argument is that these banners are bad UX and will be abused (because that's always Apple's argument for why something should not be allowed in browsers), then they should own up to it being bad UX for native apps too and remove it.