Interfaces should be user-centric
What killer-apps.com says :
Build superior digital customer interfaces that mediate human interaction, providing quick and efficient automated service at a level defined by the customer. These interfaces record their interactions, providing a rich store of data that the company can learn from.
What we understood :
When developping a software or a online service, people are tempted to build the interface with a lot of functions, even if the user does not use them. That is why we should always think about the use if the product before building its interface.
As Steeve Krug says in his book "Don't make me think" :
" When we’re creating sites, we act as though people are going to pore over each page, reading our finely crafted text, figuring out how we’ve organized things, and weighing their options before deciding which link to click.
What they actually do most of the time (if we’re lucky) is glance at each new page, scan some of the text, and click on the first link that catches their interest or vaguely resembles the thing they’re looking for. There are usually large parts of the page that they don’t even look at. "
This means that if you want to build a efficiet interface, you should put the stress on what is necessary and on what people are mostly going to use. For the rest, you sould not hide others functions, but display them in another way, to make them smaller.
A good example : BlogoText
For instance, the blogging softwate BlogoText particularly simple, it has been designed with simplicity and ease of use in mind. This tool provides usual features of a blogging tool but without complicate functionalities.
BlogoText is not only easy to use, it is also easy to manage. This tool doesn't use any database. You can have a blog without SQL. And if you decide to move from your host, you can take your content with you : it is stored in a folder.
Tags : interfaces learning user centric
