3 ms·
This isn’t a protection, it applied retroactively as well. Anyone who ever gave FB login AS AN OPTION is now required to create Sign In with Apple. I do not bu
by sturgill 7y ago
This isn’t a protection, it applied retroactively as well. Anyone who ever gave FB login AS AN OPTION is now required to create Sign In with Apple.
I do not buy their company line at all. This is simply Apple flexing its power in the App Space to require developers to implement an ecosystem very few would do of their own volition.
You can argue it’s a good thing. I disagree. But it is hopefully clear that Apple being able to wield this kind of power is indicative of monopolistic power in that marketplace.
- scarface74 7y agoExactly. Because developers are lazy. Apple shouldn’t put developer’s interests over user’s interests - and yes I am a developer.
- Marsymars 7y ago> This isn’t a protection, it applied retroactively as well. Anyone who ever gave FB login AS AN OPTION is now required to create Sign In with Apple. I don't think that's correct. Anyone who currently gives FB login as an option is required to support Sign On with Apple. If FB Login was previously an option, but was removed at some point, Sign On with Apple is not required.
- sturgill 7y agoThey clearly aren’t saying FB login is bad (or they’d just disallow it). They are saying “we want in on the game and we can force it on you.” I happen to have an app out there which we maintain security updates but aren’t adding new features. It was built with a FB login option. So now we either never update or have to implement features we don’t care about.