Should Your App Use Bottom Navigation or a Menu Drawer?
Choose bottom navigation when your app has a small set of main destinations that users need to switch between often. Consider a navigation drawer when users need a broader directory of sections, especially when those sections need grouping. For bottom navigation vs navigation drawer decisions, start with users' regular tasks, then check whether the destinations fit with clear labels and predictable behaviour.
What belongs in your app's main navigation?
A destination is a place users return to, such as Bookings, Messages or Account. An action is something they do, such as making a booking or sending a message. Keep that distinction clear: a button that creates something should not look like a tab that opens a section.
Write down the main things someone needs to accomplish. For each task, identify where it starts and which other sections the person may need along the way.
Then separate your list into:
- Main destinations: places central to regular use.
- Supporting destinations: places needed occasionally, such as help or preferences.
- Screens within a destination: details, filters and steps that belong inside a section.
Do this before choosing a navigation component. Otherwise, a long screen list can become a crowded menu. Our guide to how to scope an app MVP can help you decide which tasks belong in the first release.
How should destination count affect the choice?
Count the main destinations, not every screen in the app. A booking detail screen does not need its own navigation item if it belongs within Bookings.
For bottom navigation, sketch the actual labels at the smallest supported screen size. If they need awkward abbreviations, compete for space or hide essential destinations behind More, revisit the structure.
A drawer gives you a way to present a longer, grouped list. Treat that space as a reason to organise carefully, rather than permission to add every feature.
| Planning question | Consider bottom navigation when… | Consider a drawer when… |
|---|---|---|
| What needs frequent access? | The same compact set of destinations matters throughout a session. | Users need access to a broader collection of sections. |
| How do the labels fit? | Each destination has a short, distinct label. | Clear labels need more room or grouped headings. |
| How is the app organised? | The main destinations sit at the same level. | Sections need a directory with meaningful groups. |
| What happens during a task? | People switch repeatedly between main sections. | People usually enter a section and work within it. |
Use this table to form a starting hypothesis. Validate it with the tasks your app must support.
What makes a navigation label clear?
Prefer labels that describe what someone will find. Bookings tells a person more than Hub if the section contains their appointments. Avoid using different labels for nearly identical content.
Write labels before choosing icons. An icon should support the meaning, and a visible label should make the destination understandable without a guess.
Try a simple review: show someone the navigation labels without explaining the screens. Ask where they would look for a particular item. If their answer differs from your intended structure, investigate whether the label or the grouping needs to change.
Also check translated labels and enlarged text. Do not approve a layout solely because its shortest wording fits.
How should nested sections work?
Keep the main navigation focused on destinations at the same level. Within a destination, use a list, local tabs or another clearly labelled route to its subsections.
For example, Account might contain personal details, notification preferences and help. Those screens do not automatically need separate bottom navigation items.
A drawer can group destinations under headings, but avoid building a deep tree of expanding menus on a small screen. If finding an item requires several guesses, reconsider the grouping or provide a direct route from the relevant task.
Decide what Back means at each level. From booking details, it could return to the booking list. That behaviour should remain understandable whether someone arrived through main navigation or a notification.
How should you check one-handed use?
Test the real interaction on a phone, using the hand positions your audience is likely to use. Do not assume that putting navigation at the bottom settles the question.
For a drawer, check how someone opens it, selects an item and closes it without making a selection. For bottom navigation, check every item, including those at the edges.
Include the keyboard in the review. Someone writing a message should have a clear way to finish, dismiss the keyboard or leave the screen without losing work.
Reach is only part of the decision. Check that touch targets remain distinct, labels remain readable and assistive technology announces the selected destination. Include these journeys in your Android app testing before release.
What should happen when someone switches sections?
Define what each destination remembers before implementation. Switching sections should have an explicit result, rather than whatever the screen happens to do.
Consider a person browsing a filtered booking list, opening Messages, then returning. A sensible requirement might preserve the filter, scroll position and selected booking.
For each main destination, specify whether the app keeps:
- The current screen within the section.
- Search terms, filters and sort order.
- Scroll position.
- Unsent text or other unfinished input.
Separate keeping a person's place from keeping information current. A returning screen may need fresh booking details while retaining its filter.
Also define exceptions. Signing out should clear private content. If a saved item has been removed, explain that change and provide a useful next step.
What would this look like in a booking app?
Consider this illustrative example: a booking app has four main destinations, Book, Bookings, Messages and Account. Help and preferences sit inside Account.
Start with bottom navigation because the proposed journeys involve switching between availability, existing bookings and conversations. Keep those destinations visible while reviewing the prototype.
Now change the scenario. The app also serves staff who need schedules, customer records, service settings and reports. Do not simply add every staff section to the same bottom bar.
First decide whether staff need a separate workspace. Within that workspace, a grouped drawer may be worth testing. The choice follows the work each audience needs to do.
For both versions, test the same continuity requirement: someone opens a booking, checks a conversation and returns to that booking without rebuilding their search.
What common mistakes should you avoid?
Giving every feature equal prominence. Ask which destinations deserve attention throughout a session. Place supporting features where their context makes sense.
Using a drawer to avoid prioritising. A long menu still needs clear labels, sensible grouping and a reason for each entry.
Mixing actions with destinations. Keep Create booking distinct from Bookings so people can predict whether a tap opens a section or starts a task.
Resetting sections silently. Specify what switching preserves and make deliberate refresh or restart behaviour clear.
Treating one layout as permanent. Revisit navigation when the product's tasks change. Adding a feature does not automatically justify adding another main destination.
When might neither pattern be necessary?
An app built around one focused task may need neither a persistent bottom bar nor a drawer. A clear starting screen with local controls may be enough.
Similarly, a checkout or onboarding flow may need focused step navigation. Decide how someone leaves safely and what happens to unfinished input before hiding the wider app navigation.
What are the frequently asked questions?
Is bottom navigation always better than a drawer?
No. Start with the destinations users need most often. Choose bottom navigation if that set fits clearly; test a drawer when a broader, grouped directory better matches the work.
Can an app use both?
It can, but give each a distinct purpose. Avoid duplicating the main destinations across both. Before adding a drawer, check whether supporting items belong within Account or another existing section.
Is there a fixed destination count that decides the answer?
Do not use a count alone. Review label length, available space, text scaling and the journeys between sections. A layout that technically fits can still be unclear.
Should switching tabs return users to the start?
Choose and document the behaviour. For tasks involving frequent switching, preserve useful context. Define tapping the already selected tab separately so it does not cause an unexpected reset.
Before approving the design, walk through a complete task that crosses sections. Check that each destination is easy to identify, easy to reach and still in a useful state when the person returns. To plan how those screens adapt to different screen sizes, see how to plan app layouts for phones and tablets.