What navigation is for
Navigation answers three questions every person asks, usually without noticing: where am I, where can I go, and how do I get back. If an app answers these clearly, people feel oriented. If it does not, they feel lost, even if each screen looks fine by itself.
There are three widely used patterns on phones: tab bars, navigation drawers and stacked screens. Most real apps combine them. Understanding what each does well makes the combinations easier to choose.
Tab bars
A tab bar is a row of icons and labels, typically along the bottom of the screen, that lets people jump between the app’s top-level sections.
Strengths
- All the main destinations are visible at once, so people can see what the app offers.
- Switching sections takes one tap.
- The bottom of the screen is comfortable for a thumb, which fits well with thumb reach.
- The current section is clearly highlighted.
Limits
- Space is limited. Guidelines for the major platforms generally suggest a small number of tabs, commonly around three to five, but check the current recommendations for the system you build for.
- Every tab must be a real, equal destination. A tab labeled “More” that hides half the app is a sign of poor structure.
- Icons without labels are often misread.
Tab bars suit apps with a few peer sections that people switch between often, such as a home feed, search, saved items and a profile.
Navigation drawers
A drawer, sometimes called a hamburger or side menu, slides in from the edge and lists destinations.
Strengths
- It holds many destinations without using permanent screen space.
- It keeps the main screen uncluttered.
Limits
- Hidden items are used less. People often do not open the menu unless they know what is inside.
- The control is usually in the top corner, which is the hardest area to reach one-handed.
- It makes the app’s structure invisible, which hurts discoverability.
Drawers are best for secondary destinations such as settings, help and account pages, or for apps with a large number of sections where most are visited rarely. A common compromise is a tab bar for the main areas and a drawer or settings screen for the rest.
Stacked screens
In a stack, each new screen is placed on top of the previous one. A list leads to a detail page, which leads to an edit page, and a back control removes the top screen to return to the one beneath.
Strengths
- It mirrors how people think about going deeper into a topic.
- The back control gives a consistent way out.
- It scales naturally for content with a hierarchy.
Limits
- Deep stacks make people tap back many times. Jumping to the start can become tedious.
- Without clear titles or breadcrumbs, people can lose track of how they arrived.
Stacks are the backbone of most apps, usually working inside each tab of a tab bar. Each tab can keep its own stack, so switching tabs and returning does not lose the person’s place.
Other patterns worth knowing
- Top tabs or segmented controls switch between views of the same content, such as “All” and “Unread.” They should not be confused with the main navigation.
- Modal screens appear over the current one for a focused task, such as composing a message. They need a clear way to close or save.
- Search is a navigation method in its own right and is often the quickest route in apps with large amounts of content.
- A single screen with sections can be enough for very small apps. Not every app needs a navigation system.
Choosing between them
A few questions help.
- How many top-level destinations are there, and are they equal? A handful of equal ones points to tabs. Many unequal ones suggest a drawer or a search-first design.
- How often do people switch? Frequent switching favors always-visible controls.
- Is the content hierarchical? If so, use a stack.
- What do people do most? Put the main task one tap away.
- What will people expect? Familiar behavior reduces learning.
Writing short user stories beforehand shows which journeys matter most, and sketching the screen map on paper makes weaknesses visible before anyone writes code. Paper wireframes make it easy to draw several structures and compare them.
Consistency and back behavior
Whatever you choose, apply it consistently.
- Use the platform’s standard back behavior, including the system back gesture or button on Android and the edge swipe on iOS, rather than inventing your own.
- Make sure the back action returns to where people expect, not to an unrelated screen.
- Keep the same control in the same place across screens.
- Do not trap people. Every screen should offer an obvious way out.
- Label items with plain words. Vague labels such as “Hub” or “Zone” make people guess, which links to the wider topic of interface microcopy.
Navigation and attention
Navigation also influences how long people stay. An app that buries the way to leave, or that keeps pushing new content into view, can encourage endless wandering. A calm structure lets people finish a task and put the phone down, which supports digital wellbeing. This matters especially in apps for children.
Test the structure
Give people a task, such as “find your saved items” or “change your email address,” and watch where they tap first. If several people go to the wrong place, the structure or the labels need work. Do this with a rough prototype or a paper mock-up, because moving things around is cheap early on and expensive later.
Good navigation is mostly invisible. People simply reach what they want, and the app stays out of the way.