No more duplicate accounts (cos you can't recall which option you chose)

Hey everyone 👋

I'm working on a solution that makes Internet browsing smoother and less stressful and I'd really appreciate anyone's feedback on this idea.

Problem:
Namely, do you also have situations in which you can't recall what option did you use to register on a particular site? Google? Apple? Email? Twitter?

It happens to me all the time and it's the most annoying thing I can think of.

Solution
Right now, I'm working on a solution that would tell you, every time you want to log in on a site, which option you chose. So no more duplicate accounts in the same service.

My questions are:
Is it a problem that you have?
Is it worth solving (in your honest opinion, of course)?
Would you pay for such solution?

I'd love to hear your honest feedback.

Thanks in advance!

Jakub Kliszczak

posted to

Ideas and Validation

on May 23, 2020

Say something nice to jacobk…

Post Comment

1
Hi Jakub,

Interesting idea. I've implemented something similar in past projects from the supplier's side, but never from the user's perspective.

I personally think the burden of solving this problem should be on the developer - they should support login from multiple options for the same account on the website.

Often a social login is simply to 'prove' you own the associated email address, and where that proof comes from can be changed very easily. Here's an example:
- A project starts with only email / password login. To prove they own that email address, we send them a verification link when they first sign up. To sign up with alice@example.com, Alice would have to click the link in her inbox to verify she owns the address.
- The project then adds sign in with Google, which allows us to get the user's email address simply by making an API call. To sign in with alice@example.com, we can simply request the email of the logged in user that Google has already verified. It doesn't matter if Alice signed in with email/password before.
- Same thing with GitHub - even if the Alice signed up with Google or email/password, all we care about is if alice@example.com is who she says she is.
- Later Alice could choose to revoke OAuth permissions on GitHub and Google, and go back to email/password sign in. Same email address, same account on our side.
glynnforrest

·
5 years ago
·
Reply
1. 1
  
  That's an interesting point. And I agree that the solution could be or even should be provided by the dev side. Yet, there isn't one and so I was thinking about a 3rd-party tool to solve it.
  
  I reckon many ppl kinda solve this problem by sticking to the email+password combination and using 1password or similar password manager. Yet, it doesn't help when you have many social logins and combine different methods.
  
  jacobk
  
  ·
  5 years ago
  ·
  Reply