Re: Role of IxD in Open Source [was: good interfaceexamples for web basedapplications]

9 Mar 2004 - 9:17am
10 years ago
1 reply
553 reads
Dave Malouf
2005

Hi Todd,

Open Source (I get really confused when you used OS b/c that means operating
system to me) is a mystery to me.

I mean how do we as IxD just go out and create a design on top of an open
source project? How do we do that w/o also having connection to the kernal
of the application we want to effect? How do our processes for research and
analysis fit into the process of an always moving target of many if not all
of the open source movement?

When I think about throwing my hat in the ring these are the areas that keep
me from jumping in. Not money or time so much as how.

I would say there is the business model that feels really strange to me. I
could see making money but selling consulting and customizations of existing
systems, but contributing to the IxD of a system and giving that away? Now
what? Once its out there there is nothing left to consult for and make money
on. Now if you want to specialize as a consultant with experience in
manipulating the design of an open source project that sounds interesting,
no? Lindow's business model (whichis not exactly a huge success) is to sell
their design as a package; so basically their design is not open but it is
built on an open platform.

I'd be interested in hearing about anyone on this list who has worked in one
of the open source projects.

-- dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.interactiondesigners.com/private.cgi/discuss-interactiondesigners.com/attachments/20040309/34f46eea/attachment.html

Comments

9 Mar 2004 - 10:45am
Dave Malouf
2005

Alain said:
"Open source is all about the code. All about software developers
interacting with the code. Not about users interacting with an
application."

Is that true? I know that Jeff Raskin has an open source project of his own
going on.
I do think you are right historically, but isn't open source about proving
that software can be open and profitable at the same time? That open
software actually produces better software? Is better software ONLY about
performance and defects? Isn't better software also mean more usable,
engaging, practical, useful, etc.?

Are you suggesting that we aren't invited to the table?

-- dave

Syndicate content Get the feed