Bottom tabs or a side menu? App navigation for stores

By Abdalla Kamesh · Published September 20, 2026 · 4 min read

Navigation is the highest-leverage design decision in a shopping app, and it is usually made by accident — whichever pattern the tool defaulted to.

The choice matters because it determines what is one tap away. Everything one tap away gets used. Everything behind a menu icon gets used by the minority of people who open menus.

The two patterns

Bottom tabs. A persistent bar with three to five destinations, always visible, always one tap away. Native on both platforms, and the pattern every shopping app your customers already use has trained them on.

A side menu (drawer). A hamburger icon that slides out a list. It holds an unlimited number of items and hides all of them behind one tap plus a scan.

The trade is exactly that: tabs make a few things prominent; a drawer makes many things available. For a store, prominence usually wins, because your job is to get people into products, not to present your site map.

Why tabs win for most stores

Three reasons, in order of impact:

Visibility drives use. A tab bar advertises its destinations continuously. A drawer requires the customer to wonder what is in it.

One-handed reach. The bottom of the screen is where thumbs are. The top-left hamburger is the hardest place on a large phone to reach.

Familiarity. Your customer’s expectation of a shopping app is a tab bar. Matching that expectation is free.

The four tabs almost every store needs

Start here and only deviate with a reason:

Home — merchandising, search, new arrivals. See designing an app home screen that sells.
Shop / Categories — the catalog, and the way into the full category tree.
Cart — with a badge showing the item count. The badge is not decoration; a visible count recovers carts by itself.
Account — orders, wishlist, addresses, support.

A fifth tab is available and should be spent on the thing your catalog most needs: Wishlist for fashion and considered purchases, Search if your catalog is large and search-first, Reorder for consumables, or a single named collection for a seasonal push.

Do not use six. Labels truncate, targets shrink, and the sixth destination gets almost no traffic anyway.

Where a drawer still earns its place

The drawer is not obsolete — it is the wrong primary navigation and a perfectly good secondary one. Put in it the things people need occasionally and should not be one tap from:

The deep category tree, beyond your top-level entries
Store policies, shipping, returns
Contact and support
Language and currency switchers
About the brand

This is the hybrid, and it is what most well-designed store apps actually run: tabs for the four or five destinations that drive shopping, a menu for everything else. StoreToNative supports tabs, a side menu, and the combination — the tab set is configurable, and it is part of the over-the-air configuration, so you can change it without a rebuild.

The rules that make either pattern work

Label your icons. An unlabeled icon row is a guessing game. A bag, a heart and a person are not universally understood, and the text costs you eight pixels.

Respect the touch floor. Every tap target at least 44×44 points. A cramped tab bar is a mis-tap generator, and mis-taps on a cart icon are lost orders.

Keep the tab bar visible while browsing. Hiding it on scroll saves a little space and costs you the cart badge, which is a bad trade. Do hide it on the product page if you need the room for a prominent add-to-cart.

Badge the cart, and nothing else. A badge on every tab is noise, and noise trains people to ignore badges — including the one that matters.

Preserve state per tab. Someone who scrolls halfway down a category, checks their cart, and comes back should land where they left. Losing scroll position is one of those small failures that makes an app feel cheap.

Mirror everything for right-to-left. In RTL layouts the tab order reverses and icons that imply direction flip. This is a rendering-level concern rather than a setting; Arabic-first commerce covers what first-class RTL actually involves.

The three mistakes worth naming

A hamburger as the only navigation. Common in apps built from a website’s menu structure, because a website’s menu is what was available. It buries your catalog.

Tabs that are categories. “Men / Women / Sale” as tabs looks tidy and breaks the moment you add a third category or a customer wants their account. Tabs are destinations, not merchandising.

More than five. See above.

How to check yours

Open your app and answer three questions honestly:

How many taps to the cart? Should be one, from anywhere.
How many taps to order history? Should be two. Order tracking is the most-used feature in most store apps and the most common reason someone opens it at all.
How many taps to your third-best-selling category? If the answer is more than two, your navigation is hiding your revenue.

Then change one thing — the tab set, most likely — and read the taps-per-block numbers again in a fortnight. Because navigation is configuration rather than code, that experiment costs you nothing but the wait.

Related reading

Navigation, layout and theme all live in the design studio, next to a live phone preview.