They will get removed. They don't have the power to fight Apple.
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.)
Why we won’t be supporting Sign in with Apple
11–20 of 485 posts
Re: Why we won’t be supporting Sign in with Apple
#12A lot of the points they make here are real points, and I think AnyList has validity in their actions.
I also think it’s not as unmanageable as it seems.
Let’s analyze this quote, from the article, as it highlights what I imagine are a big crux of this issue:
> with the “Hide My Email” option, your spouse or friends obviously won’t know your privaterelay.appleid.com email address, so when they enter your email address, our systems will believe that you don’t have an account
Since you know this to be the case, why not have an onboard if flow they Sign In with Apple where you have them A) choose a visibility email used for sharing/communication etc. and B) allow for this email to be their backup email? So if they forget their login or whatever you could just transfer the account to this email instead? Of course this should be opt-in but you can always Under good faith explain benefits there in.
It’s more work, but I don’t believe that it’s going to run issue with Apple and provides end users with flexibility.
Of course this may not be worth it, at all. This is just a consideration worth thinking about as an app developer
edit: Of course another alternative here is they just make users aware of what their sharing email is and allow users to optionally change that, if they want to. This most definitely wouldn’t run counter to this I’d think
Re: Why we won’t be supporting Sign in with Apple
#13There's a subtle sense of exuberance shining through in this article that makes it a gratifying read, even if you've never heard of the company before. Kudos to them for their decision not to bow to Apple's demands. Please tell us how it goes!
Well, they're also getting rid of the "Log in with Facebook" option too, which is arguably giving into the demands of Apple.
Re: Why we won’t be supporting Sign in with Apple
#14A lot of the points they make here are real points, and I think AnyList has validity in their actions. I also think it’s not as unmanageable as it seems. Let’s analyze this quote, from the article, as it highlights what I imagine are a big crux of this issue: > with the “Hide My Email” option, your spouse or friends obviously won’t know your privaterelay.appleid.com email address, so when they enter your email addres…
> Since you know this to be the case, why not have an onboard if flow they Sign In with Apple where you have them A) choose a visibility email used for sharing/communication etc. and B) allow for this email to be their backup email? So if they forget their login or whatever you could just transfer the account to this email instead?
I'm fairly certain that detecting someone hiding their e-mail from you and then making them pick a different e-mail goes against the spirit, if not the rules, of Sign In with Apple.
That said, it would be extremely beneficial to pop up a screen saying "Hey, is this the e-mail you want to use for communications?" and let the user decide.
That said, removing third-party sign-in is also a fine solution, almost definitely a better one, and simplifies things immensely for everyone involved (assuming their sign-in form in the app supports saving passwords to the keychain).
Re: Why we won’t be supporting Sign in with Apple
#15That was an interesting read. Also, they close with... "These are both excellent points, and it’s absolutely true that some of the arguments above apply to creating an account via Facebook. That’s why we’re also announcing that we’ll be removing the Facebook Login from AnyList."
Well, that, and also if they don't remove FB login, then the would be required to also implement Sign in with Apple. They didn't want to implement Sign in with Apple, so they had to remove FB login.
Which is a pretty anti-competitive move on Apple's part.
They're essentially using their control of the iOS ecosystem to benefit unrelated products.
I seem to remember that those kinds of actions didn't work out well for Microsoft :)
Re: Why we won’t be supporting Sign in with Apple
#16If you implement Sign In With Apple, you don't have a relationship with your customers anymore. They're Apple's customers, and Apple can take them away at any time.
How is that different from FB/Google's login services? The only apps that are required to support Sign in with Apple are those that also support FB/G/etc sign in, so those companies have already chosen a path...
Re: Why we won’t be supporting Sign in with Apple
#17If you implement Sign In With Apple, you don't have a relationship with your customers anymore. They're Apple's customers, and Apple can take them away at any time.
It's good that you read Hey's blog post and are repeating it here, but it's not very accurate in this case.
Specifically, if you implement Sign In with Apple, then they are still your customers as much as ever, they just might choose to hide their information from you because they don't trust you, which means that the power in the relationship is transferred to the user instead of the app developer.
Re: Why we won’t be supporting Sign in with Apple
#18This 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.…
I've never seen an app that required a FB or Google login. It was always possible to use email+password.
Re: Why we won’t be supporting Sign in with Apple
#19> One problem is that most Apple IDs are tied to an iCloud email address.
Is that actually true? None in my household are.
Re: Why we won’t be supporting Sign in with Apple
#20Earlier quoted context omitted.
Well, that, and also if they don't remove FB login, then the would be required to also implement Sign in with Apple. They didn't want to implement Sign in with Apple, so they had to remove FB login.
Which is a pretty anti-competitive move on Apple's part. They're essentially using their control of the iOS ecosystem to benefit unrelated products. I seem to remember that those kinds of actions didn't work out well for Microsoft :)
Apple takes many anti-competitive and consumer-hostile actions. They can freely get away with it, though, as they aren't a monopoly.