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"?
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"?