I'm curious to know how other developers go about creating the basic user interface/design for a new project.

I have put a lot of time and effort into creating what I consider to be an ideal user interface/design with custom graphics, etc. I was planning on re-using this design for future clients. However, my current client is concerned about their database not looking like others.

I realize, that in the end it's the clients decision and I'll give them whatever it is they want, but I'd like to hear if other developers use a "canned" user interface/design, or if you re-design, create new graphics, new color schemes, etc.

(by user interface/design, I am referring to the navigation method, basic structure of layouts, color scheme, custom graphics for tabs, borders, buttons, etc.)

Hi there,

The solutions within filemaker should give you a good idea how a database looks like, or at least should. If you are stuck, go over to scriptology.com, they have a theme library.You can download a demo.

I design my database first on paper, draw all the elements and then when I am happy with it, then I get to work.

Perhaps include a screen-shot of your work, that way other members could give more helping points

Edited October 15, 200916 yr by Guest

Thanks for the input Matt. However, I don't think I was very clear about what I was asking...

I'd like to know if other developers re-use layout designs for many projects/customers.

More specifically, as I put it in my original post:

"I'd like to hear if other developers use a "canned" user interface/design, or if you re-design, create new graphics, new color schemes, etc."

It's a little beside the point, but perhaps a few screen shots will help...

I use a custom menu item for navigation, and a multi-window solution.

If this user interface/design was to be used for another project, all that would be different would be the window name, page title, column names, etc. The overall look and feel of the database would be very similar though - which is what my customer was concerned about.

I use a custom menu item for navigation, and a multi-window solution.

If this user interface/design was to be used for another project, all that would be different would be the window name, page title, column names, etc. The overall look and feel of the database would be very similar though - which is what my customer was concerned about.

You can read this two ways.

The customer wants a uniform look for his databases?

The customer doesn't want you to use the same look in another Client's interface.

Lee

yikes! you can read that both ways. I meant the 2nd one.

"The customer doesn't want you to use the same look in another Client's interface."

How does your contract read on ownership?

I can use the current user interface/design without legal constraint.

The solution I am building for this new client will be owned entirely by the client.

Although, what I'm really looking for is to hear if other developers re-use user interface/designs.

Was this your first job?

I show clients some "templates" of design and let them pick one. If they want something radically different it's more money, but usually I don't explicitly offer them that option. It's more "these designs have proven to be functional and usable, which do you prefer."

In the end, the interface "design" is unique to their database because no other solution will have exactly the same fields, windows, etc. If however by "design" they mean decorative elements like background colour or tab shape or buttons... well that's not really open for negotiation, of course they cannot have it exclusively.

Get the client to think in terms of functionality and usability.

Also get them used to the idea that their solution uses techniques that you have used in previous projects, and techniques used in their project will be used in others in the future.

Thanks Vaughan, that's exactly what I was hoping to hear, and how I was planning to work.

The current project I'm working on is my first job as an independent consultant. The previous project, which I provided screen shots of, was something I built as an in-house developer for a company that is no longer in business, and I was given permission from the owner of the business to use the database.

I don't understand why a client would be concerned if their database looked similar to a competitors. They probably use the same web browser, e-mail client, word processing program, etc.