I've seen "Sign in with Apple" exactly once since iOS 13 launched. I am kind of surprised it's not being rolled out more widely. The first app I've seen and used it with was Byte (the Vine successor) over this past weekend.
I never take that option if there is anything else available. They don't need to see my signins on other sites, why should I just give it to them? For a few sites where it is utterly unavoidable I make one-off twitter accounts instead, because Twitter doesn't require your phone number to make an account and doesn't have a "only one account per person" policy I think.
It's also easy in general to revoke permissions with these SSO providers rather than dealing with whatever the service's account cancellation protocol is.
1. It’s fast
2. It gives you a pseudonym
3. It doesn’t leak all your other social graph data
4. Doesn’t require a new password
The rest are:
1. Faster than creating an email, but will require redirects, and possibly logging into fb/google
2. May give you a pseudonym but often reveals your real name
3. Are used typically to build profiles of you and create stats on app popularity across demographics
4. Don’t require a new password.
I know they're very popular, but there's so much long-term unintended baggage with using these singe signon systems...even assuming Apple's doesn't have the nefarious parts most others have.
Over here, I just use Face ID and 1Password does the tedious filing-and-remembering part that computers are good at.
And... 90% of the time, that's what I do, because I prefer to have separate logins for every site.
But sometimes, I just click the 'sign in with google' because it's a hell of a lot faster and easier.
It's a sign in to Apple, if not a sign in with Apple, and it's weird because what I'm trying to use is Google's Maps application without signing into anything. What is going on with all of this?
> not required if...Your app exclusively uses your company’s own account setup and sign-in systems.
So there’s no official guidance on the both/and case?
- If you only have social logins, you must implement apple sign in.
- If you only have your own login, you don't need to implement apple sign in.
- If you have both apple sign and your own login, you must implement apple sign in.
> If you have both social logins and your own login, you must implement apple sign in.
which is my understanding as well! Would be nice if they explicitly handle this case as it's probably the majority.
I would think that too, but the text is odd by saying "exclusively"
> Apps that exclusively use a third-party or social login service