platform-guideline 2 linked patterns checked
Android Developers Responsive Navigation
Documents choosing bottom navigation for compact-width apps with few items, navigation rail for medium widths, and drawers for larger or many-item navigation.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Bottom navigation | Choose bottom navigation for three to five top-level mobile destinations of similar importance. | Activating an item switches to its top-level destination rather than performing a transient command. | Android responsive navigation maps compact-width few-item navigation to bottom bars and wider layouts to rails or drawers. |
| Responsive navigation adaptation | Choose responsive navigation adaptation when the navigation surface itself must change across viewport, posture, orientation, or destination-count constraints. | The adapted surface changes presentation, not the user's destination model. | Supports responsive choice among bottom navigation, navigation rail, and drawer according to width and destination count. |
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: Google. Last checked: .