Content needs to be separated into sections and accessed using a flat navigation structure that gives a clear indication of current location.
The Navigation tabs pattern is an extension of the desktop metaphor in which physical objects are represented as GUI elements. Navigation tabs are derived from the idea of folders in a file-cabinet and are thus familiar to the end user
Navigation tabs provide a clear visual indication of what content can be found on a website and places the current location in context by highlighting it.
Actually Jacob said:
“…use tabs to alternate between views within the same context (not to navigate to different areas).”
The main issue is not to use it as primary navigation, but its use in switching between similar sets of contextual information is valid.
So the example is out of data and perhaps the pattern could be updated?
@Stephen Holmes – I agree with update needed
I think the Amazon example (according to Jacob’s definition) is still semi valid because the tabs are flipping between sets of products. Though I think the blue bar (below the tabs) sort of breaks it. Though you could argue that the tabs are flipping between website objects so it could still be valid. Or if you treat Amazon as an app, you are simply flipping between views of the database based on department.
I think the main reason for Amazon abandoning tabs is that they now do so much more than just sell physical products.
What does everyone else think?