Android Pay counter-rant

[G+_Vance McAlister]

Android Pay counter-rant

 

I would like to provide a response to Big Jim's well-spoken, but possibly over-stated, rant about Android Pay and try to answer Ron Richards  question regarding why two apps.  First, I have been following the discussions about Android Pay in forums and communities and have used Android Pay myself on numerous occasions.  Not only have I never had a mishap, the general chatter among the users doesn't seem to bear out any particular issue at all.  It seems that the misfires tend to be individual issues, not something pervasive. Most seem to be doing just fine.  The only annoyance I had early on was having to install a PIN/Pattern in the first place, but Smart Lock with either body detection or my watch solved that problem.  The only other complaint I have seen with any regularity is that their card is not supported.

 

As for Ron's question, I wondered that at first as well, why two apps, but after using them for a while, it makes sense.  First, the Tap to Pay and loyalty card features of Android Pay are just MUCH smoother, simpler and faster than it was with Google Wallet.  With so much less going on, you can get in and out of the app as needed on the fly.  Sending money is such a niche use-case, and entirely unrelated to tap to pay or loyalty cards that I definitely don't want that rare use gunking up my lean and clean Android Pay experience.  

 

After having used both set ups with some regularity, I can say without hesitation that the new way is the better way. 

 

cc Jason Howell Florence Ion 

[G+_Joseph Cappellino]

While I agree that the new way is better, I have an issue with the way they handle the PIN when using Smart Lock.

 

I use Smart Lock with my Moto360, so basically, it's almost always unlocked (unless I walk away from my phone/watch).  For me to actually pay for something, I have to first tap my device, which then prompts for me to unlock my device.  From there, I have to wait for the transaction to timeout, and then tap again.

 

I love that they have additional security when using Smart Lock, but this should be on app open instead of after a tap.  Granted, this could all be based on my use case (a vending machine), but I'm pretty sure it's the same for other terminals as well.

[G+_Vance McAlister]

Joseph Cappellino Interesting, since adding Smart Lock I have not had to put my pattern in again.  I think the idea is that if your phone is unlocked with Smartlock, it doesn't require any pattern or PIN upon tap.  What you should try is having your phone unlocked and on a home screen at the time you tap and see what happens.  My understanding is that it will only prompt a PIN or pattern if your phone is actually not turned on and locked.  Of course, I could have that entirely wrong.

[G+_Joseph Cappellino]

Vance McAlister every time I do it, I'm in the app first (I find it has the most success).  Thankfully, it's a software issue, not a hardware one, so it can resolved somehow.

[G+_Vance McAlister]

Joseph Cappellino Yes, that is interesting.  I wouldn't want to have to enter a pattern every time I tap.

[G+_Vance McAlister]

Joseph Cappellino hey, you jinxed me, the exact same thing happened with me today, I had my phone open, tapped and it pulled up my pattern! Do that, retap and works fine, but still. Wonder if this is all just settling in, or whether that will be the way it is.

[G+_James Thatcher]

Allow me to elaborate on my rant. Not only did I have issues with android pay, I also had to factory reset later (after rant) to get my phone to function properly, perhaps it's because I'm on a one plus one, perhaps it was just an of circumstance, but I one think so... I think Google half baked this and sent it out.?

[G+_Vance McAlister]

James Thatcher But, despite some annoyances like we were discussing above regarding having to possibly put in a PIN/pattern, I have not seen anyone else with that crashing issue.  It may be more of a One+ issue than a Google/Android Pay issue.

[G+_James Thatcher]

Vance McAlister?? then why am I seeing others having similar issues on other devices, look at the reviews, Google search android pay not working and you see several lg and Sony devices having issues.

 

Just because it works for you doesn't mean it works for everyone. And just because it's broken for me doesn't mean is broken for everyone

But the rants issue was that it did work, then they monkeyed around and made a new app that didn't work for several.?

[G+_Vance McAlister]

James Thatcher Yes, I guess it is a matter of degree of the issue. With every new device there are going to be some who have problems, but I am trying to see whether it is greater than the norm for a new tech release, or whether there is a significant pattern.  It always sucks for those who DO have a problem, though, that is for sure.  I have been there on a number of occasions.

[G+_Elizabeth Whitmire]

Android Pay works great for me, and what was that about not being able to use Chase? I have Chase cards loaded into the app, and I've been using one of them for Android Pay. I've also been able to use the Chase app, in case that's what Jim was talking about. I think he's doing it wrong. :P Jason Howell Ron Richards Florence Ion 

[G+_James Thatcher]

Elizabeth Whitmire  ... My credit card sync'ed just fine. my reward cards are there, NFC is turned on - but when I want to pay it asks for my password/pin/pattern and then it freezes up my phone requiring me to do a hard reset. That's not how this software should work; especially after I had 0 issues with Google Wallet. So if I am doing it wrong, please tell me what I need to do to get it to function, then I would ask Google if that's the case why didn't they make that kind of instruction when you start the app (like they do with every other google program

[G+_Elizabeth Whitmire]

James Thatcher Your phone isn't rooted, right?

[G+_James Thatcher]

Nope