3 ms·

Cool idea. It will require the user to have access to their mail right then and there, i.e. maybe they're on a public machine and don't use GMail. Another thing

Cool idea. It will require the user to have access to their mail right then and there, i.e. maybe they're on a public machine and don't use GMail. Another thing you could do is skip the registration altogether. Let the user into your app using a single big button on the home page. Then, once they've interacted with your app, progressively ask them for the vital info you need. You walk the wire for a few minutes where a user could leave without registering, but I'm sure the upside in conversion rate would be worth it. I've just (literally yesterday) launched a different kind of contact management app at https://szpil.com https://szpil.com that has an experiment going with this (one-click button, deferred registration).

jorangreef 16y ago
Another idea I'm mulling over is using a person's real name for signing in together with their password to provide enough entropy, then enforcing that the password be long enough etc. so that the name/password combination gives you something unique enough to authenticate with. The reasoning behind this being that typing your real name in is somehow more personal, more gratifying and more memorable than typing a username/email. Another slant on this is that people have more than one email address which the authentication mechanism could take into account. The final idea is allowing any of: real name/email(s)/id as a username. Although name is great for interface use, id/email are better for programmatic use.
dublinclontarf 16y ago
I was planning to do this anyway, as the user goes through the app, get a nibble of information each time. But with only using an email, it instantly creates an account for them. Sending a login link also gives them something to keep. And if they come back years later(after just using) it should be easy for them to re-authenticate.

jorangreef 16y ago

Another idea I'm mulling over is using a person's real name for signing in together with their password to provide enough entropy, then enforcing that the password be long enough etc. so that the name/password combination gives you something unique enough to authenticate with. The reasoning behind this being that typing your real name in is somehow more personal, more gratifying and more memorable than typing a username/email. Another slant on this is that people have more than one email address which the authentication mechanism could take into account. The final idea is allowing any of: real name/email(s)/id as a username. Although name is great for interface use, id/email are better for programmatic use.

dublinclontarf 16y ago

I was planning to do this anyway, as the user goes through the app, get a nibble of information each time. But with only using an email, it instantly creates an account for them. Sending a login link also gives them something to keep. And if they come back years later(after just using) it should be easy for them to re-authenticate.