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