[
https://issues.apache.org/jira/browse/WHIMSY-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045741#comment-16045741
]
John D. Ament commented on WHIMSY-99:
-------------------------------------
Heh. So I'll point out that UX != CSS/colors. It's about the application's
behavior. So while bootstrap probably remains the core of this, ultimately the
color scheme should just be consistent. We probably would have some custom CSS
styles for what I would consider ASF branding, and hopefully those can be
derived from the TLD.
There are some UX faux pas that I see pretty outright. I've listed them below.
I was actually planning to show the app to a friend of mine to get his input
(we both deal with a certain amount of experience in day jobs).
- The instructional text should not be in a success bubble
- The instructional text should be subjectively near where the action is and
somehow draw your eyes to where to do the action (hence the root problem of the
double click, you look at it and wonder "what do I do now?")
- We have to understand who actually uses Whimsy and how. There are more
active users (which is a small number) and passive users (which is a larger
number). They do different actions.
- The loss of the input field after you've entered something is odd, because it
makes you want to do one entry only instead of a bulk entry format.
- I'm not sure that separating out mentor/ppmc/committer/pmc/chair is the right
thing, or if they should appear in the same grid.
- We may want a discreet view/edit mode.
- Should we have a confirmation of activity?
So sure [~curcuru] if you want to work together, that's fine. What I was
planning to do was first story board what some of these interactions look like
and run it by some end users.
> Improve roster tool UX
> ----------------------
>
> Key: WHIMSY-99
> URL: https://issues.apache.org/jira/browse/WHIMSY-99
> Project: Whimsy
> Issue Type: Improvement
> Components: Roster
> Reporter: John D. Ament
> Assignee: John D. Ament
>
> The roster tool needs some UX improvements:
> - Double clicking on a row is not conventional, and actually makes mobile
> support next to impossible. We should have some kind of edit mode (as some
> call it, the hamburger may work)
> - The plus button turns into a search for some reason, without explaining
> whats going on. The search should explain more about what to do, and perhaps
> even explain the multi-search mode.
> - The buttons that do appear are in a notes column
> - There's no way to actually add notes so its not clear why we need a notes
> column
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
