Import all posts.

1 files changed, 25 insertions, 0 deletions

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:

+<ul>

+	<li>You have a <em>user driven app</em> on the web.</li>

+	<li>You also provide some actions for <em>guests</em>.</li>

+</ul>

+What you would do? Either:

+<ol>

+	<li><strong>Don't show the user only actions?</strong> (my opinion: this one reduces clutter on your interface).</li>

+	<li><strong>Or do show them and when the user clicks</strong> the links/buttons, the user gets a login redirected page for every new click?</li>

+</ol>

+<h3>My pick would be number <em>1</em>. Why?</h3>

+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 <em>several times</em> is not that much of an engaging experience.

+

+Feel free to add up on this thought.