8 Web Design Mistakes That Developers (Non-Designers) Make
wakeuplater.com
wakeuplater.com
The points about free fonts and stock photography. Using system standard free fonts is good for several reasons including initial cost. The main reason I favor system standard fonts is being able to render headers and menus in text versus having to load up and image which is wasted bandwidth for most cases. Stock photography purchases are also tough to swallow for a developer but in a proper setting the developer for the site shouldn't worry about the cost of things because he isn't footing the bill! If it is a developers personal project, understand that he is a do-it-yourself kinda person and will want everything for inexpensive or free.
Sorry this article got me worked up a bit. I felt I fell into the developer (non-designer) category but I don't know anyone so full of themselves to make many of those mistakes. Can't we all just get along? ;)
I also think its very helpful if developers learn at least basics of good design in case they have to make some minor changes.
Check it out here: http://www.cocunderground.com/fpt.jpg
As far as what's wrong with it, I'm sure you can figure that out. It's still a lot better than what they have currently: freepromotips.com.
That being said, I think it is much easier for a coder to pick up on what is important for designers than vice versa.
Design is just like code, there is a version 1.0 that works, but isn't great and still needs some features. So you iterate on the code based on feedback and your own ideas. Design is the same, and if you include usability I think it is more important to iterate on your design than your code.
I did a consulting gig for a semi-large online retailer where we changed the design, the flow of the site, etc. Primarily design changes. And their turnover rose by 30% because of it.
That's how important design is.
(You bring the beer.)"
Taken from Advanced Common Sense (http://www.sensible.com/) I really recommend the book.
Mmmmm... beer...
It's a recently launched web application. The layout is just one huge <table>. There is no design to speak of. Probably because none is needed.
First, it doesn't matter whether the page is made with tables, divs, or strawberry marmelade - the user will never know.
Second, don't think that just because something looks like it wasn't designed that it isn't. A large part of googles success lies in its simple design, bordering on the naive. Don't think that this isn't intentional and that a lot of hours haven't gone into designing it.
And if you don't know these general ideas, why not just hire someone? Learning design takes a LOT of time, more time than most math/science/computer oriented coders are willing to spend simply on artsy design.
"I Know What Looks Good (and I Have Photoshop)"
"Just Use Blue and White Again"
"I'll Just Center Everything"
"Use the Free Font...It Looks Fine to Me"
"We Can Fit More Information in That Space"
"I'm Not Paying for a Picture"
"I Don't Need to Ask for Opinions"
"No Need to Get Too Detailed"
If the article's writer thinks those are the _best_ designs out there, then I suspect the opinions are somewhat limited.
Screw that, this is the best rule ever! Really, why not? I have no designer ego to feed.
UI designer != graphic designer
And yes, I really oughta do something about it.
One of these days.