The birth of the Microsoft Office “Ribbon”

New ideas for user interface components don’t come by very often.  For example, the pointer, icons, and toolbars have been around since the late 1970′s courtesy of the work done at Xerox PARC.  It’s safe to say that the computing environment in the late 70′s was quite a bit different than it is today, so it’s only logical that some of the paradigms developed then need a modern refresher.

There have been high profile attempts at designing new, complete, usable components to solve specific problems such as interactive assistants and horribly bloated CD lists.  But in recent memory, all pale in comparison to the Ribbon that Microsoft introduced in Office 2007.  The Ribbon is what replaced the toolbar system used in previous versions of Microsoft Office.

office ribbon

The ribbon effectively solves the problem of displaying the functionality of a very complex and feature-rich piece of software like Word or PowerPoint much more effectively than toolbars, tabs, and other competing concepts.   In combination with gallery views of icons, and organising things in use-driven groups, the solution is elegant and ages well.  It’s unfortunate (read: fucking brutal) that Microsoft is patenting this idea in the current climate of software openness and growth, but I digress.

Jensen Harris did a presentation at MIX ’08 about the history of Office and how the ribbon was developed.  A must watch for any employed interface designer:  the ideas about religious tenets, building lots of high-fidelity prototypes,  evaluation over a number of months, and constraining ideas to make reasonable decisions are worth discussing.

YouTube video below, but the complete presentation is available from Microsoft.

Bridging the digital divide between rich and poor using cellphones.

Today is the 20th birthday of the World Wide Web, and in celebration there was this telecast on French TV from CERN about the future of the web. Stéphane Boyera’s five minute talk stood out as being particularly interesting to me.

There is a digital divide in the world, as there are 5 billion people that have never used the Internet.  Bringing them on board ought to be a priority for agencies involved with human development.  This doesn’t necessarily mean that everyone needs access to a traditional computer. In much of the developed world, even in places where there is no running water, there are cell phones.  Cell phone networks cover 80% of the world’s population. I can attest to this fact in my travels to India. In the middle of the foothills of the Himalaya’s there was limited running water, sporadic electricity, no sewage, but every family has a Nokia with SMS and a web (WAP?) browser.

The idea that services (education, banking, emergency services, and the like) can be delivered via mobile platforms is the cause d’etre of this W3C working group.  From their website:

Mobile Web for Social Development (MW4D)

The MW4D Interest Group explores how to use the potential of Information and Communication Technologies (ICTs) on Mobile phones as a solution to bridge the Digital Divide and provide minimal services (health, education, governance, business,…) to rural communities and under-privileged populations of Developing Countries.

Amazing ideas, definitely worth checking out.  As with any good idea, there are a variety of challenges, from availability of information, software development, and information literacy of the population.

Though it’s a solution that will gain traction in the future.  From a developers perspective, if I have use cases that involve use by emerging internet populations, I better be thinking about mobile browsers and serious localisation. The BBC speaker at the same conference mentioned that 20% of hits to the BBC website from Africa already come from cellular phones.

Settling on a Research Topic

To be perfectly honest, I was admittied into my Masters program with zero funding. In retrospect, starting a two year+ project with no guaranteed income wasn’t the greatest idea, for a variety of reasons.

First, every semester I hope/pray to get a Graduate Teaching Assistant job, which luckily gets easier and easier as I accumulate “seniority points.”

Second, no funding means no specified project, which means freedom to choose any research topic I please, as long as my (very lenient/forgiving) advisor is OK with it. Well, it’s been about eight months since I’ve come back from India all ready to start researching, and only two days ago did I actually settle on a topic.

Eight months is a long time to pay tuition, and follow dead ends with literature reviews. Also, those months are expensive if you waste your time on partying, girls, video games, Union involvement, student government, keggers, new housemates, motorcycles, trips to Mississippi, Vancouver, Ottawa, and so on. Well .. maybe it wasn’t a complete waste, per se :)

Finally, I’ve settled on a topic that I’m truly interested in.

Continue reading

User Interface Design Patterns

This is information about design patterns that can be used in the design of user interfaces. The patterns I’m particularly concerned with deal with the look, feel, and behaviour of modern interface elements, such as those found in browsing “the Web.”

Patterns are often employed in object oriented software development and engineering, much more so than user interface design. I believe that by applying patterns at the user interface layout and design level, employing a “top-down” approach, we can avoid some situations where deep-system code decisions impede usability of the resulting user interface.

Continue reading

Proudly powered by WordPress
Theme: Esquire by Matthew Buchanan.

Switch to our mobile site