What Open Source Can Learn From Apple

Linux and open source have long struggled to gain acceptance from the wider (read: non-technical) audience. This has improved in recent years, but still has a long way to go. Columnist Matt Asay suggests that perhaps open source projects should attempt to emulate Apple's design philosophy, with whoever succeeds becoming the "winner" of the hearts and minds of the vast majority of users. "Some projects already accomplish this to some extent. The strength of Mozilla, for example, is that it has figured out how to enable 40 percent of its development to be done by outside contributors, as BusinessWeek recently wrote. The downside is that these contributors are techies, but the upside is that they're techies who add language packs, accessibility features, and other "niche" areas that Mozilla might otherwise struggle to deliver. This suggests a start: enable your open-source project to accept meaningful outside contributions that make the project reflective of a wider development community. But the real goldmine is broadening the definition of "developer" to include lay users of your software. The day that I, as a nontechnical software user, can meaningfully participate in an open-source project is the day that open source will truly have won."

Comments

user analytics

[alain94040]

I agree with the article that user involvement is key. However, users are clueless about what they really want and you can't possibly use them to write the specs of your product! On the other hand, developers tend to reject criticism from end-users because they lack technical expertise.

I can think of one approach that might work: build a really good analytics library that would measure various usability aspects. Applied to Firefox for instance, it could generate data on how the average user goes about finding a particular setting, how long it takes them to perform a given action, etc.

Developers would respect the hard, factual data that the analytics would generate. It would make it easier for the minority of usability engineers to argue against feature creep.

Re:user analytics

[AshtangiMan]

Agreed. The lay user will only be able to meaningfully participate in early design phases (think requirements) and then again in testing (especially UI testing). It seems to me that they already have the ability to participate in these ways. Any attempt at involvement in the architecture design surely would only hinder good software practices.

Re:user analytics

[ByOhTek]

I think a bit better of a way to put it:

5 out of 10 users know what they want, but can't express it in a manner that communicates it sufficiently well to achieve it.
4 out of 10 users haven't a clue what they want, but think they do.
1 out of 1 users know what they want and can express it.

And then you have the developers, who want to make something with nice nifty features, but don't want to be bothered with the polish.

This reminds me of a friend who is a senior analyist has a paper on her cube wall, I've seen two variants of the theme. It has a picture of a sports car with the caption "What the users want". This is followed by the picture of a UFO (in some variants a fighter jet) with "What the developers want to make". This is followed by "What the company is willing to spend money on" and it has some small compact car. And then finally, a picture of a really funny looking "tricked out" tricycle with the caption "What ends up being produced".

Re:user analytics

[Dare nMc]

then lastly in plugins and add-ons that don't require changes to the core of the project. Clearly:

The day that I, as a nontechnical software user, can meaningfully participate in an open-source project

is referring to things like: addons.mozilla.org not to things like adding crud to every projects main branch.

Re:user analytics

[T Murphy]

users are clueless about what they really want

They know what they want. Ask them what they want in a car and they'll say an SUV with room for 8, at least 50 MPG, all the latest gadgets and costs less than $12,000. If you can't provide that then it's your fault.

I mean this for humor's sake but thinking about it I'm scared that it might be an accurate description.

Re:user analytics

[hobbit]

But would user analysts spend their spare time analysing users like hackers spend their spare time hacking?

Re:user analytics

[geekmansworld]

"However, users are clueless about what they really want and you can't possibly use them to write the specs of your product!"

This demonstrates the inherent problem with open source's attitude towards user demands. To them you are either (a) a Programmer, or (b) a Grandma.

I'm an IT professional, a power user, and consider myself a connoisseur of good interface design. But I've never coded a line of C++ in my entire life. Does this make my input useless?

For example, I've been trying to get bugs in Thunderbird fixed for a while that seriously impede usability, but the development team doesn't seem to care.

Open source is always talking about how they can win over more users. But how do you win over users if you don't focus on usability?

Re:user analytics

[Estanislao Mart�nez]

I agree with the article that user involvement is key. However, users are clueless about what they really want and you can't possibly use them to write the specs of your product! On the other hand, developers tend to reject criticism from end-users because they lack technical expertise.

I get the impression you didn't understand the article then, because quite early on they approvingly cite this (which they attribute to Jason Snell of MacWorld):

"Apple excels at creating products that the general public likes because the company is driven by design, not by engineering." [my emphasis]

They're not simply asking users what they want and then just doing what the users say; that would indeed be a recipe for disaster. They have design people in charge of figuring out what the products should be, validating proposed designs against user focus groups, sitting end-users down for experiments to see how usable something is, discovering usability problems with existing products, etc. And then they use this sort of information to decide what to build.

I can think of one approach that might work: build a really good analytics library that would measure various usability aspects.

Won't work. You need to know what the user is trying to do to interpret the data, and the software can't read the user's mind.

Re:user analytics

[jo42]

senior analyist has a paper on her cube wall

There is also this classic product development comic.

Re:user analytics

[cheier]

Because I can appreciate and judge great cuisine, doesn't mean I can make it, yet the feedback these judges provide is the cornerstone for a chefs continuous improvement. People who use and judge interfaces in the field are usually a great resource to find ways to improve it. If it is a hit to the interface designers ego that some interface element isn't where the users would like it to be, suck it up. Make it better, always improve it.

Re:user analytics

[je ne sais quoi]

I'm an IT professional, a power user, and consider myself a connoisseur of good interface design. But I've never coded a line of C++ in my entire life. Does this make my input useless?

I'm a scientist who writes C code on a weekly or semi-weekly basis on average and have written a theme for e17 as well as done some writing some small "in house" type guis used for interface with instruments. My bug reports to open source projects are largely ignored as well (to the point that I rarely issue one now). But then again, Apple devs ignored all my complaints about the Finder when they removed the horizontal scroll bar from the Finder when you clicked on a special location awhile back too. They had a vision of what they wanted to do and they did that and didn't care what I thought. It's nothing to do with you, it's that open source developers are doing this usually for some small salary or part time and what they get paid to do is sometimes not what what you want them to do and there's only so many hours in a day.

Re:user analytics

[DrgnDancer]

Probably not notice anything :-)

Re:user analytics

[Actually, I do RTFA]

This demonstrates the inherent problem with open source's attitude towards user demands. To them you are either (a) a Programmer, or (b) a Grandma.

Close. To open source developers you are either (a) The developer himself, or (b) Not the developer himself. If (b) then the excuse is either (i) you are a Programmer - develop it yourself, or (ii) you are non-technical - I can ignore your input.

Open source is always talking about how they can win over more users. But how do you win over users if you don't focus on usability?

You cannot! Usability is very important. And everyone should concentrate on it. But not me right now, I just have this nifty little feature to add for myself/my close friend/etc.

Closed-source and other funded software can pay people for the unfun work of UI design and documentation.

Re:user analytics

[Weedhopper]

and 11 out of 7 statistics are just made up.

It's not about contributers

[Mork29]

It's about standards. Apple's UI guidelines are very well written, and very well thought out. When developing your app, you don't need to spend a lot of time thinking about the proper place to put something, because it's generally obvious. This makes it so much more user friendly as a user can pick up on things in a very intuitive way. It also gives a general "feel" to the entire operating system.

When working with Objective-C/Cocoa in XCode, your almost forced to give your app a very Mac like feel to it. The same goes for the iPhone. Everything you'd want in your interface is already pre-built, so everybody's apps have a familiar feel. I know I've heard the exact opposite when developing for something like the Blackberry.

Having more people contribute with no clear guidance will just make things worse.

Re:It's not about contributers

[davester666]

"Apple would never allow that"

What do you mean by this? Both on the desktop and on the iPhone the developer has complete control over virtually every pixel of their interface (I haven't messed with drawing in the menu bar proper, as you can do custom drawing in menu items, but I'm not sure drawing the title's in the menu bar itself).

Hell, Apple itself deviates from it's own standards, as well as wildly popular applications such as Delicious Library (just as an example). Apple has always expounded that they have "guidelines", not "rules" or "laws" or "requirements".

Re:It's not about contributers

[clintp]

Companies that are successful in this field have UI experts -- and the management to back them up -- to say

"Yes, this works adequately, but it looks awful. Sorry, you can't ship it."
"Yes, this works adequately, but it doesn't blend well with the rest of our product line. Sorry, you can't ship it."
"Yes, this works adequately, but it's hard to use. Sorry, you can't ship it."
"Yes, this works adequately, but there's too many extraneous features. Sorry, you can't ship it."

(And of course, the ever popular "It was a nice product, but we're abandoning it for something simpler, prettier, and not overburdened with legacy.")

UI guidelines give everyone a place to start talking about the problems (looks/blend/hard/extraneous) and give the development teams a starting point. If there truly is an earth-shattering eye-popping UI feature (a widget) that the guidelines don't allow, then you alter the guidelines after buy in. This *then* requires re-engineering the rest of the applications to account for that great widget and use it where applicable to maintain consistency.

It's expensive and it may seems pointless, but no app is an island when you're trying to engineer a great user-experience.

Linux generally tries to compensate by providing standard frameworks for UI. But there's the I-Love-Standards-There's-So-Many-To-Choose-From problem and that there'll always be the cowboy that turns out a useful app that looks and works different from everything else.

Re:It's not about contributers

[nine-times]

I don't even think Apple's success is about UI guidelines. I mean, sure, they help, but Apple seems to have a... I don't know... what's the opposite of "tin ear"? Anyway, they just have a very good sense of design. Not just UI design like "graphic design", but engineering a product, like figuring out which features to include and how those features should work.

I've always thought that one of the interesting differences in design approach that Apple uses is that they don't throw in the kitchen sink right away. Some people hate them for it and feel like their products aren't feature-rich enough, but it really seems to work. They just start with a basic product that basically does one thing simply and well, but might not yet have all the features you want. Then their next release of that product adds a few features, but very carefully integrated in to the existing feature set. The next version adds some more in the same way. What you very rarely hear as a criticism about Apple's products is, "this feature feels tacked-on". You might hear, "It doesn't hear every feature you might want," but it's usually followed by, "but if you only want the features it has, it will do those things well."

Microsoft, for example, has in the past had the exact opposite design philosophy. It used to be that version 1 or 2 of their products had pretty much every major feature they're ever going to have, but none of it was actually usable until version 3. It's only then that Microsoft seems to focus on making those features work well together.

Re:It's not about contributers

[Actually, I do RTFA]

And overly-restrictive UI requirements will prevent the interface from ever evolving.

It's a GUI. Evolutions happen in spurts. There was (in Microsoft land) the Start button/taskbar in Win 95, and the widget panel in Vista. Oh, and an add on that shows all the open windows when you alt-tab. Whole lotta evolution. Apple has had three evolutions, their taskbar variant (the dock?), their widget panel, and their program switching, show all the apps screen.

I suppose, in fairness, Vista and some release of OS X also added screenshots when you roll over the icons on the taskbar/dock.

But interfaces have had for evolutionary steps in 14 years. And all at the OS level. I think that's fine, don't you?

Linux users...

[Anonymous Coward]

... only care about EXCLUSIVITY.

I want to make clear that I like Linux and free software; in fact I'm writing this from Mandriva Linux. But we have to accept the awful truth: many Linux users would be using Mac OS X if they weren't a misers. Why do I say that? Because even if it hurts to all of us, I have to say that the Linux community doesn't appreciate quality and freedom.

Normally, Linux software DOESN'T have the same quality that propietary software has. It's normal, it is not bad. After all, free software is free (as in speech) and the other one is costly... No one would use MS Project if GNOME Planner did have the same quality. Is good to have freeware software for things that are not serious, though.

The other reason why someone decides to use Linux is to read the source code, it is a good reason. But let's be serious, how many of you read the code of every update your apps recieve, and when you make sure everything's okay, you compile them and execute them? Nevertheless, I appreaciate the freedom to make modifications. Even myself have modify apps to see on the "About..." screen my own name.

And, the other reason, the reason I would walk on hot coals for it, is that at least 50% of Linux users, use Linux just for exclusivity.Just like Apple is the shit on usability, but more than 50% of Apple users use their products because of the "little apple" logo that appears on the notebook; most of the Linux users don't care about Linux advantages but EXCLUSIVITY.

I would make a difference between two exclusivity types: the miser version of the Macuser, that don't want to spend a buck and uses things like GNOME+Compiz or KDE 4; and the megafriki like Richard Stallman that sees movies with a MPEG-->ASCII converter, edits his web page with a text mode emacs, sees some web pages throught wget, and do everything throught a console while is eating snacks.

The first group don't care about dislocating their hands rotating a 3D cube, nor that KDE 4.2 only do half of the things KDE 3 can do using more time. The cool things is to have windows that bounce up and down like a good tits. Perhaps that is the closest thing to sex they will have. This kinds of users like Ubuntu, Debian, Mandriva... it doesn't matter. After all, they're people without prejudges, that with faith (sometimes thanks to the bad advise that the second group (I will talk about them later) gave them) run from Windows to the freeware Linux.

The second group searches for intellectual exclusivity (as if configure X.org with nano were considered intellectual by someone with a healthy sexual life). They are the typical guys who give you shit because you use MS Office or OpenOffice instead of Latex, the guys who believe they're awesome because they have to type thousands of sequences like "/isearch:qqvv!!" just to edit a text on Vi, the guys who see pages on Lynx and treat you like shit because you use Flash, the guys who think that desktop enviroments are a conspiracy from multinationals companies to force all of us to buy high cost PCs, and the guys who think that, if you use Ubuntu, you're a lammer.

All of them used distributions like Corel, Mandrake, etc. several years ago, distributions that were easy to use (much more easy than Debian or Caldera) and could use lightweight enviroments like IceWM, XFCE, ENlightment... That was enough for them to feel more important than their stupid friends that used Windows, friends that used PCs to do disgraceful things like play videogames, edit rich texts, use scanners or printers, surf on internet with a 56k modem...

With the popularization of distros like Ubuntu, their friends started to switch to Linux, just like they told them before. In fact, they never thought anyone would pay attention to them, and that's why they never thought about the possibility that someday they will not be "superior" to other people because they work for their PCs while everyone else drinks beer or has sex,

Re:Linux users...

[dyingtolive]

because they work for their PCs while everyone else drinks beer or has sex, like a normal person.

Really? Cause the reason why I use Linux is because your girlfriend gets wet when I recompile my slackware kernel, and cause when I go out to bars and scrawl perl on napkins women get so tight around me I can hardly breathe and start buying me drinks.

Seriously though. I have a mac, and I have several linux boxes. I have a (gasp!) windows box for gaming/movies too! At my job I run Solaris and Linux servers both. Which stereotype do I fit into? Please, I need to know which condescending asshole to act like.

Re:Linux users...

[Ian Alexander]

Gimp gets the job done. iPhoto doesn't.

To be fair you're comparing apples to oranges. iPhoto is primarily a photo-management application; it's in the same category as Picasa or F-Spot, not GIMP. It does have photo-editing abilities but by their extremely-limited nature it should be obvious that that's not its primary intended use and that those are there for quick, simple touch-ups. It would be better to compare GIMP to Photoshop or Aperture, or iPhoto to Picasa or F-Spot.

Mac OS X can be better or worse than other Unices but first you need to get your comparisons right!

Re:Linux users...

[larry bagina]

Fun fact of the day: Mac OS X is certified Unix; Linux is not.

Umm

[hansraj]

This suggests a start: enable your open-source project to accept meaningful outside contributions that make the project reflective of a wider development community.

Isn't that already the case with most of the free software anyway? I mean not many people might be contributing to every project, but I don't think that is because the core team wouldn't accept outside contributions. In fact, what the hell does "outsider" mean in this context? I suppose anyone is usually free to start contributing to any project they like; usually it is hard to get accepted as part of the team but that is mostly because you can't expect to just get up one morning and figure out everything about an already existing project or convince everyone that what you want to add is in fact a desirable feature.

Seriously, with every Jack writing a piece of "analysis" these days, I am reminded of the saying: "Opinions are like assholes, everybody's got one".

Re:Umm

[Estanislao Mart�nez]

Isn't that already the case with most of the free software anyway? I mean not many people might be contributing to every project, but I don't think that is because the core team wouldn't accept outside contributions. In fact, what the hell does "outsider" mean in this context? I suppose anyone is usually free to start contributing to any project they like; usually it is hard to get accepted as part of the team but that is mostly because you can't expect to just get up one morning and figure out everything about an already existing project or convince everyone that what you want to add is in fact a desirable feature.

The major problem is in fact that people who control a project can be incredibly hostile to doing things that improve usability, and will just not compromise because they see no reason to do so.

A relevant example: Linus's uncompromisingly negative attitude toward Unicode normalization of filenames. OS X's HFS+ filesystem guarantees that all names are stored in normalized UTF-8; Linux's ext3 apparently just lets you use whatever you want. This means that in a Linux system, you could search for a file called Martínez.txt (note the accent on the "i"), search for a file whose name contains the subtstring Martínez, and not get a match because the filename and the search string are using two different representations of the accented "i". Or, from the user point of view, you get a search term that doesn't match itself.

At any rate, you do seem to agree that getting project owners to accept usability contributions is an obstacle. What I want to point out is that very often the obstacle is just not practically surmountable, period.

Nontechnical software user

[Anonymous Coward]

This is a universal. Most software is delivered to nontechnical software users.

Even the specialized mrp and accounting and I bet even the most technical/scientific of software are delivered to nontechnical software users.

Most development approaches begin and end at the source code control systems, by people who don't ever and probably wouldn't want to get near their customer.

Successful development projects do not simply arise from people having the "fun" experience of development. To be successful you will have to do the "not fun" things of supporting your endusers and documentation and attention to the supporting infrastructure that delivers your running software into running systems.

Easier said than done

[C_Kode]

Apple spends a lot of money implementing their design philosophies. Lets face it. It's not cheap to design user friendly high quality UI. Most companies that build open source products aren't serving the Desktop; they're serving the server market. The few that actually are (Ubuntu) are taking Linux and the open source desktop to a higher level.

I am very thankful for Mark Shuttleworth and what he is doing for the Linux Desktop. Everyone knows Redhat flip-flops on the Desktop subject all the time and never actually get much done for it.

Really?

[fluffernutter]

"Linux and open source have long struggled to gain acceptance from the wider (read, non-technical) audience"

Do they really? Consensus on Slashdot seems to be "If they can't figure it out, screw 'em".

What users want, not what they say they want

[dazedNconfuzed]

Apple is very good at figuring out what users actually DO with the products - and that includes figuring it out BEFORE the product is released. This in contrast with giving people what they _say_ they want, which rarely satisfies them.

Re:What users want, not what they say they want

[Late Adopter]

You think Free Software developers pander to what users say they want?! I can't think of any more group more intransigently opposed to doing anything other than scratching the itches that satisfy their particular use cases.

At least corporations have an obligation to pretend to care (for better and for worse).

Re:What users want, not what they say they want

[Bassman59]

You think Free Software developers pander to what users say they want?! I can't think of any more group more intransigently opposed to doing anything other than scratching the itches that satisfy their particular use cases.

This is truth, folks. I made a suggestion to the gEDA PCB developers, asking if they could implement a feature found in pretty much every commercial PCB layout package -- display the netname in every footprint pad. Seriously, this is a standard feature. And the tepid response from the developers? Something along the lines of, "Huh? I've never seen that ... and anyways, I can't imagine how that could be useful."

And, with that, I unsubscribed from the gEDA mailing lists, deleted all of the sources and dev builds from my machine, and went back to using the paid-for and perfectly functional schematic capture/PCB layout tool I had been using.

Re:What users want, not what they say they want

[babyrat]

Hmmm...as a recent convert from Linux to OS X, I have to comment here.

I like iPhoto. I like the app-centric database. I like the simplicity of time machine. I never noticed anything wrong with the red-eye tool. It is more than good enough for the casual photographer.

I never told anyone that I wanted this. I didn't even know I wanted it until I tried it.

As far as I am concerned, when I started needing to get stuff done, instead of 'messing around on the computer' is when the shift from Linux to OS X happened for my home computer use. At work I am still forced into using windows and still use Linux for the server functions.
 

Re:What users want, not what they say they want

[Beardo the Bearded]

I think his point was that if they hadn't used other programs to see:

a) what features they had, and
b) why they had those features at all

then their product would be theoretical at best, and not take into account several factors that would make it a useful and productive tool.

His attitude may be sub-optimal, but that doesn't mean that his point is invalid.

My experience with EMC2, an open-source milling program, has been expectional. The chat rooms are full of helpful people, we ran some experiments, and in the end, we found a way to configure a gamepad ($20) to work like a jog wheel ($1000).

My experience with Ubuntu at home has been complete shit. I still can't look at Youtube, Flash is troublesome at best, and apparently it's my fault for not buying a new machine every year. "Why would you have that card? It's ATI and it's, like, 4 years old. Get a new nVidia card and it'll work."

Re:What users want, not what they say they want

[gbarules2999]

As far as I am concerned, when I started needing to get stuff done, instead of 'messing around on the computer' is when the shift from Linux to OS X happened for my home computer use.

Really? I find Linux (or at least Ubuntu) is the opposite way. Set it up for a half an hour, and then everything works behind the scenes. Updates OS-wide, various configurations and whatnot, new programs, etc. It seems so hands-off to me. Maybe I'm just a weird Linux user.

More whining from fashion designers

[0xdeadbeef]

The more complicated a product gets, the more technical acumen is required to put it together. Bad Web sites are built by people who know how to code HTML and JavaScript but don't understand how people use the Web. Bad software is written by people who are experts at knowing how a computer works and how to write code to make it do what they want, but no idea about how regular people behave and how those people expect to interact with that software.

This is bullshit. Bad websites are built people who barely know how to use HTML and Javascript, but believe that the more HTML and Javascript you use, the better the website is. Slashdot, Digg, Gizmodo, Endgadget, Facebook, MySpace - they're all fucking horrible. People believe that because Google can pull it off, they can too. They believe that because they have very fast machines, everyone else does too. The believe that "moar interactive" == "awesome website", and that the more iframes you can pull into one page makes it a "mashup" and very "Web 2.0".

Do you see that kind of shit on the Apple website? Of course not! Apple doesn't succeed because of "design", they succeed because they have production values. They don't tolerate "good enough", they don't fixate on technology because it is new, they don't march to the beat of an ideological imperative. They believe in themselves, and they do what they want because they like it, on the assumption that their tastes are like everyone's tastes. Apple does not live by focus groups. Apple doesn't hold "design" over "technology", they hold "simple" over "complicated". The design wankers attach themselves to Apple's coattails because they can't differentiate between pretty technology and well executed technology. They don't understand technology, so they make a religion out of design so their priests can have something to lord over the unfashionable nerds.

Do you know why so much open source software sucks? It's because the programmers suck! They don't measure themselves against any standard of excellence. They stop when something works, ignoring the fact that it doesn't work well. It's plain old slob apathy. They're not getting paid for it, they can't be fired for failure, so what do they care?

Re:More whining from fashion designers

[edalytical]

No, he's right. Why hasn't Apple released a Netbook? They could have put there OS on a tiny underpowered device with a 800x600 screen and called it a Netbook. But they didn't. Why do you think that is? Maybe they're not fixating on new technology. Maybe they don't "ideologically" repackage products to fit every new product category like other companies do. I mean, people wanted an iPhone for years before Apple release it and it turned the market upside down. If they just put an iPod on a phone or a phone on an iPod nobody would have cared except for a few fanboys. Instead they made a truly innovative device and entered the market when the time was right -- when they had something interesting. The same thing will likely happen with the Apple Netbook. They'll enter the market for sure, but not just for the sake of entering the market. They'll have something to offer, something that will take two years for the market to catchup with.

Re:More whining from fashion designers

[edalytical]

You're not only confused, you're miss informed. The iPhone was specifically designed to be a smart phone. Not only that it was the iPod touch that followed the iPhone.

Furthermore, they got the phone right the first time. I own a first generation iPhone and am completely happy with it. I'm not even compelled to upgrade (AT&T is a different story). The industry has barely started to catchup (there might be something to the Pre, etc).

Sure the eMate was a flop, but you're talking about historic Apple Computer, not Apple Inc. proper. I don't think they've flopped since the eMate (their netbook as you say). Certainly nothing has flopped after the release of the original iMac.

And you really shouldn't reference belligerent bloggers when you are attempting to make a point. That guy is as laughable as he is loony.

It's about marketing

[enrevanche]

What keeps Apple and Microsoft on top is marketing and momentum. We live in a society driven by mass media. For the most part open-source does not have a sufficient marketing budget. Most people do not even know about alternatives.

Re:It's about marketing

[gbarules2999]

Most people do not even know about alternatives.

Even if they did, installing and configuring an OS is much, much more complex than what a lot of computer users can (and should) handle.

Downside?

[willoughby]

"The downside is that these contributors are techies..."

That's like saying the drawback to commercial aircraft is that they are designed by aeronautical engineers.

Re:Downside?

[Estanislao Mart�nez]

That's like saying the drawback to commercial aircraft is that they are designed by aeronautical engineers.

But that has in fact often been a problem. There are many aircraft accidents where bad human factors design played a major role. For just one example, check out this Bruce Tognazzini article.

Re:Downside?

[Anonymous Coward]

I don't fly based on the make of the plane. I fly based on the customer service the airline offers.

Re:Downside?

[nine-times]

Well, if you're running a commercial airline and you allow the aeronautical engineers to design the interior of the aircraft (including seats, lighting, fixtures) without including anyone with interior design experience, then yes, that might be a problem. If you allow the aeronautical engineers to design the menu for the inflight meals without consulting any kind of chef or caterer, then that might be a problem too.

I Can Tell You This About Users

[RobotRunAmok]

They're not impressed nor amused by app names like gtkWTF, IAMRECURSIVERECURSIVEIAM, and, especially, The GIMP. Also, stop talking about programs being "stable." Isotopes are "stable." Programs either run well, or are buggy.

People mock Microsoft, but I tell ya... I've worked with people who have no idea what Silverlight is or does, but they want it cuz it sounds cool and has something to do with the Web. It's almost as if Linux developers go out of their way to be non-MS in everything -- including creating marketable names for their wares.

The problem, of course, is that the same guys doing the codewriting are the same guys doing the naming and marketing ("...because, after all, I've written the code, and that's the tough part that really matters, right? And if people don't get the Linus/Stallman/Montypython joke upon which I've based the app's name, then fuck 'em, who needs 'em, I'm only doing it for love anyway...").

Why isn't there any open-source marketing? Maybe some of the bigger projects could reach out to some university business and marketing students who could take on the work in much the same way they attract coders?

Re:I Can Tell You This About Users

[bigredradio]

I think you are right. Get marketing students or business students involved. Same goes for graphics designers and webmasters. Get the people who are experts to perform the right tasks.

Re:I Can Tell You This About Users

[RobotRunAmok]

I agree with you that a lot of projects could use better or more descriptive names, but you've gotta realize that 99% of the time these are people's personal projects that they are either working on because it has some utility to them or because they just want to get experience.

That's fine, and God Bless. Keeps 'em off the streets, and all that.

But every time someone criticizes Linux for not having an app that does what such-and-such closed source app does, the response is invariably, "Whaddya mean? KgnuSMEGMA is out of pre-Alpha and does EVERYTHING that program does, and once Joey gets home from camp he's going to be spending the rest of the summer building a killer GUI for all the lusers who don't like the CLI."

Personal project? Or alternative to proprietary commercial? You may choose one.

Re:I Can Tell You This About Users

[Stormwatch]

(posting again because somehow my other post turned out all fucked up)

> If we live in a world where a good image manipulating application is overlooked
> because its name is GIMP, there is something wrong with the world.

No, actually it is overlooked because people balk at the terrible interface and go back to Photoshop.

Re:I Can Tell You This About Users

[schnell]

Fuck marketing! Just give people the free and open truth.

Let me guess ... you're an engineer?

Seriously, I think the problem here is you are confusing marketing with spin. Marketing actually encompasses a LOT of useful things, not just spin - and most F/OSS projects could REALLY use them. The definition of marketing includes:

• Competitive analysis (what do competing products do? are we ahead or behind?)
• Market research (how many people use this/want this/care about this? do they want something different?)
• Product management (what do our customers want us to build? what can we really build?)
• Reporting and analysis (how are we doing? what can we learn from the buying behavior of our customers?)
• Public relations and press/analyst relations (how can we get correct info to reporters, bloggers, analysts and get them to write about it?)
• Branding, advertising and customer communications (how can we tell customers about this and make it sound appealing?)

It's a common mistake among technical people to think that marketing only includes that last item. Just like many sales or marketing people misunderstand what "technical people" do...

Focus on what the user wants

[Thaelon]

Spend time on the UI.

Make sure that your software is the user's bitch, not the other way around.

To elaborate, here are some tips:

• Use zero modal dialogs. They force the user to act at the software's behest to continue doing what they want. Making the user your software's bitch.
• Make any reasonable action from one state as convenient as possible from that state to the most likely states.
• Observe how your users use your software and modify it to make everything the do in it as easy and as fast as possible.
• Just because it has a lot of functionality doesn't mean shit if it's too hard for them to figure out how to use it. Make it as intuitive, as logical, and as predictable as you can.

Re:Focus on what the user wants

[FishWithAHammer]

# Use zero modal dialogs. They force the user to act at the software's behest to continue doing what they want. Making the user your software's bitch.
Making

A modal dialog often has value, in that it focuses the user's attention on something that, generally, is necessary to actually do what the user wants. Take Visual Studio for example. If I click "run," and a file has changed since the last build, it'll ask me whether I want to build again before I run the application. You could assume they want to build again, but for some people that may not be what they want, so it asks. Of course, for many workflow options, this only needs to be exposed to the user once. Visual Studio asks me whether I want to build before running, but there's a checkbox that tells it not to ask me again. I check it, click "Yes," and it never bothers me again--but now it acts the way I want it to, every time.

There are many uses of modal dialog boxes that everyone gets wrong, however. No, I don't want to send user statistics ANYWHERE, and you should not be popping up a modal dialog and keeping me from doing what I want in your vain attempt to get me to do so.

Your other points, however, are right on the money. Great post.

That a single cohesive vision...

[rAiNsT0rm]

is actually better than a chaotic/bazaar mess that spins it wheels for 15 years? No shit!? Man, I mean while everyone blabs on and on about the bazaar and how great the chaotic development is, it isn't good enough for that central part: The Kernel. So why in the hell we keep fighting a cohesive and directed effort to build at least a baseline for the entire OS is beyond me.

This is why I gave up on Linux for all but my servers. One day it will happen, or Google/Ubuntu will do it first. At this point I don't even care, just that it happens.

One word

[PhotoGuy]

Polish.

Re:One word

[TheGothicGuardian]

It's a nice language and all, but I didn't know Jobs spoke it.

Apple is the bipolar opposite of open source

[goffster]

Apple is one man's dream, and it will die with that man.
Open Source will outlive any particular person.

Re:Rebuttal quote

[edittard]

I'm not saying you're wrong, but a much more likely response will be:

• None.
• Works for me.
• That's a feature not a bug.
• If you're so smart, fixit yourself and submit a patch.
  (so you submit a patch)...
  • your patch is teh sux0rz - rejected.

Further

[PeanutButterBreath]

1 out of 1(0) users know what they want and can express it.

5 out of 10 times they want something that can't be done.
4 out of 10 times they want something that can be done but shouldn't.
1 out of 10 times they want something both worthwhile and achievable.

I call BS

[tlambert]

I call BS.

bash is UNIX2003 standards compliant because of Apple contributions back to bash.
vim is UNIX2003 standards compliant because of Apple contributions back to vim.

I could repeat sentences of this format for about 80 different Open Source versions of UNIX command line commands.

Apple just doesn't make a press release every time it contributes a patch back to an Open Source project.

-- Terry

The Truth About Commercial vs. Open Source

[tlambert]

The Truth About Commercial vs. Open Source ...is that in a commercial setting, there is dictatorial editorial control, and people are willing to work on things they wouldn't ordinarily work on for the joy of it, in trade for money.

Without that, there's no way to prioritize customer input ahead of developer desires, and there's no way to get a developer to work on something that they disagree with.

The closest the Open Source community has come to this are companies like Mozilla, RedHat, and Ubuntu, which are large participants in particular Open Source projects, but which internally exercise a single editorial philosophy over the product, and have paid engineers to work on the things that no one would work on at all, if it weren't for the money.

I have absolutely no idea (and I expect no one else does, either) how you would cause a bug report to be responded to in a timely fashion and get it resolved to the satisfaction of the person who filed it, in an Open Source project, unless the person who filed it wrote the fix, and the fix was acceptable to the some pigs who were more equal than others in the project. Most large changes to Open Source projects are arbitrated by a board of people who are self-selecting, who are there because of seniority, or nepotism, or as a result of a popularity contest. From such groups, you're going to get consensus. Anything that goes against that is going to get strong resistance, even if the consensus is basically what Frank Herbert called a "demopoll", which means you will always end up with the lowest common denominator.

Great products (and terrible ones) require an 800 pound gorilla to force its views on the participants, and for those participants to be willing to stick around despite the force.

-- Terry

Enlightenment .17

[Weedhopper]

e17.

If there was ever an example of a "closed" open source project...

e16 was damn cool window manager. And then e17 happened.

iPhoto is great for what it is

[Estanislao Mart�nez]

Some of us care about the little details. The fact that it comes under the heading of "casual photography" doesn't mean that you necessarily want to be sloppy with it. The end results with any luck will last as long as conventional print photography has. There's no reason to do anything besides "do it right" if you are the owner of the prevailing platform for "professional artists".

Two points:

1. Apple makes Aperture, which is a really good application for advanced amateur and professional photographers. The controls provided make it really easy to make a lot of very sophisticated photo adjustments really fast, compared to, say, Photoshop. (I haven't used Lightroom, though.) Those controls still do require a pretty advanced understanding of digital imaging.
2. iPhoto is still a really good application for people who primarily shoot compact digital cameras, and use the jpegs straight out of the camera. The big feature there is photo cataloguing. The adjustment tools are pretty basic and not good for detailed work (e.g., no white balance dropper; the histogram only has sliders for black and white point). However, the intended user audience for the application is not at all capable of doing such work.

Is that you Michael Dell?

[andersh]

Is that you Michael Dell?

Open source doesn't need any lessons

[gig]

Apple is an open source success story. OS X and WebKit are massive open source successes. The iPod is as good an Internet citizen as BSD Unix. The Mac is the easiest to use computer yet gets no viruses. The Web was created on an early OS X and ported easily to open source Unix as a result.

The people who should be learning from Apple are not open source coders who work on the many successful projects. Open source is at least 1 step further into behind-the-scenes than the consumer. It's HP, Dell, Sony, possibly Google and Microsoft, and maybe other manufacturers of consumer technology like car makers who should be studying Apple very closely. Not only to notice Apple's design chops, but also to notice their very successful engineering, including open source efforts.

You only have to say "What Microsoft can Learn from Apple" and contemplate how much better Windows XP would have been if the core OS was BSD-compatible. No viruses. No botnets. All of the engineering efforts that went into the failed Windows 2004 could have been used more productively in the user-facing features. All of the engineering efforts to redo that for Vista could have been used more productively. The typical Windows user installs more patches than apps, and the patches are for stuff they never see or use. Microsoft could be platform-independent through open source, so they could choose to run Windows on ARM right now, which they are not at all prepared for. If they had done their browser engine a la Gecko and WebKit, then they wouldn't have 4 wholly incompatible engines running in great numbers on the Web right now, which they analogized to puke in a recent ad and they were the last ones to admit it. Apple has none of these problems. Apple runs the same kernel on iPod, iPhone, Mac, and XServe and no crashes or viruses anywhere.

On the other hand, with Palm, in the Pre you have a Linux kernel and WebKit browser engine replacing Windows Mobile and IE Mobile from the Treo. Because of Apple. That is Palm learning from Apple about open source.

So it's Apple's competition that needs to learn both from Apple and from open source. Apple and open source are both very successful.