I’m trying to decide what to put in a dialog box that tells the user their login doesn’t work, there is probably a duplicate. The system uses email addresses as user names, then requires a password.
Right now, I’m using ‘Email Login’ but that just sounds stupid.
For instance:
1) Application Starts, recognizes that it has never been run. 2) Prompts user to create a new account. 3) User puts in an email address and password to use as their new credentials. 4) Well, looks like they’ve already got an account probably. (This is the most likely case the account creation would fail but I’m using an API and I can’t be 100% this is why it failed) 5) I ask them to try again with a different ’email login’.
Could not create account - try a different email login ! After I check with the API provider, I’ll probably try to detect that it is in fact a duplicate account and ask them to try to authenticate that account with a password.
Tell them explicitly that their email address is already in use.
Call it an email address, thats what the user thinks of it as. The fact that you are using it as an id or a database primary key or a hash key is irrelevant to them.