4 ms·
What is forcing the sites that I'd want to use a fake email address with to use this? It wouldn't be in their interest to. They will just stick with their curre
by lghh 7y ago
What is forcing the sites that I'd want to use a fake email address with to use this? It wouldn't be in their interest to. They will just stick with their current SSO setup of Google/Facebook/whatever and never touch this, if they have SSO at all. I LOVE LOVE LOVE the idea, I just don't know if it will be useful and successful.
- jdminhbg 7y agoNothing is forcing them to, and lots probably won't. The carrot is the much lower friction for sign up for users. It's similar to Apple Pay, where you don't get credit card info, but you do get a much easier user flow that will get you more signups.
- DuskStar 7y agoBut will it be lower friction than login with Google or Facebook? It feels like it's more common for someone to have an account from one of those two than from Apple, and so "sign on with Apple" will never be able to be the only SSO option, while Google or Facebook could be. If the better (for the site) SSO options also have near-universal market penetration, what's the incentive to add Apple?
- awinder 7y agoI would venture a guess that apple/icloud accounts are the highest % account type amongst iPhone holders. All sorts of people have reasons for not having gmail / facebook / etc., but apple account setup is pretty prominent in device setup.
- DuskStar 7y agoSure, it might be the highest % among iPhone holders - but for a website, what portion of your users are going to be iPhone holders, and what portion of the Windows/Android crowd have Apple accounts?
- jdminhbg 7y agoYou don't have to implement it to the exclusion of other methods. There are plenty of merchants on the web with Apple Pay and also Paypal, straight up credit card numbers, etc.
- DuskStar 7y agoOf course you don't have to implement it to the exclusion of all others! But let's suppose that, say, 65% of users have a Google account, 75% have a Facebook account, and 40% have an Apple account - and the circles overlap such that adding Apple adds 10% to the total coverage. Now, if everyone who has an Apple account prefers it, and users with an Apple login yield 30% less revenue... gaining that extra 10% of users costs you revenue, because for every user you gained at 70%, three existing users cut their revenue by 30%.
- jdminhbg 7y agoIt's lower friction in that instead of having to click through an OAuth screen (and possibly re-enter your Google password), you just auth with FaceID/TouchID. And if you're writing an iOS app, then obviously the user has an Apple account.
- hobofan 7y agoI'm on Android, so I don't know how it works on iOS devices, but is reentering the Google credentials common? On my Android phone I doubt I had to enter my password more than 5 times in 2 years. And the OAuth screen would be required anyway, as they have also shown on stage.
- judge2020 7y agoSome apps don't open the "sign in with Google"(/facebook) popup correctly and so cookies end up not being enabled for that browser session, so users need to re-enter their google credentials. This is being fixed over time with proper implementation.
- jdminhbg 7y agoI frequently have to re-enter my Google credentials on the web on Google properties. I assume Android is storing those deeper in the OS, like Apple is storing your Apple credentials.
- jdminhbg 7y agoUpdate to the above, since it's too late to edit: It looks like Apple is in fact forcing you to support this sign in method, if you also support Google/FB/etc.: https://9to5mac.com/2019/06/03/sign-in-with-apple-requirement/ https://9to5mac.com/2019/06/03/sign-in-with-apple-requiremen...