15 Clicks to install an app from the web using the newly proposed Apple flow
twitter.com
twitter.com
There are problems with Apple's proposal. This is not one of them, and I don't think it's fair to come to the right conclusion for the wrong reasons.
I dislike this post a lot. I'm not sure what else to say.
There could be many problems. Who decides that "installing an app from a website should be as easy as from the App Store, but is not" isn't one of them?
That's also a real issue on Android yes.
You could say how many clicks it takes to install an app from the web in the best case.
1. Visit the website
2. Hit "Install"
3. There's some confirmation screen apparently, press "Install" again
4. Verify your password/Face ID
And that's it.
That's what the Twitter link describes, minus the first-time setup of allowing third-party apps (which as I said in GP, is rightly a thing on Android too), and absurd steps like "wonder where you were" and "swipe on your home screen".
It takes 15 clicks to install an app from the web using the newly proposed Apple flow. Here's the journey:
1. Visit the website for the download link. Click on a unique deep link.
2. Encounter a warning about the unknown provider. Click "Learn More."
3. Navigate to an Apple support page for instructions.
4. Find the “allow installation” section in settings.
5. Encounter another warning screen.
6. Use Face ID to proceed.
7. Wonder where you were and go back to the browser.
8. Tap "Install" again for the app.
9. See a confirmation sheet; tap "Install."
10. Face another scare screen and confirm.
11. Use Face ID again.
12. Nothing seems to happen; you're back on the website.
13. Check your Home Screen and swipe to the last page.
14. A new icon appears, not marked with a "New" bubble.
15. Finally, launch the app.
Also his last 4 items are all things that happen after the app is installed and the flow is the identical to apps from the Apple Store. Also two of those do not involve any clicks or other UI operations.
In discussions of user paths when discussing their length, where most of the actions are clicks (or touches which get called clicks), people often count other actions as clicks instead of counting them separately. For another example in this very list: swipe.
It would be more correct to say “15 actions” or “15 steps” not “15 clicks” but that to many readers would seem to exaggerate the process more as a step or action might imply something more complex than a click/touch.
> Also his last 4 items are all things that happen after the app is installed and the flow is the identical to apps from the Apple Store.
Which people will know, so it is a valid comparison. Though I suppose it would be more accurate to state “11 additional actions” which is attention grabbing enough.
Also, is it exactly the same (don't own/rent any iDevices so can't check first hand)?
With a native app install is “not marked with a "New" bubble” true?
Does nothing truly seem to happen at the native app equivalent of step 12? If so that is bad UX to start with. On Android at that point I get the option to open the newly installed app or return to the app store.
> Also two of those do not involve any UI operations.*
But possibly should. Some indication that something has happened, if only a toast that auto-vanishes.
Just as Apple has sabotaged Safari forever, there's no chance Apple will ever allow third party app stores to be usable.
And they will continue to do so, as long as enough people behave like gullible fools for them to make money from them hand over fist.
How is this considered step in installing an app from the web?
The iPad is new, running the current iPadOS. The iPhone is too old for the current. Is this something they added in 17 for iPhone but not iPad, something they have added but only in Europe, or what?
I think it only shows when an install/update is done without user interaction (e.g. auto-updates, or when you've got "Automatically download purchases" enabled).
> Check your Home Screen and swipe to the last page.
While Apples implementation may have valid problems this post is just a clickbait exaggeration.
1. Visit the website for the download link. Click on a unique deep link.
2. Encounter a warning about the unknown provider. Click "Learn More."
3. Navigate to an Apple support page for instructions.
4. Find the “allow installation” section in settings.
5. Encounter another warning screen.
6. Use Face ID to proceed.
7. Wonder where you were and go back to the browser.
8. Tap "Install" again for the app.
9. See a confirmation sheet; tap "Install."
10. Face another scare screen and confirm.
11. Use Face ID again.
12. Nothing seems to happen; you're back on the website.
13. Check your Home Screen and swipe to the last page.
14. A new icon appears, not marked with a "New" bubble.
15. Finally, launch the app.
I just checked on iOS. Here's an example PWA: https://mdn.github.io/pwa-examples/a2hs/
The steps to install are (following the GP's format):
1. Visit the page
2. Press the share button in the toolbar
3. Scroll down a bit in the share panel
4. Tap "add to home screen"
5. Edit the name and click "done" (or "Add", both work)
6. Check your Home Screen and swipe to the last page
7. Finally, launch the app
All the scary warning dialogs and face ID checks are only for native apps, just as for APKs on Android.
Edit to add: hmm, it's possible there is some scary warning dialog the first time you install a PWA, and I've already skipped that, but I don't recall encountering such a thing before.