Design and Development Process

Moore, Kathleen E kemoore at
Fri Sep 21 22:07:21 UTC 2007


This is excellent! The design group in Sakai has tried to come up with
similar lists, but I like the process of letting a developer decide how
best to express these points for other developers -- in collaboration
with designers.

Thank you!

Kathleen Moore
Web Manager, Information Technology Services
BU School of Management
kemoore at

-----Original Message-----
From: fluid-work-bounces at
[mailto:fluid-work-bounces at] On Behalf Of
michelle.dsouza at
Sent: Friday, September 21, 2007 4:56 PM
To: fluid-work at
Subject: Design and Development Process

Hi everyone,

In preparation for the summit, I've been thinking about how we as the  
Fluid community can better integrate designers and developers. My  
original thoughts, based on what we've done so far in Fluid led me to  
create this page on design and development process for Fluid.

It didn't take very long for me to realize that although this process  
would result in a great user experience, it wasn't very practical. At  
this point in the Fluid project we have the luxury of lots of design  
resources but of course this is not the reality for our projects where  
designers are difficult to come by. As a developer, I've always found  
this to be a difficult position to be in. I want to create better UIs  
but have never been very clear on what constitutes 'better'. I don't  
have a lot of time to spend on UI so I'd like to spend that time well.  
To this end, I've done some research and put together a *short* list  
of design tips for developers. I've kept the list to 5 points because  
I know that I'm not likely to have the time for more then that.

This is a work in progress and I welcome your feedback and  
suggestions. This may make for an interesting conversation at one of  
the joint sessions at the summit.


fluid-work mailing list
fluid-work at

More information about the fluid-work mailing list