Because Apple prioritizes their customers over developers.
If they didn’t force developers to adopt this, they would never do it as it’s in their interest to harvest the e-mail addresses of their customers.
If they didn’t force developers to adopt this, they would never do it as it’s in their interest to harvest the e-mail addresses of their customers.
the rule seems somewhat orthogonal to developers getting emails. Developers can still request login by the old school email-and-password with (or without) sign-up verification by email. On the other hand, some third-party logins don't give developers their users' contact information (just a token to verify that they're on their platform with no authentication permissions, or a dev can request that this be so else the third-party will inform the user that the dev is requesting their contact info).
So anybody who is using Sign In with Apple trusts Apple to do the right thing.
Besides, what monopoly? Apple is perfectly happy with other single sign ons — provided you also offer Sign In With Apple.
It is pretty standard "embrace, extend, and extinguish" strategy. Similar to what's happening in the browser market. They are waiting for majority of the apps to have their sign on and majority of users use Apple sign on, then update the policy to disallow other methods.
I mean I don't have any issue of Apple doing these in their own ecosystem, but at least don't be so hypocritical or naive when defending them.
If the only other options you provide are Google or Facebook, you (as an app developer) clearly doesn’t care that much about privacy.
Apparently Apple doesn’t feel that any other providers care enough. That’s why they’re mandating the use of their privacy-focused solution.
They are using their app store monopoly to gain a foothold in the single sign-on business. You could try to claim that there's no business there but look at how Microsoft got spanked for giving away a free browser. Now the Apple has over half the phones in the United States, I'm looking forward to them getting spanked very soon hopefully.
Yeah, it's practically the same thing if you just ignore the basic facts of the case.
That's exactly the kind of behavior that Apple is exhibiting here.
It's pretty easy to come along and say that I'm "ignoring the basic facts of the case" though without presenting any facts of your own to back that up. So let's hear your take now.
[0] https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....
But again, Sign In with Apple sits in addition to the other offerings, it doesn’t replace them, and in no case are developers expected to be unable to offer regular sign in with email.
To my mind, you’re not wrong, but making a rather different argument.
They don't, and aren't trying to. They are trying to disrupt the Google/Facebook duopoly in the SSO space. Devs are free to require new accounts that they have the email for, just not outsource it to FB/Google.