[natem345]

Why do you find this more friendly than Google Authenticator? Just because it pushes rather than requiring the user to open an app? Can you still manually get a code, in case you lack network (& don't want to break out the backup code)?

What if you're actually logging in with the iDevice, does it just automatically allow it without asking?

[masnick]

> Why do you find this more friendly than Google Authenticator? Just because it pushes rather than requiring the user to open an app?

Exactly. I have so many things in Google Authenticator that I have to scroll. The timer is also annoying -- sometimes you have to wait for a few seconds for the codes to refresh so you have enough time to type in the code.

> Can you still manually get a code, in case you lack network (& don't want to break out the backup code)?

No, but for Apple you don't need to do this because you only need the code if you're accessing their website so you have to have internet access. I don't think I ever use the Google Authenticator without internet access.

> What if you're actually logging in with the iDevice, does it just automatically allow it without asking?

No idea.

[natem345]

Fair enough.

> No, but for Apple you don't need to do this because you only need the code if you're accessing their website so you have to have internet access. I don't think I ever use the Google Authenticator without internet access.

At work, I have no cell service but can still use my laptop. I don't want to use their wifi with my phone due to proxy server setup hassles. So I think it's still a valid use case.