Ask HN: Require a sign-up or allow anonymous/guest users?
When you launch a web application, more users will try it out if they don't have to sign up first.
Logically, if they like it enough they'll eventually sign-up to use more features.
But when you require a sign up in advance, you can:
1. Stay in touch with the user (contact for feedback or when features available)
2. Have better analytics (also, the sign up itself is a signal?)
3. Use social features
Any insights on the subject?
Any rule of thumb on where to draw the line and require a guest user to "convert"?
12 comments
[ 3.0 ms ] story [ 39.4 ms ] threadMy idea that I haven't gotten to implement yet: Make it possible for the user to get started without logging in, then force them to create an account after they've started playing around.
The particular application that I specifically want to try this on is going to be a document-oriented application. I'll let the user jump in and start creating something without creating an account, but then make the user create an account (or log into an existing account) to be able to save their work. If you've already spent even two minutes creating something, having to type in an email address and password seems trivial compared to having to start over again if they want to come back later. (That's the theory, at least.)
The key in my mind is to get the customer invested in the application (even slightly) before forcing them to make an account.
But for young applications, it is important to get in touch with the users, and try to engage them-
There are some start-ups dedicated only to automatically send users email after some conditions, and most of the service I use do it manually too (like sending you "we noticed that after you built your form you didn't publish it for a month, care to tell us why?")
If you don't know who your users are, how can you get the negative feedback?
Getting feedback only from the people who sign up is going to be skewed to the positive side, and you'll have a problem realying on analythics for guest users (because some "guest users" are can be the same user- from different machine, or after cookie clean)
All of the websites competing in my space require a signup except mine. Their products may be way better but I don't bother to check and neither do my users.
In fact I think you can make a viable business just by taking popular websites and working out how to implement them without user accounts.
This gives people a chance to try the product without making a time investment. We are getting close to 1 million users (not including guest users) so it seems to be working pretty well for us.
Our product is JotForm if you would like to see how it works. www.jotform.com
How did you get feedback/nisights about users that started to use your product, but fall of the funnel before entering the email address from some reason?
And I don't mean "disable your account until you come to your senses" but "it's like you were never there."
If you can build value in your product without forcing me to login, I'm more likely to want your product more because I've been sold on it. I think thats important, I should want to sign-up. This could be via a product tour, guest account, even a demo video. Ultimately I'm window shopping so give me a reason to come inside.
No matter what though whether you allow anonymous users or require a sign-up, measure the funnel between guest-user and registration. Find out where your users are bouncing and where you could improve the onboarding. Is the homepage persuasive enough? Is the sign-up page itself losing users? Measure, iterate, and repeat. I'm sure there's quite a bit to learn.