Salesforce Authenticator 4+

I usually don’t write reviews by putting my time but this app deserves this review.
I previously trusted Microsoft authenticator and loaded all my accounts but after resetting my phone, I got Fkd because I don’t pay for my icloud backup and it microsoft authenticator is not backed up.
Salesforce Authenticator automatically backsup all your accounts with your phone number as a login id.
even though you buy a new phone or reset your phone, if u have your phone number and passcode, your 2FA accounts are all safe.

This app is horribly intrusive and inconvenient. The only way it will remember a trusted device is if location tracking is set to “Always allow.” This is due to the way the authenticator handles registered devices: it is based on geographic location, so I see the street address of the sign-in attempt. I never permit any apps to “always track” my location and it seems outrageous that this would be necessary in order for Salesforce Authenticator to do something as simple as remember a trusted computer. I’ve never encountered another authenticator app with this behavior. Users are left with the poor choice of either permitting the app to track them at all times (as an aside, this is poor handling because the location icon is always visible in the iOS status bar, which is its own annoyance), or to manually approve the sign-in attempt every single time. Truly noxious app behavior.

The Authenticator functions but might require a heavy lift to get it there and it doesn’t play well with all SF access points. If you’re logging in to SF via a browser, the Authenticator is straightforward. If you’re trying to use SF extension for Gmail it’s amateur. Sometimes you have to uninstall and reinstall the extension entirely because even after you click Approve on the app, it won’t let you in on the Extension. Have had to reinstall twice within first three weeks. If you have already authenticated your device and logged in to SF in a browser, you still have to do it again on the same device to get into the Extension. The functional but amateur fix is to authenticate on the browser experience first, then on the extension, otherwise you’ll click approve on the app again and again, but you won’t be able to get in.