Slashdot Mirror


Software, Tools, Or Techniques For UI Review?

Comatose51 writes "Does the Slashdot crowd know of any software, tools, or even techniques for reviewing the UI of an application? Right now at our company this is a long and arduous task of looking at slide after slide of pages and menus from our UI, and taking notes and arguing over what should go where or how the UI elements should behave and interact with the user. It takes many, many hours to do this and with all our UI developers involved, it adds up. This has to be a common and recurring problem so there must be a better way to do this. If there is open source software to help, great, but any helpful suggestion would be appreciated."

8 of 246 comments (clear)

  1. Uh... by SatanicPuppy · · Score: 5, Insightful

    Not sure what you're getting at. If your action listeners are screwed up, that's an obvious problem with a straightforward solution, but if your UI just plain sucks, no program is going to tell you that.

    You need to go find someone with aesthetic sense, and a minimum of technical knowledge, and you need to shut up and listen to them whine as they use your UI. When you've fixed enough stuff that they stop whining, bring in a couple more and listen to them whine. Eventually they won't whine, and at that point, you'll know you've got a good interface.

    For gods sake though, don't get a fricking committee involved! They will all want to make a trivial change to put their mark on it, and all those changes will turn your unpolished interface into the sort of steaming crapheap that wouldn't meet the basic user-friendliness of the interface on a piece of stereo equipment.

    So yea; get the users involved, distill their complaints, make changes, NO COMMITTEES. And the simpler the better. I should write a UI testing program that just runs for 10 minutes and then pops up, "Your interface has too many buttons. Simplify it please." The interface can almost always be simpler.

    --
    ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
  2. Re:Apple Human Interface Guidelines by vimm · · Score: 5, Funny

    The layout of that webpage makes my left eye twitch.. however it was very intuitive and easy to use, and suddenly I crave IPHONE I MUST HAVE IT

  3. Joel Spolsky's writings by Stormwave0 · · Score: 5, Informative

    While it's not a tool, Joel Spolsky has written a long and detailed series of articles on how to correctly design a user interface. It's worth your time to check it out, even if it doesn't speed things up.

    Here's the first chapter

  4. Re:Ask the users. by hardie · · Score: 5, Insightful

    Absolutely ask the users. There is no better way of evaluating your UI.

    Have your programmers watch users try the UI. Don't lead the witness--let them make mistakes (and fix that part of the UI).

    You will be surprised what you learn.

    Steve

  5. Re:Just Use It by sm62704 · · Score: 5, Informative

    useit.com, Jacob Nielson's site. Everyone having anything to do with interface design should read the whole thing.

    --
    mcgrew's razor: Never attribute to stupidity that which can be explained by greedy self-interest
  6. Re:Well, there's your problem. by matrix+mechanic · · Score: 5, Informative

    Also, for all your developers, do you have a designer? UI development = graphic design + industrial/interaction design. Read Magic Ink: Information Software and the Graphical Interface

  7. Re:Ask the users. by Jupiter+Jones · · Score: 5, Interesting

    You know what's better than asking the users?

    Not asking the user.

    What you really should do is watch the user. If you ask them, they'll tell you what they think they'd do, or what they think you want to hear, or what they think they'd like to see... everything except what is most important: what they really do.

    (And I'm not the only one who thinks so.)

    JJ

  8. Comment removed by account_deleted · · Score: 5, Insightful

    Comment removed based on user account deletion