When Apple announced a new ‘Sign in with Apple‘ button as part of iOS 13, the move was warmly welcomed by users, offering an option that combines convenience with privacy.
However, one requirement and one suggestion by Apple are raising eyebrows …
It’s common for apps to offer the option of third-party sign-in via something like Google, Facebook or Twitter because it’s much more convenient for users than having to create a separate login for every app. There are, however, two problems with this.
First, the third-party platform will pass your email address to the developer – you’ll be asked to approve this, but won’t be able to proceed with the login unless you agree.
Second, the platform itself will learn which apps you are using. This could be a problem with some sensitive apps, but even the aggregate view of all the apps you use could tell a platform quite a lot about your life.
Apple’s solution: Sign in with Apple
The ‘Sign in with Apple’ button aims to solve this problem. Apple offers the option of sharing or hiding your email address with the developer. If you choose the ‘hide’ option, Apple creates a single-use email address for you – used only with that app – and passes that to the developer. Emails sent to that address are then forwarded to you by Apple.
What this means is that any time you want to opt out of emails from that app, you can deactivate the single-use address. Plus Apple already knows which apps we use, so we’re not passing that information to anyone new.
The concerns about Apple’s terms and conditions
Apple has introduced one condition for developers, and makes another … suggestion.
The condition is that app developers must offer the option of ‘Sign in with Apple’ if they offer any other third-party sign-in. So if a developer offers sign-in with Google, Facebook or Twitter, they have no choice but to offer Apple’s version too.
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.
That’s a very different position to today, when a developer could, for example, choose to allow sign-in via Twitter only.
But Reuters notes that Apple has a second requirement– sorry, ‘suggestion’ which goes beyond this.
Apple Inc will ask developers to position a new “Sign on with Apple” button in iPhone and iPad apps above rival buttons from Alphabet Inc’s Google and Facebook Inc, according to design guidelines released this week.
The move to give Apple prime placement is significant because users often select the default or top option on apps […]
Apple’s suggestion to developers to place its login button above rival buttons is part of its “Human Interface Guidelines,” which are not formal requirements to pass App Store review. But many developers believe that following them is the surest way to gain approval.
As The Verge suggests, Apple might be tempting fate at a time when the company is already coming under the microscope for alleged anti-competitive practices.
I don’t know how precisely to weigh the value of more private login tools against the cost of making an entire developer ecosystem captive to the policy whims of the world’s biggest company. But perhaps that’s where our actual regulators — which is to say, Congress — should intervene. As the House of Representatives begins an inquiry into our tech giants, I hope they will.
Personally, I’m happy enough with this as a user, and will choose Apple’s sign-in over rival ones, but I also agree with Casey Newton that Apple is prodding antitrust regulators with a pointy stick by doing this. What’s your view? Please let us know your thoughts in the comments.