Live data from Hacker News

Why we won’t be supporting Sign in with Apple

blog.anylist.com

481–485 of 485 posts

Re: Why we won’t be supporting Sign in with Apple

#481

Earlier quoted context omitted.

I can't answer that. However, if you go to appleid.apple.com to create a new AppleID, you must use an existing email address. When I create a new user account on the mac, it asks the new user if they want to create an AppleID. The default is to use their existing email address. You must specifically select an option to get an iCloud account. If you purchase an Apple device, you again have the option of an iCloud acco…

Whatever the UI is now, doesn't speak for what it used to be over the years. The cumulative effect matters. There are tons of people with @icloud.com email addresses that they never use who will fall into the login / customer support traps described in the article. But sure let's not even acknowledge those very real problems, deny Apple's role in this, and blame users. That will surely solve the issues.

I think you are missing the point and are perhaps letting this app vendor create an impression of a large problem based on anecdotal evidence. Perhaps they are just whining because they don't want to lose all that data. I have no idea that that is the case, but we can't rule it out.

Tons of people falling into these alleged traps? Really? What is that based on?

Apple is saying they want their platform to support personal privacy. If an app on their platform offers third party sign-ons that are known to abuse personal privacy, that app must offer Apple's solution that respects personal privacy. Despite it being an imperfect solution, I personally am thrilled that I have that option and I'm happy with Apple taking a stand on one of the most important issues today and going forward.

Some occasional customer support issues vs. providing customers with a real solution to significant privacy issues. From a user perspective the value of having such a choice is high.

Nobody is blaming users. Frankly, I think users are smarter than we typically assume. The support situation is really pretty trivial. If you save the onboarding email sent to the anonymized email address, you've got all you need to interact with an app customer support. People will quickly learn this and get on board if they want the privacy benefit. Its just not a big deal.

Apple's role is about increasing privacy and respecting their user's right to privacy. I fully acknowledge that. Does this create some hassle for app vendors? Yes, but I don't care about that in relation to the greater gain.

Re: Why we won’t be supporting Sign in with Apple

#482
post #343

Earlier quoted context omitted.

If only there was a decentralized option that has already solved this... We could call it OpenID or something like that... Oh, wait..

You also have IndieAuth that is slowly gaining more adoption. https://en.wikipedia.org/wiki/IndieAuth https://indieauth.net/

Cool, that looks awesome, thanks!

Re: Why we won’t be supporting Sign in with Apple

#483
post #454

Earlier quoted context omitted.

Verification is only one part of the problem. The other is communication. If I can't contact my customers, how do I support them (e.g. report a security problem)? If my customers can't communicate which account is theirs, how do we help solve problems? Email addresses and/or phone numbers make this a lot easier.

tl;dr email isn't needed, people are just used to it. It's a fair point, and perhaps its one that the likes of Apple SignIn should solve. On the one hand, even Microsoft and Apple send me heaps of spam under the guise of "communication" and I don't want them to have my email address if I can avoid it. The OP says they have trouble with support, but they can (and it sounds like do) tell people to just check their Appl…

Call us back when you get the entire internet to stop using emails and phone numbers for communication. There really isn't a reasonable other option right now.

Re: Why we won’t be supporting Sign in with Apple

#484
post #327
post #277

Earlier quoted context omitted.

Not necessarily. I have an app with 1,000 users, and about 99% of them choose to obfuscate. My app isn’t untrustworthy at all either. It’s an experimental app which attempts to let users create an iOS app on iOS. My suspicion is that people choose to obfuscate because it’s what’s selected by default.

Why is it a problem for you?

Isn’t a problem. I chose to use Apple sign in because I didn’t need email other than for having a way to later setup billable accounts. I plan to introduce a subscription option in a month or 2 and thought there’d be less friction if people already signed up.

Re: Why we won’t be supporting Sign in with Apple

#485
post #484
post #327

Earlier quoted context omitted.

Why is it a problem for you?

Isn’t a problem. I chose to use Apple sign in because I didn’t need email other than for having a way to later setup billable accounts. I plan to introduce a subscription option in a month or 2 and thought there’d be less friction if people already signed up.

update: I've now removed the login entirely until it's absolutely needed. This change will go live in the next few weeks
Post reply on HN