Came here to say this too. I hate making new accounts. I was really hoping I'd click try and be greeted by a blank word processor with a blinking cursor. Instead I got yet another login screen and I bailed (for now).

I wish more people just used Google/OAuth.

We all have Google accounts. Just use those, devs. You even get two-factor for free.

Google/OAuth doesn't beat just letting users play with it.

I rarely sign in with Google for any app.

or, Mozilla Persona

It seems to me Draft's key growth action is getting users to share a draft with a friend.

Design the user's first required action to relate to sharing; capture the author's email after they click Draft/Save, and their friend(s) emails when they want to share. The interface could use a little work to encourage sharing as well.

This product is designed to spread itself inherently, so play to that strength!

Thanks Scott. To be honest, I really debated that. I have a blog post or two on this topic specifically. I've gotten a lot of advice from smart people that goes both ways on this. I personally like a guest user experience and no sign up. But from a lot of a/b testing with previous products, I've seen requiring registers to have a great effect on being able to increase signups, but more importantly create valuable conversations. Namely to discuss problems and feedback, which helps me make something much more valuable for people.

I assume that by "increase signups," you mean that when people view the landing page, a higher percentage of them signup. But what would worry me is the stat that such testing does not capture: the number of people who did not share the site with others because it's not easy to play with. And that kind of sharing is advertising.

In other words, it's possible to have a lower signup percentage, but more total signups.

Keep in mind that requiring users to sign up before trying the product contaminates user count as a meaningful metric, and devalues it as a marketing channel because it's filled with unqualified non-users.

I totally hear you that it sucks when you know people try your product but leave without signing up, and worse still you have no channel to ask them why. Users exploring a public demo have shown real interest in your solution to problems they have, and while they're exploring (especially if the demo is somewhat guided) there's a very natural opportunity to begin a conversation without requiring a signup. Ask for feedback (via survey, olark chat, quick submit comment form, your contact info...), offer to email product updates or tease future enhancements, show you twitter feed, etc. Moving registration downstream doesn't have to mean you can't learn about potential customers.

The wisdom I've heard is that you can either lose people on the "what is this -> signup" phase or the "signup -> pay" phase. Your leads are better qualified if you lose them on the former. You get better gauge of the potential market on the latter (guessing on this one).

I've worked in two completely different companies where we tried some notion of using the product without signing up. Both times we just got more people with less overall engagement at the cost of complicating the backend infrastructure.

Not to say this will never work, but it's definitely not a panacea.

I can see your reasoning behing making people sign up, even if that will significantly retard your growth rate multiplier.

But there's NO reason to make people create a new account. Everyone hates making new accounts, and there are a zillion identity providers out there, from google to facebook to twitter to linkedin to github to yahoo (ad nauseum).

And even if it's too much work right now to configure your application to accept third party identities, you can still "sign-up" users by requesting an email address, letting them straight into the application, and then email them a URL with an embedded identity token that allows them to pick up where they left off.

My advice would be to give people something for signing up. For example, let them start playing without email, let the save, and then ask for their email address to send them a unique url to their new account. This has the added advantages that (1) more people will play with the app and hopefully talk about it! and (2) those that sign up are more qualified leads as they know what they're signing up for.

Just to add my twopenneth from running https://www.writelatex.com - allowing users create documents and start trying out the editor without signing up has been a big plus for us in terms of users, and is generally popular according to feedback.

And in the early stages, more exposure through more users is a good thing, helps spread the word.

For us it was the way we'd started out though, so easy to implement :-)

you can try the experience on this random doc. https://draftin.com/documents/5606?token=SWh7LSoED_pnCwLtgJR...

just started typing as soon as it opened which felt like a good change from adjusting fonts

Simple, do something like jsfiddle. Let me play around with it, then if I want to save the doc I'll register.

you can use something like [email protected] - apparently there is no verification step.

Come to think of it, I felt the same way. Left the registration page up in the background while I worked on other stuff. Eventually came back and made an account.

Others might not be so patient!

Yup. Agreed. I use 10MinuteMail for these situations: http://10minutemail.com/10MinuteMail/index.html

So, you were attracted to the promised simplicity of the service, but turned off by the simplicity of the user model?

I was turned off by having to establish a relationship before evaluating the service.

I totally agree. Thought exactly the same... Why not a demo page?

[email protected]:123456