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. Did You Know Paper-Prototyping Adds Value If Done Right?
  4. UI Design Challenge: Redesign A Filter Widget
  5. Site News: The State of the UI Design Guide Union

Leave a Reply

comments-bottom

More UI Design Guide Articles

thumbnail
UI Design Patterns: Exploration of Data and Visual Imagery in Application Design I was recently examining some interesting articles on Engadget and noticed  how the web site has been experimenting with different visual representations of data. As many know, Engadget is a high traffic tech blog. While it has not been special outside of the tech domain of knowledge. My eye... Jan 26th, 2010 | no responses
User Experience Design in an Agile Development Cycle The title pretty much says it all. After working for a while now in an agile development model. I’ve discovered several disturbing things that really cause a loss of sanity. The agile development cycle is quite fast. Depending on your team it has different lengths. Most iterations seem to be... Mar 30th, 2007 | no responses
Blog Response: IE 6 The Devil Not In Disguise The other day I came across an interesting article “Stop Developing for Internet Explorer 6” .  My initial thought was great I finally can stop developing for IE 6. Of course, that was just a pipedream. On many of my applications I still have a large captive IE 6 audience.... Feb 12th, 2009 | no 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.