Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

We had an interesting but "un-resolved" discussion recently within the team regarding header design (logo + navigation links etc) for a web application. I would like to know if having a dark or visually separate header (Eg: emc.com, imdb.com) help the user get confortable with the website easily when compared with headers which seem to merge with the content area (eg: amazon.com, mint.com).

share|improve this question
add comment

3 Answers

In my point of view the header should stand out in contrast of the content. Keeping the header clear and simple makes it much easier to find out who the site belongs to and what you can do there. If you compare Usability First to Amazon website - I find Usability First easier to navigate. Amazon takes much longer to understand and luckely they have a huge search area in the top center which I always use. I wouldn't dare trying to navigate to what I wanted on Amazon. But that's me, others might find the navigaton better.

Usability First says this on Information Architecture:

A “bricks and mortar” architect must balance the (often competing) demands of aesthetics, structural integrity, heating, lighting, water supply and drainage when creating building blueprints. Similarly, an information architect must create navigation schemes for software that are at once concise, descriptive, mutually-exclusive, and possessive of information scent. Both types of architect seek to create spaces for humans that are safe, predictable, enjoyable, and inspiring.

Consider this:

Header


is much more clear than the following

Header

The header is supposed to divide content - and throwing in a horizontal rule below a bigger font makes it easier to read - doesn't it?!

share|improve this answer
    
I always felt uncomfortable with Amazon's header, and many other similar content dense sites. Thanks –  amarnath01 Apr 19 '11 at 4:24
add comment

The question can't be reduced to a visually distinct header.

The rule of thumb for navigation controls is the same controls in the same place throughout the site.

A visually distinct navigation menu helps the user recognize the controls, and tell apart content from navigation.

Whether it should be distinct is usually determined by esthetics more than functionality. Functionality-wise, I would recommend to:

use a distinct navigation header if content is colorful, rich, or in another way looks very distinct on different pages.

avoid a distinct navigation header if there is no clear separation between navigation and content.

None of these explains the difference between the samples oyu provided, though in those cases I personally do feel more comfortable with the distinct navigation header.

share|improve this answer
add comment

All users are different - so you might find some that like or get comfortable with one type of header and some gravitate towards another. So if you are really wanting an answer via the users opinion maybe try some user test cases and drive test users to some different headers and ask their opinions and get feedback from the true source. As I said, it depends on the user - I know some people who hate colorful patches on websites because it distracts them and I know others who love them (like me) as it can drive the users eye to what you are trying to do for them.

share|improve this answer
    
I do agree users are different, which is what makes understanding UI impact so interesting. –  amarnath01 Apr 22 '11 at 6:44
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.