Wired:
I spoke to a variety of developers who make apps for iOS and Android, one of whom asked to remain anonymous because they aren’t authorized to speak on behalf of their employer. Some are skeptical that Sign In with Apple will offer a solution dramatically different from what’s already available through Facebook or Google. Apple’s infamous opacity around new products means the app makers don’t have many answers yet as to how Apple’s sign in mechanism is going to impact their apps. And one app maker went as far as referring to Apple’s demand that its sign-in system be offered if any other sign-in systems are shown as “petty.”
My first thought is I wouldn’t trust any developer who would use Facebook or Google login procedures but not want to use Apple’s as well.
Petty? I’m thinking that’s not what bothers some of these developers. It’s more like, “What, I can’t siphon all my users info as I please, give them no choice?”
I don’t think this Wired article was written in the best interest of consumers.
As a developer myself I think you’re absolutely right on that thought.
I could not agree with you more
Yup. In a post-GDPR world (and one with many Americans now pushing for similar legislation), I cannot imagine being the developer who thinks “oh no, my data siphoning!” That ship his sailed. Fix your business model and avail yourself of Apple reducing your liabilities.
“My first thought is I wouldn’t trust any developer who would use Facebook or Google login procedures but not want to use Apple’s as well”
… I agree COMPLETELY!
I agree with the sentiment but I think there is a little more to it than what appears on the surface. If the developer has been using FB or Google then things like the sign-up flow or user management has been nailed down. Basically they are using those services as an identity provider since they don’t want to maintain their own OAuth server or pay Auth0 (my fave).
I suspect they are wondering if the nuts and bolts admin will be more difficult. They won’t really know until they get their hands on it. I think it’s more caution than negative reactions since this type of stuff is finicky and generally a pain in the ass for most developers.
No doubt some developers would be willing to take kickbacks, so Apple has to be tough and force their hands to protect our privacy. I agree with you Shawn. Any developer who has reservations is not getting me to use their junk.
also as an enterprise developer — these people, as well as WIRED, are jokers. that they not see the value to themselves while ignoring the value to users (privacy – we’re talking about facebook!!) is absurd. our privacy matters. even if it seems like the same amount of code to use google/facebook authentication.
beyond lame.
Well, I wouldn’t expect it to offer anything dramatically different for the developer or app publishers. It’s supposed to be dramatically different for the end user in terms of privacy.