Hacker News Reader

Comment by dublinben | Hacker News Reader

I'm sure we'll continue to see more apps that saw minimal benefit from Facebook login drop it as Apple's June 30th Sign In with Apple deadline passes.

https://developer.apple.com/news/?id=03262020b

View on HN

It's not clear how the Apple thing is related to Facebook, as Facebook isn't mentioned on that page.

As a designer/developer, I'm psyched to drop dependencies. If I see that FB login is just 10% of sign-ins, I'll likely drop it. If I see it is just 20% of sign-ins, I might drop it.

I can imagine a lot of apps shifting to just two login options: direct with email, and Sign in with Apple. (All new products I work on already doing this.)

What do you do if your app is cross platform, for example iOS, Android, potentially a web app as well?

I'm psyched to drop dependencies too. Apple would be very high on that list if a history of power moves like this hadn't prevented me from accepting an Apple dependency in the first place.

Any app that supports login using external provider like Facebook, Google etc. must support Apple sign-in.

I know a few apps I manage had this conversation. Had another part of the business not added it to their side (and dealt with all the complications, customer service, and policy stuff Apple has introduced), pulling out FB sign-in would have been our best option. We didn't have the resources to comply with their product rollout.

Where I work, we almost pulled Facebook sign in for the same reason. I'm currently heading the Sign In with Apple integration project, and it was a godsend to get that deadline extended

Reply on news.ycombinator.com