[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-usability
Subject: Re: amaroK usability report
From: "Chi Shang Cheng" <chishangcheng () gmail ! com>
Date: 2006-05-02 11:19:05
Message-ID: 8e5359a90605020419y63f2cfdcr35831afe02ba130c () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
2006/5/2, Celeste Lyn Paul <celeste@kde.org>:
>
>
> Some of my comments:
>
> 1. 'skin' or 'theme' would also be good names to use as well
>
> 3. i dont know if this is really an issue. the bigger issue is if users
> understand what collection means, if so then its more of a branding issue=
.
>
> 4. this is also a HIG compliance issue
>
> 7. also note that the file dialog does have shortcuts to things like home
> and
> favorites and that may be something the developers should look at when
> they
> redesign this dialog
>
> 12. in supplement to your dialog about vertical text: when we read, we
> basically recognize patters and not individual letters. its easier for u=
s
> to
> recognize vertical permutations of text (normal and upside down) however
> vertical and backwards text is much more difficult. you may want to
> suggest
> them to use large icons with small text, it seems to do well for kontact.
>
> 14. menu organization is a big problem for applications. you may want to
> suggest some alternate organizations since adoption of the new HIG will
> probably take time across the environment
I'm planning to use some sort of card-sorting method to provide a better
solution. I'd love to get some users involved in improving the usability of
amaroK. After all, they are the ones who are going to use it.
16. more HIG stuff
>
> (wow.. this is a thorough report..)
>
> 37. a lot of people are in favour of more descriptive buttons to help mak=
e
> choices. where i see a lot of potential for this, it seems as if the
> dialog
> messages are getting more complicated because they dont have to fit in to
> an
> OK/Cancel decision
>
> i see you are up on your readings, you reference a lot of important paper=
s
> in
> your report.
>
> its also worth noting that heuristics are often interface peculiarities
> that
> wont be caught by a user test, however they do effect the user on some
> level,
> usually subconciously. sometimes a user may comment that something doesn=
t
> look or feel right but wont be able to pick out what is bothering them.
>
> im not sure if i would have graded some of the issues you found the way
> you
> did, but overall it was a good review with good suggestions for the amaro=
K
> team. thanks for your work!
Agreed. I wanted to re-grade some issues, but the document was almost
as good as finished, and I was too lazy to change it. :p
~ Celeste
>
> On Monday 01 May 2006 18:33, Chi Shang Cheng wrote:
> > I have conducted a quick heuristic evaluation of amaroK.
> >
> > Abstract:
> > After a short heuristic evaluation of Amarok, a total of 41 usability
> > issues were found. Only 8 issues of low severity were found, 11 were
> marked
> > medium, and the remaining 22 issues considered highly severe.
> > Most of the issues were related to design flaws. The application was no=
t
> > tested for task-oriented usability. Even though the application
> functioned
> > properly from a technical perspective, attention should be given to a
> more
> > aesthetic user interface design in the future.
> >
> > I wished MS Word could handle images better... the spacing isn't correc=
t
> > here and there, but it's the content that matters. :)
> >
> > I have tried to upload the report on OpenUsability.org, but it didn't
> work.
> > Hopefully, the following URL should work:
> > http://chishangcheng.googlepages.com/amaroKusabilityreport.pdf
> > It should be noted that this evaluation was not thorough. I'm planning
> to
> > do some more usability work on amaroK after 1.4 final release.
> Hopefully,
> > most issues that I have addressed can be fixed in time for 1.4. :)
> >
> > Comments are welcome!
> >
> > Chi Shang
>
> --
> Celeste Lyn Paul
> KDE Usability Project
> usability.kde.org
>
>
> _______________________________________________
> kde-usability mailing list
> kde-usability@kde.org
> https://mail.kde.org/mailman/listinfo/kde-usability
>
>
>
>
[Attachment #5 (text/html)]
<br><br>
<div><span class="gmail_quote">2006/5/2, Celeste Lyn Paul <<a \
href="mailto:celeste@kde.org">celeste@kde.org</a>>:</span> <blockquote \
class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: \
#ccc 1px solid"><br>Some of my comments:<br><br>1. 'skin' or 'theme' would \
also be good names to use as well<br><br>3. i dont know if this is really an \
issue. the bigger issue is if users <br>understand what collection means, \
if so then its more of a branding issue.<br><br>4. this is also a HIG compliance \
issue<br><br>7. also note that the file dialog does have shortcuts to things like \
home and<br>favorites and that may be something the developers should look at when \
they <br>redesign this dialog<br><br>12. in supplement to your dialog about vertical \
text: when we read, we<br>basically recognize patters and not individual \
letters. its easier for us to<br>recognize vertical permutations of text \
(normal and upside down) however <br>vertical and backwards text is much more \
difficult. you may want to suggest<br>them to use large icons with small \
text, it seems to do well for kontact.<br><br>14. menu organization is a big problem \
for applications. you may want to <br>suggest some alternate organizations \
since adoption of the new HIG will<br>probably take time across the \
environment</blockquote> <div> </div>
<div>I'm planning to use some sort of card-sorting method to provide a better \
solution. I'd love to get some users involved in improving the usability of amaroK. \
After all, they are the ones who are going to use it.</div> <br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; \
BORDER-LEFT: #ccc 1px solid">16. more HIG stuff<br><br>(wow.. this is a thorough \
report..)<br><br>37. a lot of people are in favour of more descriptive buttons to \
help make <br>choices. where i see a lot of potential for this, it seems \
as if the dialog<br>messages are getting more complicated because they dont have to \
fit in to an<br>OK/Cancel decision<br><br>i see you are up on your readings, you \
reference a lot of important papers in <br>your report.<br><br>its also worth noting \
that heuristics are often interface peculiarities that<br>wont be caught by a user \
test, however they do effect the user on some level,<br>usually \
subconciously. sometimes a user may comment that something doesnt <br>look \
or feel right but wont be able to pick out what is bothering them.<br><br>im not sure \
if i would have graded some of the issues you found the way you<br>did, but overall \
it was a good review with good suggestions for the amaroK <br>team. thanks \
for your work!</blockquote> <div> </div>
<div>Agreed. I wanted to re-grade some issues, but the document was almost \
as good as finished, and I was too lazy to change it. :p</div><br> <blockquote \
class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: \
#ccc 1px solid">~ Celeste<br><br>On Monday 01 May 2006 18:33, Chi Shang Cheng \
wrote:<br>> I have conducted a quick heuristic evaluation of amaroK. \
<br>><br>> Abstract:<br>> After a short heuristic evaluation of Amarok, a \
total of 41 usability<br>> issues were found. Only 8 issues of low severity were \
found, 11 were marked<br>> medium, and the remaining 22 issues considered highly \
severe. <br>> Most of the issues were related to design flaws. The application was \
not<br>> tested for task-oriented usability. Even though the application \
functioned<br>> properly from a technical perspective, attention should be given \
to a more <br>> aesthetic user interface design in the future.<br>><br>> I \
wished MS Word could handle images better... the spacing isn't correct<br>> here \
and there, but it's the content that matters. :)<br>><br>> I have tried to \
upload the report on OpenUsability.org, but it didn't work.<br>> Hopefully, the \
following URL should work:<br>> <a \
href="http://chishangcheng.googlepages.com/amaroKusabilityreport.pdf">http://chishangcheng.googlepages.com/amaroKusabilityreport.pdf
</a><br>> It should be noted that this evaluation was not thorough. I'm planning \
to<br>> do some more usability work on amaroK after 1.4 final release. \
Hopefully,<br>> most issues that I have addressed can be fixed in time for 1.4. \
:)<br>><br>> Comments are welcome!<br>><br>> Chi \
Shang<br><br>--<br>Celeste Lyn Paul<br>KDE Usability Project<br><a \
href="http://usability.kde.org">usability.kde.org</a><br><br><br>_______________________________________________
<br>kde-usability mailing list<br><a \
href="mailto:kde-usability@kde.org">kde-usability@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/kde-usability">https://mail.kde.org/mailman/listinfo/kde-usability</a><br>
<br><br><br></blockquote></div><br>
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic