Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by paxys | Hacker News Reader

Full thread

paxys·

And by extension all the services you sign in to using a (mandatory) sign in with Apple button.

View on HN

Actually, Sign in with Apple is one of the only things that still works.

I wonder if that is by design, or the fact it was an added service after Apple Card and maybe has some isolation.

I think they changed that after the EPIC case. Read my other reply on the subject.

The presence of the button is mandatory, your use of it is not.

Like Apple Card, like Facebook, like Google... ;-)

It’s not even mandatory unless the app offers other auth providers like Google and Facebook. If your app is based around old fashioned email and password sign-in you don’t need to include Sign In with Apple at all.

But ugh please do. From the end user's perspective I 100% do not want to navigate your app's account creation process bouncing back and forth between my email client and your website and your app (if the redirect works, which it probably wont), and I 100% do not want to give your app my actual email address. Just implement apple's Auth flow. It's not that hard.

Yeah, refusing to implement sign-in with Apple is anti-user: as a user I want to use sign-in with Apple (and Apple Pay) everywhere I can, forcing me to use some other product for these functions is not good UX.

And the reason the redirect is broken, more often than not, is because there's analytics sitting somewhere in the stack that's either not working properly because it's inherently brittle or because it's getting blocked by my adblocker.

I understand the need for analytics in some situations but registration, signin, recovery, etc are critical paths and every layer of indirection is playing with fire.

Reply on news.ycombinator.com