A Close(r) Look At OLPC Human Interface Guidelines
feranick writes "There have been a lot of articles on Slashdot about the OLPC project, most of
them regarding the hardware, the social impact or the cost of the
operation itself. However the software development,
specifically in the GUI didn't get so far much attention. This
blog summarizes some of the OLPC
global interface guidelines. You will see that what is really
new in the laptop is not the laptop itself, but the completely new idea
behind the design, where instead of applications you have activities,
documents are now journals,
'application bundles can be signed by
whoever works on them — because
there is a view source key on the keyboard,
anybody can modify an app
and distribute it'. It really looks like if this is successfully, we
could see a new breakthrough in GUI design also in mainstream PCs: "This
UI is quite simply one of the deepest and most interesting redesigns of
the desktop user interface ever produced. It makes MacOS look like what
it is — boring and unoriginal.""
The OLPC hardware is very nice actually. I've held it in my hands, and it is sturdy and looks nice. The worst part is the keyboard, which is dire - hopefully this is something they will work on in the future to improve. Sadly it had run out of battery when I got my mitts on it, so I cannot comment on the user interface, and the operation thereof.
However there are some interesting points in the blog post - it just depends on whether they are valid for the OLPC.
Fitts Law in corners for example works well when you have a mouse you can fling into the corner. But the OLPC has a trackpad, and we all know they're not so good for flinging the cursor into the corner. Something localised would be far better, for example a double-tap + pop-up directional menu for actions. Also Mac OS X lets you assign the corners to actions, contrary to his post. Many people disable these because they're annoying!
"It makes MacOS look like what it is -- boring and unoriginal."
The new GUI might be revolutionary, and useful, and create the new paradigm. Just like MacOS did.
OLPC might make the now mature MacOS look boring. But if it makes MacOS look "unoriginal", just because so many have copied it, then the audience must be a world of children with the first laptop they've ever seen. Because MacOS originated the features that MacOS still keeps the cutting edge - until something like OLPC maybe replaces it. Even if so many others have copied it, MacOS is the original.
Unless you want to dig into MacOS's roots, like the Apple Lisa, or the Xerox Star. Which were prototypes, even the failed release Lisa. All PC design has been evolutionary, however big a leap one subsystem (like a GUI, or a LAN, or a laser printer on it, or an input peripheral like a mouse) makes. But those seminal roots just show how original was the MacOS, which made it work with its original improvements and integrations.
We should replace the ancient Mac GUI paradigm. It was revolutionary in the home and office, because it finally put the home and office on the screen, replacing the algebra classroom and typesetter formes. The original. Now it's over two decades old, and we're all more familiar with PCs than with file cabinets and document scrolls. So when we improve the paradigm, it's good to target the original. Pretending that MacOS isn't original makes it harder to beat it.
--
make install -not war
There's a VMWare image of the OLPC system (forget where...found the link on OSNews.com) and I downloaded it and played with it a bit. The "Sugar" interface is one those things that presumably works better on the intended hardware, because moving the mouse around to get to the "desktop" or whatever it was got old really fast.
The other issue, which I can appreciate is a very non-trivial task because it has to work with non-computer savvy kids (and presumably adults) in a variety of languages, is that the icons didn't make any sense to me, nor did most of the interface. I got that the globe icon was a browser, but that was pretty much it. A couple of apps I still don't understand what they do.
Being that it's Linux underneath, the standard ctrl-alt-backspace killed the interface and I was able to log in as root (no password) and poke around. The one programming language they include is Perl, and that got me thinking about why not give the kids an interface or some capability to develop their own software too? The next killer app could be written by a kid on a OLPC machine. It looked like they also included a version of Squeak (Smalltalk) as well, but I only saw the interface come up once and wasn't able to get back to it again. Would they ship the docs in all languages as well?
Directories is a real-world text-based metaphor. Interestingly enough, the term is used primarily for text-based interfaces (such as CLI's). Call them what you want, but folder is the better metaphor for more people. Additionally, the fact that the icon is an image of a folder certainly helps the metaphor. What would a directory icon look like? A phone book? A mall directory?