[binarycrusader]

Actually, Google Wallet works almost exactly the same as ApplePay (my spouse has an iPhone 6, I have a Moto X 2014); I've seen and used both.

Just tap the phone on the NFC device and that's it (the PIN pad at the retail may then prompt you to hit credit or debit, if you choose debit, you just enter your wallet pin again). If Google Wallet needs to be unlocked first, it will prompt you for the wallet pin.

In fairness, it used to be far more cumbersome. They fixed most of the user interface problems with the release of Android 5.0.

[danudey]

But unfortunately most devices don't (and can't) run Android 5.0, so they're stuck with the old, cumbersome Wallet (or, worse, tried it, gave up on it because it was a terrible experience, will never try it again).

[ericd]

True, but in the same vein, most iPhones out there don't have NFC built in. (Was added in the iPhone 6)

[soylentcola]

I could've sworn it worked the same when I was running 4.whatever on my old Nexus 5 prior to the 5.0 update. From an end user perspective I haven't noticed much of a change in at least a couple of years (aside from some vendors disabling support in favor of their own tap to pay).

[binarycrusader]

The difference I believe came with the ability for the app to automatically be run in the background and for control over which one was used for Tap and Pay, which given today's announcement from Google makes sense.

Maybe this was fixed in Android 4.4, but I would swear the experience changed for me sometime right at or after 4.4.

Notably, I didn't have to make sure the app was open and wallet unlocked first, whereas with Android 5.0 it "just works".

[Nemisis7654]

To be fair, the updated design (Material Design) is mostly back-ported all the way to 2.3. The user experience is practically the same on 5.0 as pre-5.0.