Interface Design sucks and here is why

You likely came here because you also had that experience: Creating an interface for a client or software, just to proceed to do tedious coding work.

Sometimes that frustration is caused by dull coding: the kind of code you’ve done a dozen of times before in slightly different configurations. Creating getters and setters, adding listeners to buttons, blah blah blah.

Then again other times, it’s simply a lack of knowledge and perhaps communication with the users on how to do things better.

In other words, UI design (often) both sucks for us programmers, who have to make it and do not like it, and for the users, who have to use the half-assed programs created by demotivated programmers.

Programmers aren’t necessarily designers, after all, right?

So how can you make your life a bit easier as a programmer? Coming from both a art/design and programming background, I’ve summarized the following tips:

  1. Group together what from a user’s view logically belongs together.

  2. Visually separate actions that are functionally different: don’t place a delete button right next to an add button.
    The box on the right would make multiple problems. One is: what happens if the user clicked on the remove button instead of the add button?

     

  3. Critical actions, like removing data or changing a large set of data, need a higher use-threshold e.g. via a dialog: “Are you sure to do that…?”. Those are the kind of actions you don’t want to happen if you click on them by accident.

  4. Important actions should be highlighted through movement, form, shape and color. Like this you can control the flow of your user’s attention – and where they are likely to click next.

  5. Meaningful usage of icons increases the intuitiveness of your software – but don’t overdo it. PaintShop Pro is basically bloated with them and here they are more confusing than helping.

  6. The look and design of your components should be aesthetically coherent. Think of it like this: In code, you set the rules for your code, how it looks like via style guides and so on. This is in fact very similar to interface design: you can also set a visual rules here and apply them your components: e.g. all interactive components like buttons, menus should be blue, background stays white.

  7. Do not overload your interface with components or buttons. Instead, make information toggleable from display and use meaningful sub-menus, while keeping those sub-menus as accessible as possible, e.g. via shortcuts. Ideally, a single sub-menu should be like a red-black tree with a maximum depth of 3 to 4.
    Menus like this often don’t have a depth of more than two or three.
  8. The more a user uses a function, button or component in a program, the more accessible it should be. This helps the user’s workflow and makes your software easier to use. There is a reason why there are shortcuts like CTRL+A and CTRL+C, which quickly lets you select everything and copy the current selection.

  9. Give users the possibility to customize views so they can adapt the software to their special needs and workflow.

  10. Support the users by assistants, in-app hints or tooltip texts.

Links


 

What other important rules exist in interface design? Tell me in the comments!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s