The prototype phase didn't end on July 4 after as originally planned.
It is still going strong and eliciting a great deal of enthusiasm and
feedback. In this blog post we want to provide answers to some of the
negative comments we've received. Of course we have been thrilled by
all the positive comments, too, but the nay-sayers have been vocal, so
we need to be vocal, too.
Some of the negative comments posted after in our July status update
post were:
a) Oh no! Not like Microsoft!
b) My monitor gets wider not higher (horizontal vs. vertical UI)
c) Do not copy ribbons. Innovate do not imitate!
d) Why are you killing menus?
e) I/Everyone hate/s 'ribbons'!
f) Make it optional. Keep classic interface as an option.
g) 'Ribbons' are only for beginners/newbies.
h) Professionals (like me) are distracted by the new
interface/'ribbons' because I/they already know were to find the
desired functionality.
i) It is so ugly!
Before providing answers, we want to remind everyone of our goals and
a tidbit about doing such development work in public.
Our mission:
“Create a User Interface so that OpenOffice.org becomes the users' choice not only out of need but also out of desire”
and our project goal:
"... to know and to understand our users as they are, and to help them accomplish what they want to, by providing efficient access to valuable functionality through a desirable user interface."
Please trust us that we will not implement anything that has not been
tested and validated in real-life situations.
Working in the "open" can be tough. It seems that everyone under the
sun already knows what we should do. Regardless of what we present we
will always get at least one comment saying our idea is wrong/stupid
(See a, c, e). The team always has to keep in mind that many comments
are not from average users of OOo. The UX team has to weigh all
comments carefully. Presenting a mid-fidelity prototype means risking
that people do not understand the purpose and think the next product
will look like this (i).
We also created a survey, that shows up when the prototype gets
closed. (This requires Java 6 installed, because the system's web
browser is called). The survey has more questions now since last
Friday. New Prototype, new survey. ;-) The results of the survey are different from the negative comments on GullFoss. We think
because those users who fill out the survey give the prototype a test
drive at least for a moment. But who reads our blogs and tries the
prototype? The average OOo user? No! So only real live testing can
show us if a new UI is suiteable.
Developing a user interface (UI) for office sorftware is not an easy
job, because this software is used by unique users with all skill
levels and a huge range of tasks. Nobody wants to be a beginner, at
least not for long :-) , so we have to focus on intermediate users
while not distracting expert users.
When you analyse office documents, you see that most users only use a very basic set of features out of what OOo offers. So it seems
that we are already done, because OOo could do so much more. Really?
But why do those office documents look so basic even if they are made
by experienced users? We only know a few people who are good in
techniques and design at the same level. So users should concentrate
on what they are the experts in: the document content, and not have to
design/define/layout each and everything inside their document on
their own.
Most expert users stated that they already know where to find the
fucntionality (h) and that no new UI is needed, so that only beginners
(g) would take any advantage of a new UI. We want to provide rich
formated document pieces like tables, header, footer, indexes, etc. in
galleries, so that the user can easily choose from professionally
designed ones. This allows all users to create powerful and beautiful
documents.We need some kind of new UI to offer those galleries.
This new UI needs a home. So the question was where to place it. The
reading direction in western countries is from top left to bottom
right and users are used to finding the interface on top of the
document area. Furthermore the height available for a bar on, e.g. the
left side, is too low for the amount of functions, especially on small
displays like netbooks. Also we did not want to spread the
functionality all around the application. So the team decided to go
with a horizontal on top even if monitors are getting wider (b) these
days. Most users use the software as it is out of the box, so we have
to focus on a good default. But there is nothting to say that the
user can't configure it to fit their specific screen or work needs. It
is a clear requirement that the new UI must support a minimized
visualisation (fold open or change to float) and it should support a
vertical visualization in a second step. Configuration possibilities
could be added in future versions.
Our prototype did not kill the menus (d). They are still there! Even
the new prototype, which is in the making, will keep at least the same
structure (File, Edit, View, Insert, Format...) users are used to
these days, but it will provide new graphical possibilites where we
need it to provide rich formatted document pieces. The next prototype
will also implement a context-sensitive interface approach.
We do not want to copy the ribbon (c) interface. But what makes the
'ribbon'? The tabbed interface? No. On top navigation? No. Rich formated
document pieces in galleries? Maybe, but templates are not new and other
products did provide those possibilities earlier. Do we have to keep the
classical interface as a second interface? This would mean that it has
to be maintained as well as the new one. So maybe it is a good idea to
offer this as an OOo extension, if really required by users (f).
We hope that we provided some answers to comments/questions posted on
the previous post on
Project Renaissance.
Please stay tuned for the
new prototype being released by end of next week!
Best regards,
The Renaissance Team