Which Widget is the Right Widget for My Application Design?

Let’s talk about proper widget usage. It’s imperative to know when to use the right tool for the right job. I wouldn’t use a sledge hammer to hang a painting (unless it was a very large painting.) I wouldn’t use a socket wrench as a pliers. I could use a butter knife to screw something in, but is that the best solution? It’s all about using the right application piece at the right time.

Part of this comes from knowing what the common design pattern is for a particular widget. Another part is knowing how and when to stretch the limits of what is considered to be “common usage.” Any time you do something outside of the user expects is when your usability can start to plummet.

The Naked Anatomy of a Check box

Let’s take a look at a simple example our beloved friend the check box. There are two states to this standard check box that are considered common.

  • If an item is checked it can indicate either something was accomplished.
  • If the box is unchecked you are undoing or indicating you do not want to follow through on an action.

Generally you will find a check box in an unchecked state. Suppose for an instance that we reversed the common usage. A check box when checked now indicates to the user they are NOT SUPPOSE TO DO SOMETHING.  Applying this to the example below we see that because the current state is checked I would un-check to save my selections. Not only is this conter-intuitive but see how hard it was to explain that. You may have to read what I wrote twice to figure out what we are trying to accomplish.

Save Selections:

The same holds true for the most minute details in your application design and ultimately in the widget you choose to use. Going against the common accepted practice has already introduced unneeded complication and confusion.

In future stories we will be looking at a number of controls and how they should be used effectively.  Soon I will have a forum setup (next few weeks) to continue on the discussions outside of the articles written here.

Related articles:

  1. When is it the Right Time to Use Icons?
  2. SXSW Interactive 2008 – Pre-Morning Wakeup Planning
  3. UI Design Challenge: Redesign A Filter Widget
  4. Did You Know Paper-Prototyping Adds Value If Done Right?
  5. SXSW Day 3 – Wrap Up

Leave a Reply

comments-bottom

More UI Design Guide Articles

thumbnail
UI Design Software Review: Flair Builder v1.6 Recently, I received a copy of  Flair Builder , a new wire-frame, mock and interactive prototyping tool.  As many of my readers know, I am very much for utilizing paper prototyping for the first few iterations of a design. Of course, when I need to present something to a client I try to clean up... Jun 24th, 2009 | 3 responses
Corporate Conflicts A Cantakerous Cacophany of Confusion. One topic that constantly is under debate in the corporate design world is: “Who makes the final decision.” Does the designer, business analyst, information architect, developer etc? Personally, this has been a major area of contention. When it comes to design and the user interface... Mar 24th, 2007 | no responses
Agile UI Design: A Fundamental Miscalculation in UI Design Excellence? I’ve been banging my head against a wall trying to figure this question out for some time now.  Can existing in an agile development cycle truly create the best ui design? I’ve worked in Agile development environments. I’ve worked with structured project management. I’ve... Mar 25th, 2009 | 15 responses

Twitter is a great way to share new and exciting resources with all our viewers. Each day I provide links and commentary on all things UI. You can find UI resources, UI design examples, new techniques, and a lot more by Following @UIDESIGNGUIDE on Twitter.

The idea for this design blog first came about two years ago at SXSW Interactive.

Currently UI Design guide is in its fourth redesign. This site takes quite a bit of time to maintain as well as write the content. Just like UI Design this site is a passion that keeps evolving.

Inside, I cover articles on many topics icluding: lessons, prototyping methods, agile UX methods, design reviews, design challenges, application features, and of course design experiences, just to name a few.

With all the blogs out there you may be asking yourself who are you to give advice? That's a fair question. If you have a moment feel free to read about my design history.