Live data from Hacker News

Why we won’t be supporting Sign in with Apple

blog.anylist.com

131–140 of 485 posts

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

#131
post #114

Your iCloud account does not have to be paired with an iCloud email address. Mine is paired with my regular email address.

Yes, but many are. This app in particular needs an email address that is actually checked.

From what others have said, they also need it to add to their marketing list....

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

#132

For me it sounds like they didn’t like the additional work Apple made them do, that would actually benefit the end user - I love sign in with apple, the best part is the unified workflow without typing on a phone. I dream of a world when I won’t have to type passwords on a phone anymore.

Their blog post is well written and explains point by point why implementing it would be problematic for them AND for end users. Strange that you arrived at the conclusion "they didn’t like the additional work Apple made them do"

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

#133
post #28

Earlier quoted context omitted.

Transferred to Apple more than the user.

Apple operates on behalf of the user. Apple saw users with throwaway/burner email addresses and said why not make this easier for everyone?

Apple operates on behalf of profit. As it should.

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

#134

Earlier quoted context omitted.

That ship sailed long ago. Apple basically has apps and app-developers by the balls, not to mention the 30% extortion money they try to get not just for app purchases but any transaction done within the app, so much as even banning an app from telling the user that they can do the transaction elsewhere. It makes my blood boil but from the discussions I see on HN about it, most people here seem to be more or less ok w…

It’s not any transaction. It’s any digital transaction. You can sell physical goods and services either without giving Apple any cut, or by using Apple Pay and Apple just gets your standard credit card processing fee. Does Walmart let you sell your product in their store and say you can look at it there but get it cheaper from Amazon?

My app is not the App Store. The user has already paid to download my app from the App Store and Apple has gotten 30% of the cut. What users do on my App after that is none of Apple's business, though of course Apple would like to claim otherwise.

Similarly, once I have bought something from Walmart I can use it as I wish. Our business transaction ends there, so your analogy isn't really apt.

> Does Walmart let you sell your product in their store and say you can look at it there but get it cheaper from Amazon?

Funny you say that, because Walmart and many other brick-and-mortal retailers will happily price-match Amazon and each other. You know why? Because they are not a monopoly or pseudo-monopoly and so need to do good by their users to compete.

Of course you can justify Apple's behavior any way because you can claim that I am on an iPhone so I am on their property or something and so they are my overlords but that is precisely what users here are trying to argue against.

Or to be honest, you don't even need to justify it that way. The magical market justifies it because the fact that these apps are on the Apple ecosystem means that staying on it is better for them than staying off it. And no other justification is necessary. And you would not be wrong.

But people have a moral intuition about these things based on how they see the world work, and so they have an intuitive sense for when something seems 'off', even if the market seems like it's working. That's why they complain against things like exorbitant pay-day loans despite them too being an example of a market that seems to be working.

Last I checked, I did not get an iPhone on lease from Apple. This attitude where just because I am on an iPhone means I owe Apple in perpetuity needs to die.

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

#135
post #42

Earlier quoted context omitted.

I love it. With password managers becoming better and by owning your domain, it almost feels like a self-sovereign identity system. It would be great if services would implement better support for browser form auto-fill, and ask the minimum amount of information during signup. That way it would be very little hassle to signup for a service.

And Apple has integration points with third party password managers.

Only ~1-2 apps of the several dozen I use support them. For folk that aren't super tech savvy, still a struggle

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

#136

> Furthermore, if there are platforms where AnyList doesn’t support Sign in with Apple, like Android, and someone wants to log into their account, they’d have to know their privaterelay.appleid.com email address. (And that certainly won’t be easy to find if you no longer have an iOS device.) And then they’d have to create a password with us, since they wouldn’t be able to sign in using Sign in with Apple. I’m an avid…

Sign-In with Apple is a (mostly) standard OpenID Connect provider that works everywhere (and works just like sign in with FB, Google, et al from a technical implementation), including the Web and Android. It's an interesting miscommunication or misunderstanding (and I was not surprised to see it in this article) that applications and developers think the "Sign in with Apple" button should only show up on Apple device…

If you read the article, you'd see they address the reason they cannot implement it on Android yet. Apple hasn't provided documentation for it. Apple doesn't seem to be taking it seriously.

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

#139
This seems to be a common problem, made more visible when using third-party authentication, that your application has taken the concepts of "Account" and "Authentication Method" as if they were the same thing.

It appears that the "account ID", "preferred contact method+address" and "authentication ID" are all the same here - which then creates the "account management code into a rat’s nest" scenario they describe in the post.

If an Account is, by design, it's own entity - you should be able to have 100 different authentication methods linked to that same account without impacting any other flow or part of the application.

Turn on and off authentication methods would also allow for seamless transition for users, without worrying about when one method is about to be killed.

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

#140

Worth noting that AnyList automatically subscribed me to a marketing list without double opt-in or any kind of consent, which is exactly the kind of behaviour that makes me not want apps to have my real email address.

They mention customer support so many times in that article, but it's a grocery list app! When is the last time I asked for support for the sticky note attached to my refrigerator? I don't doubt that there are indeed customers who need support from time to time, but surely it's a small minority. These seem to just be contrived arguments to protect their customer data selling bottom line.

Yep, my feelings exactly after reading. All this whining happens only when your business is very dependent on specific information that gets taken from you.
Post reply on HN