Onboarding about slick HOT 4 OPEN

We could just require a password in any case. People are used to putting in email address, nickname and passwords nowadays. Sure, not needing a password is also cool but it might be confusing.

from slick.

I wonder whether the appeal of just showing a single input (just 'username') is versus showing a form and password. Do people sign up faster? Email newsletters for example that just show your email address. Does anyone know of any research on that? Does needing a password right off the bat create an illusion of "signing up to something" that might be a detractor?

There's a lot to be said for getting people to just use your interface without any hurdles (username is the bare minimum here) and then getting them to commit more further down the line. Slack's slackbot is a great example of that. As is mailing lists that ask for confirmation and more details later.

from slick.

You can avoid even entering a username, and generate a random one. Then just make it obvious how to select your own username.

from slick.

@simonv3 Just using the username as first step and then handling NickServ if it's registered from there on is exactly how I want to implement it in Kosmos. Got the idea from momentumdash. See my Hyperchannel issue here: 67P/hyperchannel#39

from slick.