[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Usability Strategy Discussion
From:       Ian h <arcaneone () yahoo ! com>
Date:       2002-07-09 20:16:08
[Download RAW message or body]

--- Robert Watkins <robert_maria@yahoo.com> wrote:
> >> Doesn’t it concern you that developers are
> >> creating programs without an understanding
> >> of the subject matter? 
> >
> >Why should that concern me?
> Dear Lord! Without understanding, at a minimum,
> the needs that a user would have and which the
> application is intended to fill seems a colossal
> waste of time. The only benefit I can see for
> writing an application under these circumstances
> is some sort of 'Look at these screens I made'
> kind of ego boost. If there is no ultimate goal
> of creating an application that is reasonably
> close to filling a true need, there is no need to
> consider Usability for the project.
>
> >> Who are they writing the application for,
> then?
>
> >For themselves, usually. Sometimes for
> >friends,
> >or family.
> Don't look now, but you've just started to
> identify the target user for an application...
> Just a few more details and you have some useful
> information.
>
> >> Besides, creating an application that will
> >> likely fail because of a lack of understanding
> >> seems a poor way to spend what little time
> >> is available to volunteer coders.
> >
> >Do you do any sports? Isn't that a waste of time
> >considering that it is ver> >y 
> >unlikely that you will ever win an Olympic
> >medal?
>
> If you _are_ working towards the Olympics and
> fail to learn the best techniques, enhance your
> existing techniques, get feedback from people you
> trust and/or respect, don't be surprised if you
> don't get there. If you're just out for a good
> time, don't sweat it if you aren't making
> progress. As long as you're having fun, don't
> change.
>
> Similarly for Usability. If your whole goal in
> volunteering for OSS development is to have some
> satisfaction in affecting an application, then
> keep working the way you are. However, if you are
> interested in Usability, you have to get
> knee-deep in the subject to gain any benefit from
> it. Just calling a discussion about "Look at my
> new screenshot!" isn't appropriate as a general
> Usability topic.
>
> Robert
>
>
I completely disagree because for most people there is
a middle ground. Using the sports analogy; Most people
are serious about their sport will never shoot for
being in the Olympics. This doesn't mean they won't
try to be the best they can be. They read magazines,
join clubs, swap stories and advice, some will even
take lessons or hire a personal coach to help with a
specific aspect of the sport. They spend all this
effort, time and money just to increase their
enjoyment of the sport their choice.

I think this represents most people involved in OSS
development even those who are paid for it. Just
because we enjoy working on Usability and think its
important, there are those who could care less about
it. Forcing them to get 'knee-deep" in will only make
them put upon. That just makes working on any project,
KDE in this case, no longer fun. A better way to
spread the word is to do just that. Explain what
Usability is, why its important, and maybe give them
some friendly advice. Basicly make it less of a buzz
word and more part of a good app.

Some ideas (most of which have already been discussed
on this mailing list)

1. a basic UI file showing suggested menu and
window(?) layout
2. List of item that contribute to the look and feel
of KDE
3. Provide a quick and easy way to for users to be
able report problems with and developers to ask
questions about Usability.
4. A short explainion of what questions to ask
yourself (or others) as if you were an "Average" user.


I feel the last point is the most important.
Understanding what the "Average Joe" and/or their
intended audience will think when using his/her app is
the key. This would allow problems to be fixed while
in development instead of as an after thought. Most
importantly it will make usability more of a non-issue
in the developers' mind thus making a usability issue
akin to a bug report.

- Ian

"Knowing is half the battle"


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com
_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]