summaryrefslogtreecommitdiff
path: root/_posts/2015-01-16-your-website-is-not-special-dont-make-visitors-make-accounts.markdown
diff options
context:
space:
mode:
Diffstat (limited to '_posts/2015-01-16-your-website-is-not-special-dont-make-visitors-make-accounts.markdown')
-rw-r--r--_posts/2015-01-16-your-website-is-not-special-dont-make-visitors-make-accounts.markdown2
1 files changed, 2 insertions, 0 deletions
diff --git a/_posts/2015-01-16-your-website-is-not-special-dont-make-visitors-make-accounts.markdown b/_posts/2015-01-16-your-website-is-not-special-dont-make-visitors-make-accounts.markdown
index fddac2c..08a319c 100644
--- a/_posts/2015-01-16-your-website-is-not-special-dont-make-visitors-make-accounts.markdown
+++ b/_posts/2015-01-16-your-website-is-not-special-dont-make-visitors-make-accounts.markdown
@@ -8,6 +8,8 @@ date: 2015-01-16 00:00:00
One of my pet peeves in website usability design is forcing people to create unnecessary accounts. My recent purchase of some concert tickets from [Ticketfly](https://www.ticketfly.com) required me to make an account to buy them. For people who buy a lot of concert tickets, having an account may make a lot of sense. But for me, as someone who buys concert tickets at most once every year or two, having an account on a site that I will probably only use once is not only unnecessary, it's annoying.
+<!--more-->
+
This is not to say that you shouldn't offer accounts; that would be ridiculous (depending on the type of site you are running, of course). However, in general, your users know far better than you do whether or not they actually want or will use an account. Forcing them to create an account will only drive them away. People don't like creating accounts they don't want to have. There's really no reason you can't have a "check out as guest" option.
And if you do offer accounts, here are a couple of rules to follow to ensure a good user experience: