Back to compare picker

Global navigation vs Breadcrumbs vs Bottom navigation

Use global navigation for persistent movement across top-level product or service sections, breadcrumbs for hierarchy orientation, and bottom navigation for a small set of mobile primary destinations.

Learn the decision

Match the interaction to the person's task

Use global navigation for persistent movement across top-level product or service sections, breadcrumbs for hierarchy orientation, and bottom navigation for a small set of mobile primary destinations.

Global navigation

Use it when: Users revisit several top-level product or service areas.

Make this state clear: Default state with product or service identity and top-level links.

Observe the result: Users switch from Projects to Reports, return to Projects, and find their project draft count preserved.

Study the full pattern →

Breadcrumbs

Use it when: Pages sit inside a clear parent-child hierarchy.

Make this state clear: Interior page with full ancestor trail.

Observe the result: Opening a saved deep link still shows the same parent path and lets users jump to Migration or Projects.

Study the full pattern →

Bottom navigation

Use it when: A compact mobile app has three to five high-frequency top-level destinations.

Make this state clear: Default state with all primary destinations visible.

Observe the result: Switching from Home to Saved and back preserves each section's scroll count and draft state.

Study the full pattern →

Practice the judgment: Imagine this situation: Global nav lists every page and becomes impossible to scan. Write the person's goal, choose one of these patterns, and show the state that helps the person continue. Use the decision rules and source trail below to explain your choice.

Review the underlying principle →

Decision dimensions

Dimension Global navigationBreadcrumbsBottom navigation
UI or UX UI + UX - Persistent top-level navigation shellUI + UX - Hierarchy orientation navigationUI + UX - Persistent mobile primary navigation
UI guidance Render product or service identity, a compact set of top-level destination links, current-section state, separate utility controls, and responsive overflow behavior.Render a labeled breadcrumb nav as an ordered hierarchy from the broadest relevant ancestor to the current page, with real ancestor links and a distinct current-page item.Render three to five bottom destinations with stable touch targets, labels or accessible names, reinforcing icons, selected state, optional badges, and safe-area spacing.
UX guidance Help users move between major product or service areas while preserving orientation, local state, and confidence that they are in the right service.Orient users who arrive deep in a site by exposing the canonical parent-child relationship for the current page.Support rapid switching between top-level mobile sections while preserving each section's local navigation, scroll, filters, and drafts.
Good UI A header shows the product name, Dashboard, Projects, Reports, Billing, a More overflow, and separate Help and account controls.Home, Projects, Migration, and Runbook appear in hierarchy order with ancestor links and Runbook marked current.Selected state uses shape, weight, and text color instead of relying on color alone.
Bad UI A crowded row mixes every page, account action, language selector, and sign-out link.Recent clicks are displayed as if they were the page hierarchy.Six tiny icon-only items and a center plus button compete for space.
Good UX Users switch from Projects to Reports, return to Projects, and find their project draft count preserved.Opening a saved deep link still shows the same parent path and lets users jump to Migration or Projects.Switching from Home to Saved and back preserves each section's scroll count and draft state.
Bad UX Navigation opens external or utility destinations as if they were service sections.The breadcrumb changes after every click, so the same page shows different trails for different users.Tapping Search clears the Home feed position and opens a one-off command instead of a destination.
Best fit Users revisit several top-level product or service areas.Pages sit inside a clear parent-child hierarchy.A compact mobile app has three to five high-frequency top-level destinations.
Avoid when The flow has a single ordered transaction where navigation would distract or cause abandonment.The flow is linear task progress rather than site hierarchy.There are fewer than three or more than five primary destinations.
Required state Default state with product or service identity and top-level links.Interior page with full ancestor trail.Default state with all primary destinations visible.
Accessibility burden Use a labeled navigation landmark for primary navigation.Place the trail in a labeled nav element.Every icon must have a visible label or accessible name.
Common misuse Listing every page or admin object in the global nav.Showing browsing history instead of hierarchy.Putting too many destinations into the bar.

Global navigation

UI or UX
UI + UX - Persistent top-level navigation shell
UI guidance
Render product or service identity, a compact set of top-level destination links, current-section state, separate utility controls, and responsive overflow behavior.
UX guidance
Help users move between major product or service areas while preserving orientation, local state, and confidence that they are in the right service.
Good UI
A header shows the product name, Dashboard, Projects, Reports, Billing, a More overflow, and separate Help and account controls.
Bad UI
A crowded row mixes every page, account action, language selector, and sign-out link.
Good UX
Users switch from Projects to Reports, return to Projects, and find their project draft count preserved.
Bad UX
Navigation opens external or utility destinations as if they were service sections.
Best fit
Users revisit several top-level product or service areas.
Avoid when
The flow has a single ordered transaction where navigation would distract or cause abandonment.
Required state
Default state with product or service identity and top-level links.
Accessibility burden
Use a labeled navigation landmark for primary navigation.
Common misuse
Listing every page or admin object in the global nav.

Breadcrumbs

UI or UX
UI + UX - Hierarchy orientation navigation
UI guidance
Render a labeled breadcrumb nav as an ordered hierarchy from the broadest relevant ancestor to the current page, with real ancestor links and a distinct current-page item.
UX guidance
Orient users who arrive deep in a site by exposing the canonical parent-child relationship for the current page.
Good UI
Home, Projects, Migration, and Runbook appear in hierarchy order with ancestor links and Runbook marked current.
Bad UI
Recent clicks are displayed as if they were the page hierarchy.
Good UX
Opening a saved deep link still shows the same parent path and lets users jump to Migration or Projects.
Bad UX
The breadcrumb changes after every click, so the same page shows different trails for different users.
Best fit
Pages sit inside a clear parent-child hierarchy.
Avoid when
The flow is linear task progress rather than site hierarchy.
Required state
Interior page with full ancestor trail.
Accessibility burden
Place the trail in a labeled nav element.
Common misuse
Showing browsing history instead of hierarchy.

Bottom navigation

UI or UX
UI + UX - Persistent mobile primary navigation
UI guidance
Render three to five bottom destinations with stable touch targets, labels or accessible names, reinforcing icons, selected state, optional badges, and safe-area spacing.
UX guidance
Support rapid switching between top-level mobile sections while preserving each section's local navigation, scroll, filters, and drafts.
Good UI
Selected state uses shape, weight, and text color instead of relying on color alone.
Bad UI
Six tiny icon-only items and a center plus button compete for space.
Good UX
Switching from Home to Saved and back preserves each section's scroll count and draft state.
Bad UX
Tapping Search clears the Home feed position and opens a one-off command instead of a destination.
Best fit
A compact mobile app has three to five high-frequency top-level destinations.
Avoid when
There are fewer than three or more than five primary destinations.
Required state
Default state with all primary destinations visible.
Accessibility burden
Every icon must have a visible label or accessible name.
Common misuse
Putting too many destinations into the bar.
Decision rules
  • Prefer global navigation when users need repeated access to several top-level sections across a non-linear product, service, or site.
  • Prefer breadcrumbs when the user is deep in a hierarchy and needs orientation plus a path to ancestor pages; breadcrumbs do not replace top-level navigation.
  • Prefer bottom navigation when a mobile app has three to five high-priority destinations that need persistent thumb-reachable access.
  • Do not use global navigation as a complete site map; keep links to the most useful top-level areas and push deep or local destinations into side navigation, page links, search, or command palette.
  • Do not use breadcrumbs as global navigation; they represent the current page's hierarchy, not peer destinations.
  • Do not show both a dense global nav row and bottom navigation on the same narrow viewport unless one is clearly secondary or transformed responsively.
  • Separate utility controls such as account, help, search, language, switcher, and sign out from top-level destination links.
  • If switching global sections would lose filters, drafts, or scroll position, preserve state, restore state, or warn before leaving.
  • Use task list or step navigation instead of global navigation when users must complete a single ordered journey.
Inspect live examples
Failure modes
  • Global nav lists every page and becomes impossible to scan.
  • Current navigation state does not match the page content.
  • Account and sign-out controls are presented as peer product destinations.
  • Breadcrumbs show click history instead of canonical hierarchy.
  • Bottom navigation contains more than the compact destination set users can understand on mobile.
  • Responsive navigation hides destinations or changes destination labels across breakpoints.
  • Users lose local task state when switching top-level sections.

Saved items