Journal

How to design mobile navigation people actually use

A practical guide to mobile menus, tab bars and tap targets, so visitors on phones can find what they came for.

How to design mobile navigation people actually use

Mobile navigation is where a lot of good desktop designs quietly fall apart. The top bar with seven links becomes a hamburger, the hamburger hides everything that mattered, and visitors end up scrolling, guessing or leaving. Nobody complains about it in a usability report as "navigation". They just say they couldn't find the pricing page.

This guide walks through how we approach mobile navigation for marketing sites and product UIs: what to show, what to hide, where to put it and how to check that it works. It applies whether you build in Framer, Figma or code, and it works for a five-page portfolio as well as a product with dozens of screens.

Start with the jobs, not the sitemap

The sitemap tells you what pages exist. It doesn't tell you what people came to do. Before you design a single menu, write down the three to five things most visitors on a phone are trying to get done. For a studio site that is usually: see the work, understand the price range, get in touch. For a SaaS product it might be: check the dashboard, create something new, find a past item.

Those jobs decide what deserves to be visible at all times. Everything else can live one level deeper. If you skip this step, you end up treating "Careers" and "Book a call" as equals in the menu, and on a small screen that is a real cost.

Pick the pattern that fits the number of destinations

There is no single right mobile navigation pattern. There is a right pattern for how many top-level destinations you have and how often people switch between them.

  • Two to five frequent destinations in an app: a bottom tab bar. It keeps everything one tap away and shows where you are.
  • A marketing site with a clear primary action: a compact top bar with the logo, one visible call to action and a menu button for the rest.
  • Many sections people rarely switch between: a full-screen menu, ideally grouped with short headings.
  • Deep content like docs or a shop: a menu for top-level categories plus search, because nobody wants to drill four levels down on a phone.

Mixing patterns is fine as long as each one has a clear job. A tab bar for core screens and a top-right menu for settings is a common, understandable combination.

Don't hide the one thing that pays the bills

The hamburger menu is not evil, but it does make whatever is inside it less visible. That is a good trade for "About" and "Privacy". It is a bad trade for "Pricing", "Book a demo" or "Shop".

Keep your primary action outside the menu on mobile. On a marketing site that usually means a small button next to the menu icon in the top bar. In an app, it might be a dedicated tab or a floating action. If you can only afford one visible element besides the logo and the menu, make it the action that moves the business forward.

A useful test: cover the menu icon with your thumb. Can a first-time visitor still reach the most important next step?

Design for thumbs and real tap targets

People hold phones in one hand more often than designers assume, and the top corners of a large phone are hard to reach. That is why bottom navigation feels easier in apps and why a menu that opens from the bottom, or places its links in the lower half of the screen, is more comfortable than a dropdown pinned to the top.

Tap target size matters just as much. Apple's Human Interface Guidelines recommend controls of at least 44 by 44 points, and Material Design recommends 48 by 48 dp. WCAG 2.2 adds a minimum target size criterion of 24 by 24 CSS pixels for AA. Treat the platform numbers as your working minimum and the WCAG one as the floor you should never go under.

  • Give each menu link the full row width as its tap area, not only the text.
  • Leave at least 8px between adjacent targets so a slightly off tap doesn't open the wrong page.
  • Make the close button as easy to hit as the open button.

Write labels people don't have to decode

On mobile there is less surrounding context, so labels have to work alone. "Solutions", "Resources" and "Explore" tell the visitor almost nothing. "Pricing", "Case studies" and "Templates" do. If a label needs an explanation, it is the wrong label.

For tab bars, always pair icons with text. Icons alone look clean in a mockup, but outside a handful of universal ones like home and search, people read them differently. Short, plain words under each icon remove the guesswork and cost very little space.

Show people where they are

Navigation is not only about getting somewhere. It is also about knowing where you are now. On mobile, where only one screen of content is visible, this orientation is easy to lose.

  1. Highlight the active tab or menu item with more than colour alone, for example a filled icon, a bolder label or an indicator line.
  2. Use clear page titles near the top, especially on screens reached from a menu.
  3. Keep the back behaviour predictable. If a screen opens from a list, going back should return to the same scroll position in that list.

Make the menu fast to open and easy to leave

A menu that slides in slowly, blocks the page with a heavy animation or traps focus feels broken even when it works. Keep open and close transitions short, around 200 to 300 milliseconds, and let people close the menu by tapping the overlay, tapping the close button or using the system back gesture.

Also check the boring details. The page behind an open menu should not scroll. Long menus should scroll inside themselves. Keyboard and screen reader users need the menu button to announce whether it is expanded, and focus should move into the menu when it opens and return to the button when it closes. In Framer, test the menu overlay on an actual phone, not only in the canvas preview, because scroll locking and safe areas behave differently on device.

Test it with five quick tasks

You don't need a lab to check mobile navigation. Hand your phone, or a live preview link, to three to five people who haven't seen the design and give them short tasks based on the jobs you wrote down at the start: "Find out how much a project costs", "Open the latest case study", "Get back to the home page".

Watch where they tap first, not just whether they succeed. If people consistently open the menu to find something you thought was obvious on the page, or skip the menu and scroll endlessly instead, that is the signal to move things around. A small round of this testing catches more problems than another hour of polishing the menu animation.

Conclusion

Good mobile navigation comes from a few clear decisions: know the jobs visitors came for, pick a pattern that fits your number of destinations, keep the primary action visible, size targets for thumbs and use plain labels. Then put the design in front of real people on real phones. Do that, and your menu stops being the place where visitors get lost and becomes the shortest path to what they came for.

Oybek Ruziev

Designer & Framer developer · AidanCreates

Keep reading

All posts