4 ms·
It could be hurting you by opportunity (no way to ever know) Imagine a single developer who has an idea to make a cool app. Because data linking is a core part
by gretch 7y ago
It could be hurting you by opportunity (no way to ever know)
Imagine a single developer who has an idea to make a cool app. Because data linking is a core part of the app, they will either implement Sign in with Facebook or Google. They don't even have enough cycles to implement the other one, and they certainly don't have the time or energy to implement Sign in with Apple, so the app never gets created.
Well that app could have really benefited a niche audience potentially and we now you'll never have it.
- kyralis 7y agoThis is a completely invalid scenario. You are only required to implement Sign In with Apple if you use some other third-party sign-in system. If you implement your own sign-in system, there is no requirement for you to implement Sign In with Apple.
- gretch 7y agoI don't understand your comment. I addressed that part in my comment?
- fyfy18 7y agoThat sounds like a very unrealistic scenario. This is using OAuth2 behind the scenes (same as Facebook and Google login), so you only need to integrate another provider, not integrate a completely different authentication system. That means you need a couple of URLs, a secret key, and a new button on your login screen. I'm not a mobile developer, but I do run a SaaS that has Facebook and Google login, and adding Apple login would take me a couple of hours tops. I can't see how it would be magnitudes different on a mobile app.
- Marsymars 7y agoI don't quite understand what you mean by data linking. Do you mean an app that request additional permissions beyond login to your FB/Google account in order to do FB/Google specific things?