Skip to content

[Discuss] Don't save credentials for non-email providers #1154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
samtstern opened this issue Feb 16, 2018 · 2 comments
Closed

[Discuss] Don't save credentials for non-email providers #1154

samtstern opened this issue Feb 16, 2018 · 2 comments

Comments

@samtstern
Copy link
Contributor

The SmartLock team has learned over the years that IDP credentials that don't include a password or token actually do more to confuse than help.

We could change our strategy:

  • Only save email credentials
  • ^ and also save Google credentials since we can use them to get an ID token
  • ^ and also save Phone number credentials

But I don't think Facebook or Twitter credentials really have any value.

@SUPERCILEX
Copy link
Collaborator

Huh, I thought I had responded to this, but I guess not. Anyway, I totally agree with you! 😄 In fact, I just ran into this a week or so ago: Smart Lock auto signed me in to Twitter which was really confusing since they aren't the best provider and use a Webview without autofill support. TL;DR: it was annoying and I would have much preferred Google or email sign-in which would have been faster. To compromise, I created #1166 which still saves the credentials so users know they have an account with an app, but it doesn't suggest using unpleasant IDPs to optimize the UX flow.

@samtstern samtstern added this to the 3.3.0 milestone Feb 27, 2018
@samtstern
Copy link
Contributor Author

This issue has been fixed and released in 3.3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants