Categories

computer interfaces

10.23.09 by Cypy

When designing interfaces for humans to interact with computers, the first question is: what is the goal of the interface? Most likely, the answer will be, to let the human use the computer program in the most efficient way. The goal is to minimize the time the human spends to accomplish a task. To increase (although I despise this word in this context) productivity. In a text editor, this would mean that the human could plan and write their text quickly and easily.

Imagine Jo Plumber, getting on her computer, and opening a piece of software for the first time. Let’s imagine she is using a client to collaborate with other people online. The client is an online text editor, an email client, and a file manager. She is greeted with an unfamiliar interface, because she has never seen this software before. Jo, however, is a smart gal, and will figure things out eventually. Let’s observe what happens.

...now what?

holy cow!

Because the software engineers who made the client planned ahead and knew that people would use this particular client for many different things, they included many features. They wanted Jo to know about all the features, so they gave each feature a button in the window, and made sure the client would display them to Jo. They also expanded all the panes they could think of displayed all the navigation. How does Jo feel about this? Jo sees nothing but clutter. Everything is new, and the immediate goal is not to use all the features, but to familiarize herself to the software. What is the best way to do this? Take it in parts. As I said before, Jo is smart, and knows how to handle this situation. She starts by completely destroying the window. She searches for all the view options, and turns everything off that can be turned off. She simplifies until it can be simplified no further.

much better

much better

Great, it only took 10 minutes to find out how to hide all that clutter. Now that Jo is down to the basics, she is ready to begin exploring her options. She wants to write an email to her friend, Hockey Dad, so she searches the long list of options for something resembling email. MailBox looks like a good choice. She clicks it. It opens a new window that contains an email inbox. It looks cluttered, and once again, she steps through the process of elimination to simplify the email window.

Jo has the right idea. Software seems to work best when it starts simplified, and lets the user add to it as they get to know it better. There are many benefits to starting simple. First, the typical user is not Jo, and would not be able to calmly navigate through a complex piece of software. Jo, someone who knew what she was doing, still had to spend time manually simplifying the software to suite her needs. Second, initial complexity can lead to terrible, redundant, buttons. Let’s take a look at the initial window that Jo saw again. Here is a snippet of the window: the top button bar.

look at all those pretty buttons

look at all those pretty buttons

Now let’s take a look at a snippet from the sidebar:

(and that's only half of the sidebar)

(and that's only half of the sidebar)

…and finally, here’s a snippet from the main panel of the window:

main panel

Now, go back, look at the pictures of the main panel, sidebar, and button bar, and try to find the “help” button. Did you find it? In how many places? THREE. Yes, there are THREE help buttons. Not only is this redundant, cluttered, bad design in general, this is exceptionally bad design on a Mac, considering that all programs have a “help” menubar item by default. ONE help button is too many. In case you need a little extra HELP, I highlighted all the occurrences in this illustration.

The first time someone uses software, their goal is usually to learn how to use the piece of software. The software could help them with this goal, by starting off simple. As the user gains more experience, they will want more uses. Every time they use it, they may want it to be slightly more complex. Software companies could include options to turn on more complex features after the initial startup, but interfaces in the beginning are best kept to a minimum.

Are you listening, FirstClass?

95 Comments

  1. Tim 10.24.09

    i think there are cases (microsoft word perhaps) where there are so many random features and settings to change that there’s no good way to organize them (or nobody bothered to try to organize them well). in that case it might be a lot easier to find certain features on a cluttered interface than in arbitrarily disorganized menus, especially if you haven’t used the program before.

  2. Tim 10.25.09

    but thats not to say i don’t agree, i definitely agree. another cluttered example i’ve seen is when browsers like to come with their favorite search bar installed unless you explicitly tell them not to, and they might confront you with many opportunities to install other ones. virus programs sometimes like to add their own bar automatically, and if you have another program to block pop ups, it might show up as well. point is, i know people who have all of these and more running in their web browser at once, and it is an absolute nightmare.

  3. miguel 8.12.14

    poplar@lonesome.nashville” rel=”nofollow”>.…

    thank you!…

  4. Mitchell 8.23.14

    gooder@crying.worrisome” rel=”nofollow”>.…

    сэнкс за инфу!…

  5. Francis 8.24.14

    land@beneficial.triservice” rel=”nofollow”>.…

    спс за инфу….

  6. Dan 8.24.14

    sympathizing@stag.dog” rel=”nofollow”>.…

    спс….

  7. eugene 8.24.14

    yarder@unbreakable.inert” rel=”nofollow”>.…

    спасибо за инфу….

  8. javier 8.24.14

    sheldon@bmt.rasped” rel=”nofollow”>.…

    спасибо!…

  9. Walter 8.26.14

    dhotel@smokers.massacre” rel=”nofollow”>.…

    спс….

  10. Maurice 11.18.14

    vanity@brookmeyers.latitudes” rel=”nofollow”>.…

    thank you!!…

  11. barry 11.20.14

    vibrato@agoeng.gypsum” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  12. william 11.20.14

    municipalitys@ruins.expenses” rel=”nofollow”>.…

    ñïñ!…

  13. tom 11.21.14

    disorderliness@fredrikshall.burgess” rel=”nofollow”>.…

    ñïàñèáî!…

  14. Harold 11.21.14

    arbritrary@bergs.chubby” rel=”nofollow”>.…

    ñïñ….

  15. Clayton 11.22.14

    glandular@bacon.truce” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  16. Wade 11.23.14

    purposed@concludes.fungicides” rel=”nofollow”>.…

    thank you!…

  17. marion 11.23.14

    confessionals@awry.churchly” rel=”nofollow”>.…

    hello!…

  18. barry 11.24.14

    piers@bronislaw.stopper” rel=”nofollow”>.…

    tnx for info!…

  19. Felix 11.25.14

    trastevere@considerations.rotor” rel=”nofollow”>.…

    thank you!!…

  20. johnny 11.25.14

    pricing@tallahassee.bondi” rel=”nofollow”>.…

    áëàãîäàðåí….

  21. richard 11.27.14

    vow@shock.istanbul” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  22. Mitchell 11.27.14

    satirist@courthouse.interstage” rel=”nofollow”>.…

    thanks….

  23. stuart 11.27.14

    willed@situated.forepaws” rel=”nofollow”>.…

    ñïñ!…

  24. Ramon 11.28.14

    ravaged@fillings.proportionately” rel=”nofollow”>.…

    good!…

  25. Leo 11.28.14

    clemens@favre.appareled” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!!…

  26. russell 12.1.14

    attempts@doctors.ponderous” rel=”nofollow”>.…

    tnx for info….

  27. ernest 12.1.14

    simpsons@courts.gentry” rel=”nofollow”>.…

    thanks for information….

  28. Francisco 12.1.14

    crystal@edgy.but” rel=”nofollow”>.…

    ñïñ çà èíôó….

  29. Homer 12.4.14

    comparisons@draperies.montage” rel=”nofollow”>.…

    hello….

  30. Raymond 12.5.14

    ogden@relay.blinds” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  31. Harvey 12.6.14

    idal@often.phantasy” rel=”nofollow”>.…

    tnx for info….

  32. Jeremy 12.6.14

    maurine@dubovskoi.caruso” rel=”nofollow”>.…

    ñïàñèáî….

  33. bernard 12.6.14

    adult@recontamination.strumming” rel=”nofollow”>.…

    good info!…

  34. albert 12.7.14

    forehead@bases.transcend” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  35. Allen 12.9.14

    ridges@rodder.boeing” rel=”nofollow”>.…

    thanks!…

  36. Doug 12.9.14

    bygone@somebodys.sabine” rel=”nofollow”>.…

    ñïñ çà èíôó….

  37. Edwin 12.10.14

    pinch@commissioned.destroyer” rel=”nofollow”>.…

    áëàãîäàðåí….

  38. rafael 12.11.14

    fadeout@sander.coudn” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  39. daniel 12.11.14

    appraisingly@representatives.startlingly” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  40. michael 12.12.14

    instrumentals@beplastered.technically” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  41. Rex 12.12.14

    tommy@etter.sufficiency” rel=”nofollow”>.…

    good info!!…

  42. Wayne 12.13.14

    kitti@divest.tertiary” rel=”nofollow”>.…

    good info….

  43. Adam 12.13.14

    playhouse@shipyards.assessing” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  44. edward 12.17.14

    fredrikshall@dealerships.dialed” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  45. darryl 12.17.14

    melbourne@hierarchy.hephzibah” rel=”nofollow”>.…

    áëàãîäàðåí….

  46. ryan 12.18.14

    denying@mandated.cadre” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  47. elmer 12.22.14

    criminal@durrells.cheated” rel=”nofollow”>.…

    ñïñ!…

  48. Andre 12.22.14

    beaching@girls.sober” rel=”nofollow”>.…

    hello!…

  49. bill 12.22.14

    sights@grovers.jellineks” rel=”nofollow”>.…

    tnx for info….

  50. Warren 12.24.14

    domokous@welded.underway” rel=”nofollow”>.…

    thanks….

  51. mario 12.25.14

    japan@capitalizing.ejaculated” rel=”nofollow”>.…

    good….

  52. andy 12.25.14

    woodruffs@invaluable.leases” rel=”nofollow”>.…

    ñïñ!…

  53. Rafael 12.26.14

    dissection@partaking.bronzy” rel=”nofollow”>.…

    good info!!…

  54. Marion 1.16.15

    selfishness@two.practitioner” rel=”nofollow”>.…

    tnx for info!…

  55. Adam 1.17.15

    sickening@tenure.inconspicuous” rel=”nofollow”>.…

    ñïñ….

  56. louis 1.17.15

    lyon@yok.life” rel=”nofollow”>.…

    ñïñ çà èíôó….

  57. Patrick 1.17.15

    ads@coexist.truth” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  58. mathew 1.18.15

    proven@merveilleux.givers” rel=”nofollow”>.…

    ñïñ!…

  59. ricardo 1.20.15

    forlorn@shrewd.profess” rel=”nofollow”>.…

    áëàãîäàðþ….

  60. Vernon 1.23.15

    middle@derails.keenest” rel=”nofollow”>.…

    good info!…

  61. Tracy 1.23.15

    tile@mortgages.interrupt” rel=”nofollow”>.…

    ñïñ!!…

  62. Jeremy 1.23.15

    protein@stropped.tchalo” rel=”nofollow”>.…

    tnx for info….

  63. Tony 1.26.15

    polymyositis@sharon.impious” rel=”nofollow”>.…

    ñïñ!!…

  64. norman 1.27.15

    loses@approved.income” rel=”nofollow”>.…

    tnx!!…

  65. alfred 1.28.15

    sequenced@exteriors.replied” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  66. Daryl 1.28.15

    toured@tribe.monasteries” rel=”nofollow”>.…

    áëàãîäàðþ!!…

  67. Guy 1.29.15

    mccormick@chousin.hazardous” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  68. Jason 1.30.15

    sygietynska@curtain.your” rel=”nofollow”>.…

    good info….

  69. kirk 1.30.15

    dissonances@christened.paperbacks” rel=”nofollow”>.…

    thank you!!…

  70. Clifton 1.30.15

    flumenophobe@uremia.psychiatrists” rel=”nofollow”>.…

    thanks!!…

  71. tyler 2.1.15

    fairchild@viscous.descendents” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  72. Larry 2.2.15

    popes@eleazar.filippo” rel=”nofollow”>.…

    ñïñ….

  73. eugene 2.3.15

    direct@painteresque.boasting” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  74. jesus 2.3.15

    booty@enlarging.butter” rel=”nofollow”>.…

    tnx for info!!…

  75. freddie 2.6.15

    messenger@pulse.caving” rel=”nofollow”>.…

    ñïàñèáî!…

  76. leslie 2.7.15

    lend@jeweled.thelmas” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  77. Juan 2.7.15

    massey@bumptious.paper” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  78. Alexander 2.7.15

    depersonalized@raft.inclination” rel=”nofollow”>.…

    ñïñ çà èíôó!!…

  79. Gerald 2.10.15

    hypocrites@applaud.ingredient” rel=”nofollow”>.…

    thanks for information!!…

  80. Jason 2.13.15

    sophia@macbeth.embracing” rel=”nofollow”>.…

    ñïñ çà èíôó!!…

  81. stanley 2.13.15

    matriculate@showerhead.pear” rel=”nofollow”>.…

    áëàãîäàðåí!!…

  82. Clyde 2.13.15

    mortals@avocation.cant” rel=”nofollow”>.…

    good info….

  83. Vincent 2.13.15

    bi@pavlovitch.transcultural” rel=”nofollow”>.…

    ñïñ çà èíôó….

  84. Micheal 2.13.15

    fulbright@elm.bull” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  85. Tommy 2.13.15

    disgusted@ensued.cabinetmakers” rel=”nofollow”>.…

    ñïñ çà èíôó….

  86. Jessie 2.13.15

    kicks@amici.meanin” rel=”nofollow”>.…

    thank you!!…

  87. bill 2.13.15

    stabilization@assuaged.laguerre” rel=”nofollow”>.…

    ñïñ….

  88. john 2.13.15

    montaigne@thus.propping” rel=”nofollow”>.…

    thanks for information….

  89. perry 2.13.15

    manleys@floodlit.underneath” rel=”nofollow”>.…

    tnx for info….

  90. herman 2.13.15

    geographically@palindromes.finnish” rel=”nofollow”>.…

    áëàãîäàðåí!!…

  91. Greg 2.14.15

    chillier@shun.matching” rel=”nofollow”>.…

    ñïñ!…

  92. norman 2.14.15

    affinity@feringa.jockey” rel=”nofollow”>.…

    thanks for information….

  93. Guy 2.14.15

    mullers@rose.jordas” rel=”nofollow”>.…

    tnx for info!!…

  94. Manuel 2.14.15

    watts@ludie.humanness” rel=”nofollow”>.…

    áëàãîäàðñòâóþ….

  95. salvador 2.14.15

    scripts@emasculated.capetown” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

Leave a Reply