Registration… ah, that is the question for a lot of application developers these days: Do we include our own registration process for our software and/or service? Or, do we use the oAuth and/or open API’s of popular existing services for logins (eg Twitter, Facebook, etc.)?
The answer is most simply this: Depends.
Now, I’m not necessarily going to prescriptive about the what and why but I do know that if you’re going to make me sign up for something then make it as easy, fast, and as painless as possible. Keep the bar of adoption low.
Or, you can just do it really creatively, like how Moof.com does it:
I really liked how they did the registration at the bottom; it fits very well with a casual and somewhat-personal approach to it. In fact, it was so novel that I didn’t mind signing up.
We could probably learn a thing or two about this strategy; does your church have a signup process? How easy (or personal) is it? Or how impossibly hard is it?
That's a great registration. I think I would sign up just because it was so novel. I'll file this away for future reference.
Love it – almost makes signing up for an account feel like a mad lib
I kinda wish you could set a default password, username, etc. allowing you to just press "join" and it sets it up, and adds it back to your computer so you can remember later.
I know there's "autocomplete" but half the time it gets confused for me anyway…
that would be cool.
Very usable. I like
we use paper signup sheets in our church…