Breadcrumbs would be redundant for some of my pages and quite pointless, but effective on others which are a bit deeper.
Is it bad practice to only implement breadcrumbs on some of the pages?
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.Sign up to join this community
2007 article from NN/g Breadcrumb Navigation Increasingly Useful
Summary: One line of text shows a page's location in the site hierarchy. User testing shows many benefits and no downsides to breadcrumbs for secondary navigation.
Consistency is a key principle for UX design. If you implement breadcrumb for some pages and not for others, you are breaking your own site's consistency.
This consistency means that people know a breadcrumb trail when they see one, and immediately know how to use it. Consistency breeds familiarity and predictability, which breed usability. This again means that you must comply with conventions in the design of your own breadcrumbs.
Verdict: No, it is not okay to implement half of a breadcrumb navigation
No, you should try and use the same navigation controls throughout. Besides the obvious advantages for learnability, shifting navigation mechanisms within a site runs the risk of implying that users are moving between different ecosystems.
If only a small number of pages would benefit from breadcrumbs, however - perhaps because your site structure is rather flat - you could consider other navigational aids for those pages. Wizards with step links, progressive disclosure and tiling effects (if you're on mobile) are all patterns you could use to help users negotiate these trickier pages without forcing redundant measures on other pages.
No, breadcrumbs are about providing users with a sense of place and how they got there, plus the means to easily go back and try a new path. So, consistency, sense of place, context are vital.
Simpler architectures, mobile, and flat structures don't need them. If it's a specific task completion flow with a lot of options, you could use a guided process using a train. However, for navigating, searching, or giving users a sense of where they are in an information hierarchy they're great.
If they're not implemented consistently, the user might even think it's a design feature failing...:)
No, this is the perfect example of a bad ux i.e. - Having a navigation bar in blue on the homepage but red on the internal pages is not acceptable.
Consistency is always good. I can see an argument for having certain types of breadcrumbs in the form of progress bars for instance (Ie - to show progress).
If your site/app has a good, clean url/directory setup then you'll have no need for breadcrumbs. (ie - www.site.com/shop/mens/ is better than just www.site.com/mens/ )