HN Explorer

Ask HN: Pros and cons of asking for email during user signup

3 points by strapp ↗ HN
Hi, I am creating a new application and was wondering how to implement user login. For the app, I need to create user - but for MVP, there is no inter-user / social interaction. If that is the case, should I setup user creation with or without email addresses.

I would like to collect email addresses for two reasons: 1. If users forget their password, have ability to reset password 2. Later on if I add any social interaction - I feel having email addresses would give some authentication (and avoid spam).

Marketing / sending reminder emails / notifying users of new features etc (similar to what Linkedin / FB does) is also good, but given little marketing experience of the team, that is good to have but not sure how to implement it correctly.

Thus I feel, in the beginning we may just end up collecting emails without real use of it for marketing.

After reading this article on use of throw away emails (https://news.ycombinator.com/item?id=11595863), and my personal hesitation in joining sites where I need to give my true email, I am thinking if there is any real benefit about asking for email in creating an user account. I would like to hear what you have experienced as a end user or site owner. Would I be loosing potential users due to email requirement?

Thank you for your feedback in advance.

6 comments

[ 4.4 ms ] story [ 29.1 ms ] thread
dudul
As a user, the simplest thing would be to offer login via third party such as Google, Facebook, etc. I really have having to create an account each time I want to try a service. I much prefer linking my Google account and cancel app privileges if I want to stop using it.

Don't be too greedy with the permissions though, only require what you need (which should be almost nothing based on your description).

strapp
Thanks for the suggestion on 3rd party login. I will implement it.
dozzie
As a user, I really hate when a service doesn't allow me to create an account unless I tie it to Google or Facebook, neither of which I have nor want to have.
dudul
There are pros and cons. Personally I find it easier to link an account than to create a new password to store in lastpass. Obviously offering both is the most flexible.
hanney
A confirmed email address is probably the easiest point of user authentication.

Other than that - I totally agree with you that giving an email address away for sign-ups is pretty icky, but a necessary ickiness as there's not much else to choose from except OAuth (Google/Facebook/Twitter/LinkedIn/etc)

sharemywin
you need to create a user conversion funnel. Start with a landing page.

1. What problem are you solving?

Do you want to sign up more users to your website?

Click below to find out how to get more users to sign up for your web application.

2. find a compelling graphic that matches your domain

3. come up with 3 benefits and create sections for each:

Easy as pie We create a conversion funnel for you blah blah blah

We test it for you blah blah blah

etc.

Add a button, set up google analytics or some other thing to track the button click. I've used unbounce before for this. use something like wufoo to add a form to a page an collect emails or do a survey to validate your assumptions about your potential users.

The button is to see if people are even willing to click on a button to solve the problem you suggest you can solve.