Most of these steps apply to installing an Android app from an Untrusted SourceTM for the first time. Half of these steps are fluff added for the sake of a clickable title.
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 are problems with Apple's proposal. This is not one of them,
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?
exactly, android pulling the same strategy of creating artificial annoyances is hardly a good argument. they should both be forced to cut it out. any warnings should be reduced to a reasonable minimum, anything that goes beyond that is suspicious.
But to have an option to provide app installation from the web you have to get an entitlement from Apple and be at least two years in good standing yada yada. Is it still Untrusted Source at that point?
I thought about taking a shot at it but I thought it'd seem childish. My impression is:
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".
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.
If Apple is hellbent on getting fined the biggest fine they have ever received, they should keep going down this path. Everybody is seeing through Apple's bullshit, but they persist in treating the world like gullible fools.
I think they're trying to point it out as Apple being petty and providing a sub-standard experience, however this is exactly how it's worked for a decade for anyone beta testing outside of TestFlight, or using an MDM.
I've never seen a "New" bubble on the icon for a newly installed app from the Apple app store. I just tried it on both my iPad and my iPhone, and no bubble.
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).
One doesn't install an app for the purpose of installing it, but for using it. Thus finding it is part of the experience. Also this relates to the proceeding step of being back ob the website without further information that install was successful. Thus the user has to figure this out themselves.
Yes. However, these steps still exist and they drive down adoption of all PWA in the first place. Note that these steps also have an Android analogue, but on Android there is a button you can press to go to the appropriate settings page instead of having to navigate to it yourself.
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.
None of this accidental, the European-Commission will need to treat every single suspicious implementation detail as a potential sabotaging attempt, otherwise Apple will try to kill the user experience with BS like this.
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.