Tithi Mondal

Article6 min readUpdated

Mobile App Navigation: Which Pattern Fits Your App

Mobile app navigation explained: bottom navigation bar, tab bar, hamburger menu and more. Pick the right pattern for your app with a clear comparison.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Mobile App Navigation: Which Pattern Fits Your App: cover illustration

A founder once showed me a draft of a food ordering app with 9 icons in a row at the bottom of the screen. Nobody could tell which icon meant "Orders" and which meant "History". The fix was not a better icon. The fix was fewer sections and a clear structure behind them. Mobile app navigation starts with structure, and the pattern comes second.

Start with information architecture, not menus

Information architecture is the way your app's content and features are grouped and named. It is the map. Navigation is the signboard on that map.

Here is a quick method I use:

  1. List every screen your app needs on sticky notes.
  2. Group notes that people use together.
  3. Name each group with a word your users already say.
  4. Rank the groups by how often a user needs them.

For a food ordering app, the groups might be Home (restaurants), Search, Orders, and Account. Four groups. That is already your bottom navigation.

If you end up with 8 groups, one of two things is true. Either some groups are really one group, or some are rarely used and belong in a "More" or profile area. Do the grouping before any visual design. I follow the same order in the five stages of my mobile app design process: understand, map the flow, then wireframe.

The bottom navigation bar

The bottom navigation bar is a row of 3 to 5 icons with text labels fixed at the bottom of the screen. It is now the default for a reason. On a large phone, the thumb reaches the bottom of the screen easily and the top corners are hard to reach with one hand.

Do this:

  • Use 3 to 5 items. With 2 items, use tabs instead. With more than 5, the touch targets shrink.
  • Write a text label under every icon: "Home", "Orders", "Wallet". An icon alone is a guess.
  • Highlight the current item with colour and a filled icon, not colour alone.
  • Keep the bar in the same place on every main screen.
  • Make each item at least 48 pixels wide and tall.

Do not do this:

  • Do not put a long list of actions in the bar. It is for sections, not tasks.
  • Do not change the items between screens.
  • Do not hide the bar when the user scrolls, if the user needs to switch sections often.

A bar with a centre action button, such as "Scan" or "Add", can work well for UPI and payment apps. Use it for one action that people truly repeat.

The tab bar at the top

A tab bar at the top switches between views of the same kind of content. Think of "Upcoming", "Completed" and "Cancelled" inside Orders. The tabs do not move the user to a new part of the app. They filter or flip within one.

Good rules for tab bar design:

  • Keep tab names to one word where possible.
  • Use 2 to 4 tabs on a phone. More tabs need scrolling, and people miss the hidden ones.
  • Allow swiping left and right between tabs, and also tapping.
  • Show the active tab with an underline and a stronger text weight.

A common mistake is stacking a top tab bar and a bottom bar with the same weight, so the user cannot tell which one is the main structure. Make the bottom bar the main level and the top tabs the second level. Never add a third bar.

The hamburger menu

The hamburger menu is the icon of 3 horizontal lines that opens a side drawer. It hides navigation. Hidden items get used less, because people do not remember what they cannot see.

Where I still use it:

  • Apps with many rarely used items, such as settings, help, legal pages and language.
  • Admin tools and dashboards on larger screens, where a side menu is normal. See my notes on admin dashboard UI/UX design.
  • As a secondary menu next to a visible bottom bar.

Where I avoid it:

  • As the only navigation for the main sections of a consumer app.
  • When the app has fewer than 6 sections. They fit in a bottom bar.

If you must use it, label it. Put the word "Menu" beside the icon. Many first-time smartphone users in smaller towns do not know what the 3 lines mean.

Which pattern for which app

Here is how I would choose, as a comparison:

App typeBest main patternSecond levelNotes
Food deliveryBottom bar: Home, Search, Orders, AccountTabs inside OrdersKeep Cart visible on the top right
Fintech or UPIBottom bar: Home, Pay, History, ProfileTabs for sent and receivedFewer items, because money screens need calm
EdtechBottom bar: Learn, Live, Progress, ProfileTabs inside a courseLive classes need a quick entry
Marketplace seller appBottom bar: Listings, Orders, Messages, AccountFilters inside listsAdd a clear "Add listing" button
Travel guideBottom bar: Explore, Trips, Saved, ProfileTabs for days of a tripOffline access to saved items matters
Admin panel on a phoneHamburger or side menuTabs inside a screenMany sections, used by trained staff
Single task app (such as a calculator)No global navigationBack button onlyDo not add a menu you do not need

For more on specific sectors, read the posts on food delivery apps, edtech apps and marketplace apps. On the Sokoni seller app, a marketplace app I designed for sellers in Tanzania, the main job was getting a seller from login to a first listing. That shaped which items got a place in the bar and which went to the account screen.

Other patterns and when they help

Some apps need something besides the three above.

  • Back button and breadcrumbs. Every screen deeper than the main sections needs a clear back arrow at the top left. Keep it in the same place.
  • Search first. If users arrive knowing what they want, such as in a large catalogue, put a search bar at the top of Home. See search and filter design (covered in a separate article).
  • Floating action button. One round button for the main action, such as "New order". Use only one per screen.
  • Gesture navigation. Swipes are fast but invisible. Always offer a visible alternative too.
  • Steppers. For a fixed sequence such as checkout, show "Step 2 of 4" and no global bar, so people stay focused.

Test your navigation with a simple task

You do not need a big study. Draw your structure on paper or in Figma, and ask 5 people to complete tasks without help:

  • "Find where you would see your last order."
  • "Change the language."
  • "Contact support."

Watch where a finger goes first. If 3 of 5 people tap the wrong item, rename the item or move it. Names cause more trouble than icons. The same method works for any app, and the steps are in my guide to usability testing on a small budget.

Also test on a small, older phone. A bar that looks fine on a large screen may crowd on a small one, and that is the phone many of your users actually hold. Designing for low-end phones and slow networks covers that side.

If you are planning an app and want the structure mapped before any screens are drawn, that is part of my mobile app design service.

Frequently asked questions

How many items should a bottom navigation bar have?

Use 3 to 5 items, each with an icon and a text label. With more than 5, the touch targets become too small and the labels get cramped.

Is the hamburger menu bad for UX?

It is not bad, but it hides items, and hidden items get used less. Use it for rarely used items and keep the main sections visible in a bottom bar.

What is the difference between a tab bar and a bottom navigation bar?

A bottom navigation bar moves users between the main sections of an app. A tab bar switches between views inside one section, such as Upcoming and Completed orders.

What is app information architecture?

It is the way an app's screens and features are grouped, named and ranked. You plan it before you choose any menu style.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.