For a responsive website where - at a set break-point - the primary navigation contracts to as single menu item that opens and closes the navigation menu (See the Starbucks.com site for an example) is it preferable to:

  • a) Show the primary navigation option fully-expanded when first hitting the homepage. (Closed by default on all other pages)
  • b) Show the menu contracted until the user selects it?

See this dummy-website example below.


download bmml source – Wireframes created with Balsamiq Mockups

My preference is B - As a rule Content is more important than Navigation, so provided the nav option itself is clear then there's no need to display the expanded menu unless the user selects it, however our client is arguing the case for A because they want to drive people into the site and feel displaying the menu would achieve this. Is it wrong to initially show the menu expanded on the homepage.

  • I think it's more of a personal aesthetic preference + user testing.
    – dnbrv
    Commented Apr 4, 2012 at 15:59

1 Answer 1


I think an in-between approach is also a good option. (my preferred)

In other words, still show a few core navigation links, but also give user option to see the full list.


download bmml source – Wireframes created with Balsamiq Mockups

Bloomberg's web site viewed from smartphone kind of does this, but since they have extremely complicated menu, clicking on the "menu" actually takes you to a new page, which I'm not too crazy about.

  • Jung - i've added a link to the bloomberg mobile site to your answer (I assume this is what you were referring to?) Yes, the option to still display some items in the menu is an interesting idea that was also discussed, but that would be the case on all pages not just the homepage.
    – JonW
    Commented Apr 4, 2012 at 13:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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