A drawer holds infrequent navigation or auxiliary content
Aliases: navigation drawer · side sheet · auxiliary drawer
What it is
A drawer is a panel that slides from a screen edge, covering or pushing the main surface, for infrequent navigation or auxiliary blocks. Settings, secondary destinations, filters for the current page belong here; primary navigation and fields used on every record do not. The structural cost is that the content is off-stage by default and enters the page model only after an open. Putting a high-frequency path inside it hangs a door on the main task.
Why it happens
The main surface’s area is standing attention. A drawer moves a function off that area so the main task is cleaner, and in return that function must be summoned. Summoning costs: find the entry, open, locate inside. Infrequent paths can pay because they are rare; high-frequency paths pay every time, and the sum is dearer than a persistent slot. Auxiliary content (filters for this list, secondary attributes of this record) relates to the main column without earning a place in it; the drawer parks them on a temporary layer beside the column and leaves. Primary navigation inside a drawer makes destinations as reachable as the entry is visible, so those pages are visited less — not because they are unneeded, because they are absent. A drawer is not a small modal: main content often remains faintly visible, and the task does not require finishing the drawer first. Choosing a drawer is choosing a summonable side, not a “answer this first.”
Studying it
Place the same destinations in a persistent tab bar, a persistent sidebar, and a drawer, and measure arrivals and time. Independent variables: entry visibility, original frequency of the destination. Dependent variables: change in arrival rate, interruptions of the main task. High-frequency destinations should drop in arrival once in a drawer; low-frequency ones should shorten main-task scrolling. “The UI looks cleaner” is not a substitute for arrival rate.
Where it stops holding
On a wide desktop a persistent sidebar beats a drawer, because horizontal resolution is enough and summoning is unnecessary. A tool panel an expert opens every hour is no longer infrequent; the drawer becomes occupational damage. If the drawer holds required steps of the current task, it is carrying the main flow in the wrong container. Assistive-tech users pay more to open a drawer (another landmark, another focus move); infrequent still holds, high-frequency holds even less.
Applying it
- List frequency for each navigation or auxiliary block. Only paths clearly below the main route go in the drawer.
- Filters, help, and secondary attributes of the current page may go in a drawer; switching the app’s primary destinations should not depend on a drawer alone.
- Name the entry after the category inside; do not hide a whole infrequent group behind an unlabeled icon.
- How to check: in real use, count drawer opens and the tasks finished after opening. If the main path opens it constantly, the content should come out and persist.