The OLPC User Interface
If you are reading this post from a news reader please click through to the page, as there’s an embedded video to watch.
If you’ve been a reader for a while, you may remember a short post of mine about how enthusiastic I was with Negroponte’s idea. I’ve been following OLPC’s development for a while now, and this post carries some personal weight in it, first because I care about the project and second because I care about UIs and Usability.
Dumbed down – sure; Stupid – no, thanks
The user interface for the OLPC, code-named Sugar, tries to make it easy for a child to use the computer to perform tasks like browsing the web, reading and writing documents, chatting online and play a few games. Thinking about it, that’s fantastic – anything that allows children to be connected is a great achievement.
However, by literally trying to revolutionize the desktop metaphor (or ignoring it completely), Sugar is becoming a complex, ridiculously iconic interface that does little to help and a lot to confuse whoever is using it. Have a look at the video below to actually see what I mean:
Sugary problems
If you’re interested in learning why the UI behaves the way it does, you should have a look at the Human Interface Guidelines for the OLPC, particularly the section on the Laptop Experience. But here’s a few of my considerations on why Sugar is just wrong:
- The “Zoom” metaphor is harder to understand than the desktop metaphor. Sure, we’ve been living with the desktop metaphor for years (whereas the OLPC children won’t have), but intuitively the desktop is easier to grasp than a set of nested behaviors.
- The whole system is built around icons – icons are ambiguous and lead to confusion. Naturally, a text and icon combination for the UI would make much more sense. If this is a laptop that’s meant to have the children share and learn, it should be simple, not cryptic. See the image below and try to figure out with no “manual”, what you are looking at.
- Removal of critical elements, like the address bar on the firefox instance or a field showing who you’re chatting with in the chat client is strange and taking information away, not providing it.

Salty conclusions
I can’t stop thinking that the people behind this got carried away. The OLPC is a fantastic project that if successful could play a major role in changing the lives of many children. With such an ambitious goal, it is easy to go with the flow and try to cause an impact by making more changes than necessary to the UI in order to try and be revolutionary. You didn’t have to.
I also can’t stop wondering whether going from an established open source environment like Gnome or the lightweight XFCE and making it dead simple (but not exclusively iconic, for crying out loud) would have been a better approach for this project.
The final fact is that this interface needs a lot of work and a lot of testing with the real people who will really benefit from using it. My guess is that either this hasn’t happened it, or it hasn’t happened enough. From my point of view, shipping the UI like this is a failure, because if people all around the world, who have been dealing with computers for years and years don’t get it, a child seeing one for the first time sure won’t either.

I caught this on Digg this morning, and I can’t see why anyone would think it is an advantage to people in the developing world to learn something so completely different from what people in developed countries use. How does it help people in developing nations to learn computer technologies that no one else uses? Projects like OLPC are supposed to bring people closer together (I think), not isolate them in new ways.
Simplifying or improving the basic user interface that operating systems in the rest of the world use makes sense, but introducing something that is so radically different from what the rest of the world uses that they can’t relate to us through that technology is a disservice, in my opinion.
Comment by Josh — November 28, 2006 @ 5:18 pm