Earlier quoted context omitted.
I'm going to be fascinated to see what this does for conversions. My company built the Neil Young Archives, when doing so we initially launched with Social log ins and at one point Neil decided Facebook and Google were evil and wanted to remove the access. According to our logs a full 2/3s of all users were registering with a social account and we were having great success getting folks to log into a free service (We…
This escenario seems an clear candidate for A/B testing since I would be conflicted by wanting to provide privacy but understanding it might impact user signups. Seeing some actual numbers would help me in making that decision.
Why we won’t be supporting Sign in with Apple
81–90 of 485 posts
Re: Why we won’t be supporting Sign in with Apple
#82I found it jarring that Apple would present themselves as the vanguard defenders of privacy by announcing what is basically an email relay service. Most privacy-conscious people wouldn't exactly think of their emails going through Apple as any particular win in privacy. And even for the "general user" I find the argument very weak, since it doesn't look as being any easier than using any other email relay, and there…
Re: Why we won’t be supporting Sign in with Apple
#83This makes perfect sense from their standpoint - especially since they've had similar problems to what they outline with Facebook sign-in and are now dropping that as well. This is also a win for Apple & end-user privacy, as there's one less app using FB's login feature now. I think Sign in with Apple is a great step forward even if all it does is eliminate apps that require Facebook and/or Google accounts to log in.…
Also there are cases where a "sign in with " is the only option that makes sense because you really want to integrate with the API of this provider. Take for example a "sign in with GitHub". Or in case of services correlated, take for example Instagram where you obviously can sign up with a Facebook account.
I'm more for letting the developer choose what it prefers for authenticating the user and not having a authentication system that gets imposed by Apple.
Re: Why we won’t be supporting Sign in with Apple
#84Users have the option to provide their personal email address, but given the track record of these being sold it’s reasonable to expect users to not trust you.
You can email them correspondence because as above that goes to their primary email.
What you lose is the value of the email address as an asset.
Re: Why we won’t be supporting Sign in with Apple
#85Re: Why we won’t be supporting Sign in with Apple
#86Earlier quoted context omitted.
No, they're fine -- if your only login is first-party, you don't need to support Sign in with Apple. (They're taking out FB login to comply.)
I do wonder, though, whether the requirement for Sign in with Apple is coming in a few years. As in, if you allow users to sign in with email/password, you must allow users to sign in with "sign in with apple". It might be more subtle, like suggested auto-fill to create a new account.
Re: Why we won’t be supporting Sign in with Apple
#87This makes perfect sense from their standpoint - especially since they've had similar problems to what they outline with Facebook sign-in and are now dropping that as well. This is also a win for Apple & end-user privacy, as there's one less app using FB's login feature now. I think Sign in with Apple is a great step forward even if all it does is eliminate apps that require Facebook and/or Google accounts to log in.…
For my last two companies (both B2B), I implemented login via Google accounts only. Google login has a number of advantages: 1) Identity is an email address. If I wanted to rip out Google, or Google kicked me off the platform, all I need to do is add passwords and put a "forgot my password" link and my customers continue business as usual. 2) It's not a google-specific email address. You can create Google accounts fo…
Re: Why we won’t be supporting Sign in with Apple
#88> Another issue is Sign in with Apple’s “Hide My Email” feature. With this feature, if you create an account with us, Apple will generate a special email address just for that account. So rather than your email address being john.doe@icloud.com, we will see your email address as something like dpdcnf87nu@privaterelay.appleid.com. Ironically, this is also why I use Sign Up with Apple at every opportunity I can
Re: Why we won’t be supporting Sign in with Apple
#89Earlier quoted context omitted.
This escenario seems an clear candidate for A/B testing since I would be conflicted by wanting to provide privacy but understanding it might impact user signups. Seeing some actual numbers would help me in making that decision.
I don't disagree with you and it was proposed. However we didn't have A/B infrastructure in place then and on a project that may never make money it just wasn't a high enough priority to justify the spend.
Personally I would have considered to hack something on my own time just out of curiosity :D