To require registration or NOT to require registration–that is the question. So let’s take an example.
Today, ChicagoTribune.com has a story on churches celebrating Darwin’s birthday. I click on the link wanting to read the article and am prompted to login or register. “The story,” I’m warned, “is available only to registered users.”
But one click to the front page of Google News and the story is right there from another source.
So, on the one hand, you’d like to have your readers’ information. But, on the other, you’d like to have readers. The question of whether or not you should require registration boils down to this: is the content on your site significantly unique that the average short attention spanned user will go through the hassel of completing your registration form?
Then let’s assume that your site is interesting and compelling enough that users register. Can you stay that way? Going back to the Tribune as an example, it’s not that I oppose registration on some sort of privacy grounds. I have a username and password–I just don’t remember them.
Requiring registration imposes both an up front and an ongoing obligation–an overhead or cost–to using your site. Does the opportunity you get from having your visitors’ information outweigh the cost of having users stop by and then leave?
Sometimes yes, sometimes no. It depends on you, your site and your visitors. But it’s definitely something to think about.
On a completely different note, the title may have made you think of Hamlet’s soliloquy. While I briefly considered writing this entry in iambic pentameter, I’ve opted instead to include a snippet and a link. Enjoy!
To be, or not to be: that is the question:
Whether ’tis nobler in the mind to suffer
The slings and arrows of outrageous fortune,
Or to take arms against a sea of troubles,
And by opposing end them?