An introduction to Interaction Design and what it means for the Web, also what are our responsibilities as designers, developers and clients?
Hi there, I know you've just arrived on this page, but I want to take your focus away from this article for a second. If you are reading this on a computer or laptop, would you do me the tremendous favour of looking down at your keyboard quickly.
OK, eyes back here, thank you. Chances are your keyboard has the QWERTY layout, which you might assume is the best layout for a keyboard. It has after all looked like that since early typewriters. Interaction Design is the process of thought that goes into designing systems and objects which are the most usable or user-friendly for the target users. The QWERTY-keyboard is not an example of good interaction design, at least, not anymore. The first typewriters were arranged from A to Z, but typists typed too quickly with this layout, causing the mechanical keys to jam and therefore temporarily halt the typing process.
Interaction Design for the Web
The web is no longer the static information delivery system we were accustomed to in the 1990s. We find ourselves surrounded by buzz words and acronyms all describing some form of technology or improvement. Our experience with clients is that they're often in two camps. Either they are not as yet familiar with the concept of a pervasive web, or they are on top the the latest buzz words and want to implement as many as possible in order to stay current and as always, keep in line with SEO.
The reality is, a blog will not work for every client, a like button is not for everyone, that rotating banner may look amazing, but how well will it work for a company selling compost, for example? The point is, each client is different, their needs are different and when we don't design and develop according to that, one of two things usually happens.
Summary for Designers
Look at the trends, look at the frameworks, but start with what the client wants and more importantly needs (Hint: these may not be the same). Look how it can fit into what you know, and if not, get creative.
Summary for Developers
It is important to work with the designer, implement the systems the best way you know how, and when testing, try to be a first time user, or better, let someone else who knows nothing of the project test it.
Summary for Clients
The company you approach to engineer your site has a responsibility to know what is needed for different situations. While you may or may not be familiar with how the web works, you have a reason for wanting a site and what exactly you want to do with it. Write that down and let that focus drive the concept.
