If your app contains multiple destinations for users to traverse, we recommend
employing layout and navigation pairings that are commonly used by other apps.
Because many users already possess the mental models for these pairings, your
app will be more intuitive for them.

## Layout and navigation pairings

The navigation bar and modal navigation drawer are used as primary navigation
patterns for parent layout views and primary navigation destinations.

![Primary navigation UI](https://developer.android.com/static/images/design/ui/mobile/layout-basics-18-primary-navigation-destinations.webp)

The navigation bar can hold three to five navigation destinations across the
same hierarchy level. This component translates to the navigation rail for large
screens.

Although the navigation drawer can hold more than five navigation destinations,
the pattern isn't as ideal as the navigation bar.
This is because users must reach for the top bar on compact sizes.

![Secondary navigation tabs](https://developer.android.com/static/images/design/ui/mobile/layout-basics-19-tabs-secondary.webp)

[Material 3 Tabs](https://m3.material.io/components/tabs/overview) and the [bottom app bar](https://m3.material.io/components/bottom-app-bar/overview) are secondary navigation
patterns that you can use to supplement primary navigation or appear on child
views.

Here, tabs act as a secondary navigation layer to group sibling content.

## Layout actions

Provide controls to enable users to accomplish actions. Common patterns include
top bar actions, floating action button (FAB), and menus.

For actions of the highest importance, a [FAB](https://m3.material.io/components/floating-action-button/overview) provides a large
and prominent button for the user. Provide only one action at a time at this
level. A FAB can appear in multiple sizes and an expanded form, which includes a
label. Use [Scaffold](https://developer.android.com/jetpack/compose/components/scaffold) to pin a FAB, to ensure it's always visible even when
scrolling.

![Layout with FAB](https://developer.android.com/static/images/design/ui/mobile/layout-basics-20-FAB-provided.webp)

A floating action button (FAB) that lets users add plants to the plant gallery

You can place secondary actions within the top bar or, if it's grouped near
related content, within the page.
![](https://developer.android.com/static/images/design/ui/mobile/layout-basics-21-alert-action.webp) Alert action in the top bar on show detail (left) and overflow icon inline of list item (right)

For any additional actions that aren't promptly or frequently needed, add those
actions in an overflow menu.

## Adaptive navigation

Use the right layout for the window size class. Avoid using the same bottom
navigation bar across sizes.
![](https://developer.android.com/static/images/design/ui/mobile/layout_nav_do.webp)

### Do

Adjust your navigation to use a nav rail on large screens. The navigation rail is more ergonomic and visually balanced due to hand placement on larger devices and large spacing between nav items. ![](https://developer.android.com/static/images/design/ui/mobile/layout_nav_dont.webp)

### Don't

Use a bottom navigation bar on large screen sizes.

![Navigation on landscape](https://developer.android.com/static/images/design/ui/mobile/layout_landscape_nav.webp)
Medium sizes can use the nav rail or horizontal navigation items.

![Navigation on cover screen](https://developer.android.com/static/images/design/ui/mobile/layout_cover_nav.webp)
Although compact, a navigation rail might be more ergonomic on a cover screen.
Larger covers could take advantage of either navigation orientation. Consider
how the user might interact with the content.