3 ms·

I think you may be misunderstanding what he's saying about Android. Here's what he wrote: > Apple is going to leverage its monopoly position as app provider on

I think you may be misunderstanding what he's saying about Android. Here's what he wrote: > Apple is going to leverage its monopoly position as app provider on the iPhone to force developers (who use 3rd party solutions) to use Sign In With Apple. Keep in mind, that also means building Sign In With Apple into related websites, and even Android apps, at least if you want users to be able to login anywhere other than their iPhones. The developer will be required to support "Sign in with Apple" on the iPhone - otherwise Apple will reject your app. Once a user creates an account with "Sign in with Apple", the developer has a choice. They can either: 1. Exclusively support iOS, or 2. Add "Sign in with Apple" across all platforms they support. Both of these advantage Apple.

r00fus 7y ago
What's audacious is that Ben thinks Apple hasn't considered the antitrust implications of the above hypothetical. I really doubt they'd force developers to use Sign in with Apple, instead they'll just make it desired and profitable. My guess: this goes as far as Apple Pay app integration does now - some but not all apps, and in the least required.
- scarface74 7y ago
  How is it in any more "audacious" for Apple to force apps to use Apple's authentication for their platform than it is for Amazon to force you to use an Amazon account to use their platform (retail and AWS), or the console makers to do the same?
- jonas21 7y ago
  Apple is telling developers that Sign In with Apple will be required if you support Facebook, Google or any other third-party login: > Sign In with Apple will be available for beta testing this summer. It will be required as an option for users in apps that support third-party sign-in when it is commercially available later this year. https://developer.apple.com/news/?id=06032019j https://developer.apple.com/news/?id=06032019j
- hobofan 7y ago
  > What's audacious is that Ben thinks Apple hasn't considered the antitrust implications of the above hypothetical. Why not try it? Worst case they have to loosen requirements, and have to pay a tiny fraction of their cash reserves as a fine. Antitrust hast lost its teeth a long time ago. So there is a potential huge reward with low risk. Not saying that that's moral and should be done, but that seems to be the sad status quo.
- pwinnski 7y ago
  > I really doubt they'd force developers to use Sign in with Apple If developers allow any third-party authentication (Google, Facebook, etc), they must also allow Sign In with Apple. This is a June 3 update, and it will be a requirement before the end of the year.
ascagnel_ 7y ago
This only applies to apps that use third party logins. If you roll your own login (and only your own login), then you require zero changes. The "Sign In With Apple" implementation, at least on the surface, appears to be a standard OpenID process -- the same thing that Facebook & Google use if you're offering a log-in through those accounts -- so actual dev time should be pretty minimal.
HillaryBriss 7y ago
this may be a naive/dumb question, but I'll ask anyway: is the third option (support "Sign in with Apple" on iOS, but not on android) really that unappealing to app developers? it kinda seems like only a really small fraction of an app's user base would have an Apple account and an iPhone or iPad and an android device anyway. and since this new "Sign in With Apple" will require additional android dev work to roll out, and since it prevents app developers from getting all the info they want about their user, wouldn't some of them just omit it from their android apps?
photojosh 7y ago
> Both of these advantage Apple. And privacy-conscious users. Which is me. I always create an account using email instead of using FB/Goog login, but now I don't have to share my real email address for any service that I just want to try out.

r00fus 7y ago

What's audacious is that Ben thinks Apple hasn't considered the antitrust implications of the above hypothetical. I really doubt they'd force developers to use Sign in with Apple, instead they'll just make it desired and profitable. My guess: this goes as far as Apple Pay app integration does now - some but not all apps, and in the least required.

scarface74 7y ago
How is it in any more "audacious" for Apple to force apps to use Apple's authentication for their platform than it is for Amazon to force you to use an Amazon account to use their platform (retail and AWS), or the console makers to do the same?
jonas21 7y ago
Apple is telling developers that Sign In with Apple will be required if you support Facebook, Google or any other third-party login: > Sign In with Apple will be available for beta testing this summer. It will be required as an option for users in apps that support third-party sign-in when it is commercially available later this year. https://developer.apple.com/news/?id=06032019j https://developer.apple.com/news/?id=06032019j
hobofan 7y ago
> What's audacious is that Ben thinks Apple hasn't considered the antitrust implications of the above hypothetical. Why not try it? Worst case they have to loosen requirements, and have to pay a tiny fraction of their cash reserves as a fine. Antitrust hast lost its teeth a long time ago. So there is a potential huge reward with low risk. Not saying that that's moral and should be done, but that seems to be the sad status quo.
pwinnski 7y ago
> I really doubt they'd force developers to use Sign in with Apple If developers allow any third-party authentication (Google, Facebook, etc), they must also allow Sign In with Apple. This is a June 3 update, and it will be a requirement before the end of the year.

ascagnel_ 7y ago

This only applies to apps that use third party logins. If you roll your own login (and only your own login), then you require zero changes. The "Sign In With Apple" implementation, at least on the surface, appears to be a standard OpenID process -- the same thing that Facebook & Google use if you're offering a log-in through those accounts -- so actual dev time should be pretty minimal.

HillaryBriss 7y ago

this may be a naive/dumb question, but I'll ask anyway: is the third option (support "Sign in with Apple" on iOS, but not on android) really that unappealing to app developers? it kinda seems like only a really small fraction of an app's user base would have an Apple account and an iPhone or iPad and an android device anyway. and since this new "Sign in With Apple" will require additional android dev work to roll out, and since it prevents app developers from getting all the info they want about their user, wouldn't some of them just omit it from their android apps?

photojosh 7y ago

> Both of these advantage Apple. And privacy-conscious users. Which is me. I always create an account using email instead of using FB/Goog login, but now I don't have to share my real email address for any service that I just want to try out.