Agreed, I use Apple Pay semi-frequently, but in my experience the ergonomics taken a step back since I upgraded my iPhone. I went from pulling my phone out of my pocket with my thumb already on Touch ID > hold near reader > paid to pulling my phone out > hold near reader > phone says get face closer > double tapping the lock screen button which is kind of out of the way on my iPhone 11, and I've locked the screen inadvertently, likely due to the case slowing me down when pressing at times. Not the worst, but not an improvement in my opinion.
pulling my phone out > hold near reader > phone says get face closer > double tapping the lock screen button which is kind of out of the way on my iPhone 11
You're doing it wrong.
Pull phone out → double-click wallet button → Authenticate face → Hold next to reader → done.
Fair point, however, it is worth pointing out I upgraded from a Touch ID phone, where one simply places the phone close to the reader and applied the same behavior to a Face ID phone. I don't believe I'm alone in this learned behavior, and blaming the user for "doing it wrong" is not a sign of great UX.
Your flow misses a critical point. You can have a long pause after FaceID, but before tapping. This means that you can, say, authenticate while the grocer is ringing up each item, sit there until they finish, and only then tap.
Pull phone out → double-click wallet button → Authenticate face → Pause for a long time → Hold next to reader → done.
On my Pixel 2: Pull phone out, putting on finger on the fingerprint reader while holding it > tap on terminal. It's just all one motion. Super convenient.
The phone tells you the sequence every time. You double-press the button, it shows the FaceID prompt. You authenticate with FaceID, it tells you to hold it near the reader.
Yeah, but it doesn't tell you the sequence all at once. So you don't know that it's going to tell you to hold near reader, but you know that it needs to be held there, so you try to hold it there while you authenticate, which is at the wrong angle for auth, so it fails, so you click the button again, which this time turns the screen off...
