On: Developing a new app is unreasonable condition tha...

[duped]

As a user I'm a huge fan of it. It's how I use a lot of services these days without tying them to an email account.

[Andrew_nenakhov → duped]

I'm not a fan of any coercion. If their solution is good, people will use it voluntary, like all other social auth buttons.

[duped → Andrew_nenakhov]

I do use it voluntarily. I think more user choice is good.

[Andrew_nenakhov → duped]

You don't see contradiction here? Apple leaves you, the developer, no choice.

[duped → Andrew_nenakhov]

I'm not a developer in this situation, I'm a user. There's no contradiction. Apple makes my user experience better by forcing app developers to play by their rules.

[Andrew_nenakhov → duped]

200 years before it could be, "Slavery makes my life experience better by forcing slaves to play by the rules and serve me".

Your position is immoral. Coercion of any kind is bad. Approving it for egoistic reasons is equally bad.

You could freely support apps that do use Apple sign in voluntarily, but you like it that the developers are forced to provide it. Immoral and pathetic.

[rexf → duped]

While Apple's sign on sounds good on the surface, the reality is more user confusion.

For each app, you have a new button to consider / remember which one you used:

* Login with email

* Login with Google

* Login with Facebook

* Login with Apple

[duped → rexf]

I don't believe in treating users like they're dumb.

There's a "keep me signed in" feature too. Or if this is a serious source of confusion, use local device storage to keep track.

In practice I don't consider anything for each app. If it's worked I used gsuite. If it's personal I used Apple. OAuth is the new "same password used everywhere" but now we click logos.