Does Open-Source Software Fall Down on Usability?

Lori Halley 15 August 2008 4 comments

This is the second part in our series taking a closer look at free and open-source software: the real costs, the barriers, and the trade-offs; the best FOSS alternatives to “brand name” software; and the resources to help you make the most of it.

One of the on-going criticisms of free or open-source software (FOSS), as a general class of software, is that it’s lacking in usability. But what does “usability” really mean — to software developers and to those of us who depend on a collection of software to carry out the essential tasks?

Usability is closely related to usefulness, of course, but it’s more specifically about ease-of-use. As users of software, we’re primarily concerned with the usability of the interface between us and the program — the graphics, text, and sounds that the program presents to us, and the actions such as keystrokes or mouse movements that we use to control the program.

More simply, we can think of usability in terms of its 5 key components:

  • Learnability: How easy is it for new users to learn how to use the system, and become proficient with it?
  • Efficiency: How quickly can you perform the tasks you want to do, once you’ve learned the software?
  • Memorability: When you haven’t used the software for a while, how easily can you pick it up again?
  • Errors: How often do you make errors with the software, and how eay is it to recover from them?
  • Satisfaction: How pleasant do you find the experience of using the software?

As mentioned, FOSS comes in for a lot of criticism for a failure to measure up in all these areas. Matthew Paul Thomas, who views FOSS from a ringside seat on the Ubuntu team and has been wrestling with this issue for years, offers 15 reasons why free software has poor usability, along with suggestions for how the development process might be improved.

Many of these problems are with volunteer software in general, not Free Software in particular. Hobbyist proprietary programs are often hard to use for many of the same reasons. But the easiest way of getting volunteers to contribute to a program is to make it open source… [and] it’s in Free Software that we see volunteer software’s usability problems most often.

His article gives an interesting glimpse into the software development process, but I suspect that many of those underlying problems that a concerned developer may see so clearly are often much less obvious to us — the average users, who see the software only from one side of the interface.

After all, how much do we care about the elegance of the underlying code, or whether a specific function was patched in as an afterthought?

As long as the software works, right?

But “programming and human interface design are separate skills, and people good at both are rare,” Thomas notes.  A shortage of skilled designers in the volunteer pool for open-source projects means that design aspects may not come fully into play until after the coding has begun — and that can have a direct impact on the user experience.

[T]he more code has been written, the harder it is to fix a design problem — so programmers are more likely not to bother, or to convince themselves it isn’t really a problem. And if they finally fix the interface after version 1.0, existing users will have to relearn it, frustrating them and encouraging them to consider competing programs.

It’s true, isn’t it?

When we install a major update, and suddenly face an unfamiliar screen or can’t find a much-used menu item, we lose some of the sense of familiarity that’s such a big (and personal) part of how “usable” the software has become for us through the habit of use.

In fact, I’d like to nominate “Familiarity” as item number 6 on that list of usability components — because, when it comes down to firing up your computer and getting tasks done, the hands-on user is the best judge of any program's usability.

What do you think? How does open-source software compare to "brand name" software for ease-of-use, in your experience?

Get a Special Report on Simplifying Membership Management

Enter your email and receive this special report in your inbox.
Lori Halley [Engaging Apricot] Lori Halley [Engaging Apricot]

Posted by Lori Halley [Engaging Apricot]

Published Friday, 15 August 2008 at 1:34 PM

Get a Special Report on Simplifying Membership Management

Enter your email and receive this special report in your inbox.

Comments

  • Dmitriy Buterin [Chief Apricot] Dmitriy Buterin [Chief Apricot]

    Dmitriy Buterin [Chief Apricot] said:

    Friday, 15 August 2008 at 6:57 AM

    Here is my personal perspective:

    FOSS is great for a non-profit IF they have a friendly geek on board (and can count on him/her in the future) to set it up, maintain and help with training etc. This is the biggest hidden cost of FOSS.

    The second issue is the need to train users. Non-profits typically rely on volunteers to help with database and website updates. many of these people are non-techies. FOSS typically have great functionality - but frequently very arcane user interface, targeting power users and not meeting the novice users needs as well. (I do have to say that lots of commercial software has very poor interfaces too!)

    Finally, a lot of FOSS has to be hosted somewhere so you need to procure and setup servers - AND maintain them (at least for security patches).

    In myy experience, most small non-profits are better served with a hosted solution - it can cost next to nothing and removes the need for maintaining your own servers.

  • Lori Halley [Engaging Apricot] Lori Halley [Engaging Apricot]

    Lori Halley [Engaging Apricot] said:

    Friday, 15 August 2008 at 7:57 AM

    Yes, usability is so often tied to technical ability, isn't it? Your note about the need to have a "friendly geek" on board ties in with one of Matthew Paul Thomas's points about how open-source software evolves:

    Volunteer developers work on projects and features they are interested in, which usually means software that they are going to use themselves. Being software developers, they’re also power users. So software that’s supposed to be for general use ends up overly geeky and complicated. And features needed more by new or non-technical users — such as parental controls, a setup assistant, or the ability to import settings from competing software — may be neglected or not implemented at all.
  • Kate LaFrance said:

    Friday, 22 August 2008 at 7:07 PM

    Yes, I have big issues with WordPress for this reason. I appreciate that others love it but I don't have enough left brain to even begin to get it!

  • zahid said:

    Tuesday, 09 September 2008 at 2:44 AM

    Hello,

    I am a masters student in computer science and i am going to take my thesis and i am very interested to do my thesis on "usability of open source software" i want some suggestion from here..i want to know which key questions should i consider to do my thesis and i want some direction about my thesis also..

    Please help.

    Thanks in advance

    Zahid

Sorry, this blog post is closed for further comments.

Search: WildApricot.com 

About results ( seconds) Sort by: 
Sorry, an error occured when performing search.