Thursday, September 4, 2008

Interiour decoration - the colors of the new Notes

Colors are bad. Are they?

Some months ago, after the release of the OpenOffice.org 3.0 Beta, some Germans discussed the new Notes in a newsgroup (I don't remember the URL, sorry). There, one user referred to the notes being to colorful. He stated that it would have been better to use no color at all. Personally, I'm a little bit sad how this property of the Notes is perceived. So I would like to give some explanations a try.

Basically, color is an important information carrier and provides clues about the author of the notes. This is similar to the word processor of our biggest competitor. For me, it was no surprise that this request was estimated to be important to work on (different to other requirements which needed some more ... persuasiveness).

We only need colors. And...

The i-Team worked on it for several weeks: defining colors, gradient style, effect, visibility, ... Our requirements were (simplified):
  • provide a fresh and modern look, but avoid to distract the user from the actual text document
  • keep consistency with existing visual design work (e.g. with the Galaxy Icons Color Palette)
  • be based on the color palette of previous OpenOffice.org versions and the biggest competitors
  • consider the maximum number of different authors in the document
  • provide compatibility with the markups of the Change Tracking feature
Okay, so how do the colors actually look like? Let's have a look at the color table which has been developed...
But the competitor...

You may have noticed that there are some small differences between the application color palettes. I want to comment two of the decisions of the i-Team. First, the color of the first note is 'yellow' instead of 'red'. Although red is a nice markup color, we wanted most of the people to be able to recognize the little boxes as notes - similar to the sticky paper sheets in the real world. And, we are now somehow compatible with the visualization of notes in Calc. If you don't know what I'm talking about, try adding Notes for two different authors in the Microsoft Office applications Word, Excel and Impress. What a colorful world - they decided to use different visualizations (tested in Office 2003).

When we already have a look at Microsoft Office Word, you may have noticed that Word darkens the Note who currently has the focus. The result is a good recognizability of this note in comparison with the others, but the drawback is a clearly noticeable loss in text contrast. Remember, this is the Note the user views or edits at the moment. Personally, I don't understand that decision.

Let's have a look at a mockup which gives an overview over all the different colors and text elements. Although this is a rather old and chunky picture, you may get the point how it will finally look like... With the help of this picture, we checked the appearance on a variety of different monitors and displays.


Color is good. If you can perceive it!

At the beginning I said something about the importance of color in graphical representations. But there are people having problems to differentiate colors - maybe you know some of them personally (Wikipedia, Color Blindness). First, we checked our colors against color blindness with the help of the open source image application "The Gimp" which provides different filters to simulate color deficient vision. Look...
Yes, I'm not too glad that we can only guarantee to differentiate the first two or three authors. But you may agree that it is very hard to provide bright and decent pastel colors which differentiate well when considering such a high number of authors. This is already an issue with cheap monitors which have a limited viewing angle stability - same colors may appear different when displayed at opposite screen areas. And so we have to remember the most important principle when it comes to color: never code information exclusively with that. We respect that by showing the names of the authors in each Note.

People may not only have difficulties with colors, there are also other disabilities who have to be considered. Here is how it looks like, although it may hurt if you are not used to it...

That's it. So what is your opinion on how we worked and what was the outcome? We think color coded information is good, but we shouldn't rely on it. I experienced the selection of colors to be a balancing act of both providing a pleasing design and respecting all the users' needs. In any case, the i-Team hopes that you will be happy with the design we chose and that it'll bring freshness and improved usability for the upcoming OpenOffice.org 3.0 release.

If you want to know more about it, then please have a look at the Notes2 color wiki page. And, as always, if you have any comments or opinions to share - simply share it!

Have a nice day,
Christoph

Thursday, August 14, 2008

Let's do the Math

This time I'd like to point to something which is in early stage of development. The "OpenOffice.org Usage Feedback Extension" [1]




The OpenOffice.org Usage Feedback Extension is an extension that collects anonymous data about how OpenOffice.org is used. This information is used to better understand how people use OpenOffice.org.

Our plan is to have this extension final on release date of OpenOffice.org 3.0.

As mentioned above, the data will be used to do some statics on the usage of OpenOffice.org. For example: We can better figure out how frequently specific menu- and tool bar items are used. The collected data will help us to create a decision base for user interface changes. It allows us to decide better on defaults, or items displayed by default.

The anonymously collected data will be published in form of diagrams/tables on a page on OpenOffice.org.

As always, feedback and comments are welcome.
Directly here, or on the discussion page of the Extension Specification.

There is momentary nothing to download, but this will change soon.

Stay tuned.

[1] http://wiki.services.openoffice.org/wiki/User_Experience/OpenOffice.org_User_Feedback_Extension

Monday, August 11, 2008

OOo User Experience Project Lead Meeting in Hamburg

Sun Microsystems User Experience team had a meeting with Christoph, our OOo User Experience Co-Lead. Christoph stayed in Hamburg to meet his Notes2 iTeam, so we used this opportunity to prepare the upcoming quarterly review for Writer and to discuss general UX related things.


From top left to bottom right: Christoph Noack (OOo UX), Éric Savary (Sun QA), Max Odendahl (OOo Dev), Mathias Bauer (Sun Dev),
Christian Jansen (Sun UX), Andreas Martens (Sun Dev), Frank Loehmann (Sun UX)


I think the meeting was very productive and we also had much fun showing Christoph and Max a little bit of Hamburg at night. After dinner we went down to the harbour to have a look at the Hamburg Cruise Days. Nearly every ship/building was illuminated with blue light.


Blue illuminated Rickmer Rickmers and Disneys Lion King musical hall in the back.

I hope we can repeat those face to face meetings beside our weekly telephone calls.

Monday, July 7, 2008

Usability and handedness – is it considered at conceiving software?

Within the software products / tools I have ever installed and worked with I have never discovered one, which pointed explicitely to the consideration of handedness.
So it seems, that one is working with software, which is mostly (always?) designed for right handers.

Is this assumption right?

How to satisfy handedness?

To meet the need of right and left handers at conceiving software one needs to know and be able to identify, which hand is supported in which way.

Does it really suffice to switch the mouse keys and mirror the menu and toolbars?

What needs to be considered at conceptual design of software therefore? In my opinion this is a topic really worth mentioning.

Your feedback is welcome.


Best regards,

Bettina

Thursday, June 19, 2008

Improving the Usability: The new Extension Manager as an Example

I would like to introduce the new GUI of the Extension Manager.
The aim of this refining was to ease the use of this tool and giving it an appealing look.

The problem:
This dialog has formerly been rather overcrowded with all functions available at the same time and thus difficult to understand how to use.
The user was forced to consider too many steps before getting results, while beeing in the context of extensions which at that days were not in common use for every user.

The solution:
Which buttons need to be available all the time and which are only relevant for a selected extension? According that assignment the buttons got arranged and their visibility reduced, so that the user has certain functions only available if needed. That should help to keep the user's focus on the work flow.
We also reduced the number of further dialogs coming up on top of the Extension Manager at certain actions by integrating it within the UI.
Well, not many ways exist to arrange an appropriate UI for the purpose of handling extensions, the result shows similarity in the style of the well known Firefox.

Here are some pictures showing the old and new Extension Manager:


The old UI


The new UI: Adding an extension


The new UI: After adding an extension

Wednesday, June 18, 2008

Monday, June 16, 2008

Quarterly Review is done – what is next?

Some Quarterly Reviews for OOo are still running and some (i.e. the review for Calc) have already been finished.

The report of such a review consists of different sections. One section lists issues the teams are already working on and another the most important issues (i.e. a Top 20 of the highest voted issues). So now the question is how to start working on these most important issues to get things done?

I want to start the discussion on those issues as early as possible. If we have a good proposal in place, the chance to get those issues done is much higher. Furthermore we have the chance to do it on a high quality level if we do not start thinking about an issue when we have resources in development.

Discussions held in issues are often nonproductive, so I want to call for proposals, a kind of one pager, at the OOo Wiki. The issue itself just contains links to proposals but the discussion starts on the discuss@ux.openoffice.org mailing list. There could be more than one proposal for an issue, but in the end the UX team should recommend one proposal to development.

If the implementation of such an issue starts, the iTeam gets the supported proposal as a recommendation how to solve that issue. Maybe it is a good idea to have the original author(s) with that iTeam too.

Feedback welcome!

Best regards,

Frank