From 3204575bfcd1f12db5945c8959073d40915cfdfe Mon Sep 17 00:00:00 2001 From: José Mota Date: Fri, 6 Apr 2012 19:40:37 +0100 Subject: Import all posts. --- ...r-not-to-show-registered-user-only-actions.html | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 _posts/2010-04-20-to-show-or-not-to-show-registered-user-only-actions.html (limited to '_posts/2010-04-20-to-show-or-not-to-show-registered-user-only-actions.html') diff --git a/_posts/2010-04-20-to-show-or-not-to-show-registered-user-only-actions.html b/_posts/2010-04-20-to-show-or-not-to-show-registered-user-only-actions.html new file mode 100644 index 0000000..8e939c4 --- /dev/null +++ b/_posts/2010-04-20-to-show-or-not-to-show-registered-user-only-actions.html @@ -0,0 +1,25 @@ +--- +layout: post +title: To show or not to show [registered user only actions] +tags: +- Design +status: publish +type: post +published: true +meta: + _edit_last: '1' +--- +Last week I struggled with a design decision that really caught my attention. Consider this: + +What you would do? Either: +
    +
  1. Don't show the user only actions? (my opinion: this one reduces clutter on your interface).
  2. +
  3. Or do show them and when the user clicks the links/buttons, the user gets a login redirected page for every new click?
  4. +
+

My pick would be number 1. Why?

+I'd rather have a welcome page that showed you what to use in case you signed up. Actions such as creating a new item on a product list and message sending that apparently require a sign up are confusing for a guest. Besides, clicking on such an action and redirecting you to a login page several times is not that much of an engaging experience. + +Feel free to add up on this thought. -- cgit v1.2.3-54-g00ecf