5 ms·
My philosophy is exactly the opposite. Allow anything as email address and make it as simple as possible for the user to sign up to use my application. This me
by kinkdr 10y ago
My philosophy is exactly the opposite. Allow anything as email address and make it as simple as possible for the user to sign up to use my application.
This means, no email validation, no address verification emails, heck, I don't even have a password confirmation field. One field for name, one for email and one for password and you are in.
If 10% of the users don't trust me with their real, or even throwaway email address, so be it. My goal is not to collect email addresses, but to have users use my application and add some value to their life.
If another 10% of them enter a mistyped email, they will figure it out eventually and change it if they care.
- Karunamon 10y agoeh, password confirmation at least has a valid reason to exist - kinda sucks when someone's first hit on your site is having to go through a recovery, and if they didn't provide an email address, they're screwed.