The place of email and password sign-in in apps

With the prevalence of Third-party app sign in, what is the point of having an email and password sign-in option in your apps? It sort of adds a lot of maintenance and security issues. I have searched the web for articles on this to no avail. What are your thoughts?

Comments

[Dimitrios Desyllas]

On the other hand you rely on 3rd party services for the authentication that may also process the data in a manner that your your users may not want to. For example let me assume that instead of password you use google (gmail etc etc) for authentication in your app then:

1. You enforce your users to have google account in order to use your app.
2. You make your user to let google know that use your app, an information that the users may not want to give into google. Also google may use it in order to provide more ads to your users that also users may not want to.

[theamiro]

Thank you. Though the first one: most people already use these services. Not just google. Say for example, I’m an iOS dev and thus Sign In with Apple works cause for you to download the app, you already have an Apple ID. So providing multiple SDKs for that purpose: sign in with Google, Huawei, Twitter, Facebook, phone number, github, etc etc. For example this platform already implements that. You can sign in/up using either twitter or GitHub only.

On info privacy, 👏🏾 That’s awesome. Thank you. Though, cookies may still be a sellout?

[Dimitrios Desyllas]

And because also via cookies google for example, may know that a user uses your app by giving also the authentication confirmation via OAuth also aids google to confirm its targeting.

[Dimitrios Desyllas]

By google I mean any service that offers tagreted advertisement.