Structuring movement through an application.
WHAT THE COMMON PATTERNS ARE
Tabs, for a few top-level destinations A drawer, for many destinations A stack, for drilling into detail Modals, for tasks requiring completion
WHEN TO USE TABS
Three to five destinations of equal importance.
WHY THAT LIMIT
Beyond it, tabs become cramped and unmemorable.
WHEN TO USE A DRAWER
Many destinations, most used infrequently.
WHAT A DRAWER COSTS
Discoverability. Content behind it is used considerably less.
WHAT TO KEEP OUT OF A DRAWER
Anything important.
WHAT TO ENSURE ABOUT BACK
That it behaves predictably from every entry point, including notifications and links.
WHAT TO AVOID
Deep hierarchies requiring many taps Navigation that loses the user's place Screens with no obvious way back Bottom navigation combined with a drawer containing the same items
WHAT TO PRESERVE
Scroll position and state when returning.
WHY
Losing it after scrolling far is a significant frustration.
WHAT TO TEST
Every screen entered directly, then back.
