There's no universal best navigation pattern — the right choice depends on how many top-level destinations your product has and whether they're all equally important. Tabs and bottom nav bars maximize discoverability for three to five destinations; hamburger menus scale to long lists but hide everything behind an icon; sidebars suit dense desktop information architectures.

Quick answer: Use tabs or bottom nav for 3-5 equally weighted destinations, a hamburger/drawer for 6+ secondary items, and a persistent sidebar for dense desktop tools. Every pattern trades discoverability for scale — choose by destination count and importance, not by what looks clean in a sketch.

What Your Navigation Choice Actually Signals

Navigation is your product's information architecture made visible. Whatever sits in a tab bar or bottom nav reads as primary to the user; whatever you tuck behind a hamburger icon quietly gets demoted to secondary — whether or not that's the hierarchy you actually intended.

Every top-level nav item is a bet that this destination deserves a permanent, one-tap slot on every screen of your product. Users read that placement as a signal, and internal teams do too — arguments about "what goes in the nav" are often really disagreements about the product's core value proposition wearing a layout costume. Get the hierarchy wrong and you've structurally told users a minor feature outranks your core loop.

The psychology behind this is decades old. Hick's Law — the finding, from psychologists William Hick and Ray Hyman in the early 1950s, that decision time increases with the number and complexity of available choices — is why crowding six or seven items into one nav bar doesn't just look cluttered. It measurably slows down a decision a user makes on nearly every screen.

A navigation choice communicates more than most teams intend:

  • Primary vs. secondary status — a visible tab says "use this often"; a hidden menu item says "you'll find this if you need it."
  • The product's actual depth — a sidebar with twelve entries admits to a sprawling IA; three tabs admit to a focused one.
  • What you expect a user to do first — the leftmost or first-listed destination is read as the intended starting point.
  • How often you expect return visits — permanent nav slots imply repeat use; buried ones imply occasional use.

A common failure mode is picking a pattern because a competitor uses it, or because a hamburger "fits everything," instead of deriving the choice from actual destination count and usage frequency. That decision belongs earlier in the process, in the same conversation about whether you're solving a real problem at all — which is exactly why it's worth revisiting when a PM should wireframe vs. write before an information architecture gets locked in on autopilot.

Comparing the Four Core Patterns

Four patterns cover nearly every top-level navigation decision. Tab bars and bottom nav bars maximize discoverability for a handful of destinations; hamburger and drawer menus scale to long lists at the cost of hiding everything; persistent sidebars trade mobile screen space for desktop-scale hierarchies. Each one optimizes for a different constraint, not a different aesthetic.

Tab Bars

A tab bar — a fixed row of labeled destinations, typically along the top on desktop or web — is the most discoverable pattern available. Every option is visible all the time, with zero taps required to reveal it. Apple's Human Interface Guidelines recommend keeping a tab bar to five items or fewer, folding anything beyond that into a More tab, precisely because a sixth slot pushes past comfortable one-glance scanning.

Bottom Navigation

Bottom navigation is the mobile-specific version of the same idea, and it wins on ergonomics as much as visibility. Steven Hoober's widely cited research on how people actually hold phones found that roughly half of users operate their device one-handed with a thumb, and that the top corners of a screen are the hardest zone for that thumb to reach. That's the entire rationale for putting core destinations at the bottom on mobile instead of the top.

Hamburger and Drawer Menus

A hamburger menu — an icon that reveals a hidden list, usually a slide-out drawer — solves a real problem: it scales to any number of destinations without consuming screen space. But it solves that problem by hiding the very thing navigation exists to expose.

"Obvious always wins." — product strategist Luke Wroblewski's shorthand for why visible controls consistently outperform hidden ones across the mobile usage data he's studied for years.

Nielsen Norman Group's usability research has repeatedly found that features moved behind a hamburger icon get discovered and used noticeably less than the same features shown as visible tabs. That doesn't make hamburger menus wrong — it makes them a poor fit for anything a user needs on a daily basis.

Persistent Sidebars

A persistent sidebar is the desktop answer to the same trade-off tabs solve on mobile. Because desktop screens have width to spare, a sidebar can stay fully visible while supporting far more destinations — plus nested sub-items — than a tab bar ever could. Google's Material Design guidelines position navigation drawers and rails as the desktop-scale sibling of mobile bottom navigation for exactly this reason.

Whichever pattern you land on, treat it as a landmark, not just a layout. The W3C's Web Content Accessibility Guidelines expect primary navigation to be reachable by keyboard and exposed to screen readers as a distinct nav landmark — a requirement that applies equally to a tab bar, a bottom nav strip, and a hamburger drawer, and one that's far cheaper to satisfy in a wireframe than to retrofit after the pattern ships.

The table below compares all four side by side on the two dimensions that matter most when you're deciding: how many items each one comfortably holds, and how visible those items stay to the user.

PatternIdeal item countDiscoverabilityMobile thumb reachPlatform convention
Tab bar3-5High — always visiblePoor if placed at topCommon on web/desktop
Bottom nav3-5High — always visibleExcellentiOS & Android standard for apps
Hamburger/drawer6+Low — hidden by defaultModerate, icon often top cornerOriginated on Android; common on web
Persistent sidebar5-12+High on desktopNot applicable (desktop pattern)Standard in dashboards and admin tools

None of these numbers are arbitrary style preferences. They're a direct consequence of how much of a screen a pattern can occupy and how a thumb or eye moves across it — which means the "right" pattern shifts the moment your destination count or platform changes.

Choosing by Destination Count and Importance

Match the pattern to two numbers: how many top-level destinations you have, and how many of those are equally important. Two or three equally weighted destinations call for tabs or a segmented control; four to seven with a clear primary/secondary split call for bottom nav plus an overflow slot; eight or more call for a hamburger or a sidebar.

DestinationsEqually important?Recommended patternWhy it works
2-3YesTabs or segmented controlMinimal chrome, instantly scannable, nothing hidden
3-5YesBottom nav (mobile) or tab bar (desktop)Matches platform convention at maximum discoverability
4-7No — 2-3 primary, rest secondaryBottom nav/tabs plus a More or overflow slotProtects the primary jobs while still surfacing the rest
8+No — deep or evolving hierarchyHamburger/drawer or persistent sidebarOnly pattern that scales without a redesign at every addition
Desktop, dense IAMixed, multi-levelPersistent sidebarScreen width supports always-visible depth

Read the table as a starting hypothesis, not a verdict — it tells you which pattern family to prototype first, not which one to ship without testing.

"Importance" isn't a guess — it's measurable. Rank candidate destinations by how frequently and urgently each one serves a core job the product is hired to do. A framework like Jobs to Be Done separates a job a user does daily from one they do quarterly, and the daily job almost always earns the permanent nav slot. If you haven't ranked destinations this way yet, the jobs to be done complete guide walks through scoring frequency and importance before a wireframe gets touched.

In practice, the decision follows five steps:

  1. List every candidate destination a user might need from the top level — destinations, not individual features, meaning a screen they'd return to repeatedly.
  2. Score each by frequency and centrality to the job the product is hired to do — daily, weekly, monthly, or rarely.
  3. Count how many land in your top tier. That count, plus the yes/no on equal importance, is what the table above keys on.
  4. Pressure-test against platform limits — iOS's five-tab ceiling and the three-to-five guidance for Android bottom nav aren't arbitrary; they reflect the same scanning research already covered.
  5. Wireframe at least two candidate structures before picking one, since the count you estimated on paper often changes once destinations sit inside an actual device frame.

Where PMs Get Navigation Wrong

The most common navigation mistakes are structural, not stylistic: burying a frequently used destination behind a hamburger menu to "keep things clean," running two competing navigation systems on one screen, and locking in a pattern before testing how it holds up once real content and future destinations get added.

  • Hiding the highest-frequency destination. Teams often default the newest or most impressive feature into the visible nav and quietly demote the boring, high-frequency one — a core dashboard or inbox, say — into a hamburger menu. That inverts the priority logic above: the destination people need every session is exactly the one that should never cost more than one tap.
  • Running two navigation systems at once. A sidebar that duplicates items already in a top tab bar, or a drawer that repeats a bottom nav's own destinations, forces a user to learn two mental maps of one product. Deciding where this kind of structural call belongs is a good test case for the PM vs. designer handoff line — navigation architecture sits on the PM side of that line, visual polish on the designer's.
  • Freezing the pattern before destinations are final. A tab bar sized for four items today gets awkward fast once a fifth or sixth ships next quarter, and retrofitting navigation after launch is a far more disruptive change than choosing a scalable pattern up front.
  • Copying a competitor's pattern without their constraints. A hamburger menu that works for a content-heavy publisher with dozens of sections is a poor template for a five-feature utility app with an entirely different destination count and a different core job.
  • Treating navigation as a visual-design decision. A pattern chosen for how it looks in a moodboard, rather than for how many destinations it needs to hold and how important each one is, tends to unravel the moment real content and edge-case labels get dropped in.
  • Skipping a test under real content. A sketch of a nav bar with four short placeholder labels almost always looks cleaner than the same bar carrying your actual, longer feature names — the gap only shows up once it's tested at real size.

Prototype the Navigation Before You Commit

The only reliable way to know whether a navigation pattern holds up is to build it at real size, with real labels, inside a device frame, before a single line of production code exists. A wireframe reveals crowding, label truncation, and thumb-reach problems that a bullet list of requirements never will.

Navigation is one of the clearest cases where sketching it out earns its keep before a designer or engineer touches it. The wireframing complete guide covers the broader case for prototyping structure before polish, and the specific building block for a nav bar, drawer, or bottom-tab layout — the reusable piece every wireframing tool assembles screens from — is covered in the wireframe layout blocks vocabulary.

It's also worth mapping navigation against the paths users actually take through a product, not just a static list of destinations. The customer journey complete guide is the reference for laying those paths out stage by stage — often the exercise that reveals a destination you assumed was primary is actually a rare, end-of-journey stop that belongs behind a hamburger, not in front of one.

This is also the exact test Prodinja's Wireframing composer is built for. It includes a navbar block you can arrange directly inside the device frame — swap it between a tab layout, a drawer, or a bottom-nav strip, drop in your actual destination labels, and see whether five items still fit cleanly or the sixth forces an overflow decision, before that decision becomes expensive to reverse in code.

Key Takeaways

  • Navigation is information architecture, not decoration — whatever sits in a tab bar reads as primary; whatever hides behind a hamburger reads as secondary, intentionally or not.
  • Tabs and bottom nav win on discoverability for 3-5 destinations; Apple's five-tab ceiling and Steven Hoober's thumb-reach research both point the same direction on mobile.
  • Hamburger menus trade discoverability for scale — fine for 6+ secondary destinations, risky for anything a user needs every session, per Nielsen Norman Group's usability findings.
  • Sidebars are the desktop-scale answer, supporting far more destinations and nesting than any mobile pattern, per Google's Material Design guidance.
  • Rank destinations by frequency and centrality to the core job before picking a pattern — Jobs to Be Done gives that ranking a repeatable method instead of a guess.
  • Wireframe the navigation with real labels and real counts before committing — crowding and truncation problems rarely surface in a placeholder-label sketch.
  • Design for tomorrow's destination count, not just today's, since retrofitting a navigation pattern after launch is more disruptive than choosing a scalable one up front.

Frequently Asked Questions

Should I use a hamburger menu on mobile?

Use a hamburger menu only for destinations a user needs occasionally, not the ones core to daily use. Reserve your bottom nav's three to five fixed slots for the features people return to every session, and push everything else behind the icon.

How many items should a bottom nav bar have?

Three to five is the practical ceiling, matching both Apple's and Google's platform guidance. Beyond five, either drop a destination back a level or introduce a More tab, since a sixth or seventh icon starts hurting scanability and thumb accuracy rather than adding convenience.

Are sidebars better than bottom navigation?

Neither is universally better. A sidebar suits a desktop, dense-IA product with room to spare, while bottom nav suits mobile apps with a small, stable set of destinations — the deciding factor is screen width and destination count, not preference.

Can I combine tabs and a hamburger menu on the same screen?

Yes, but only when they serve genuinely different jobs. A tab bar for the primary 3-5 destinations paired with a hamburger for account, settings, or rarely used utilities is a common, well-tested combination; duplicating the same destinations in both is the mistake to avoid.

Does the navigation pattern affect app store conversion or SEO?

Indirectly. Navigation clarity affects engagement and retention metrics — time in app, feature adoption — that stores and search algorithms weight, but there's no direct ranking factor tied to choosing tabs over a hamburger menu. The impact runs through usability, not through a direct algorithmic signal.