Design Back Button Behavior

Navigation & IA · navigation, undo, mobile

Updated 2026-07-28

Respect the most used control in any browser. Back is the universal undo for navigation, and breaking it makes an application feel untrustworthy.
Decide what counts as a step. Opening a detail view is a step, changing a filter usually is, and typing another character into a search box is not.
Replace rather than push for rapid changes. A search that adds a history entry per keystroke means the user has to press back thirty times to escape.
Make back close the topmost layer. On a phone especially, back should dismiss an open sheet, drawer, or dialog before leaving the page.
Warn before losing work. If going back would discard an unsaved form, intercept it and offer a choice rather than silently throwing the work away.
Restore the previous state completely, including scroll position, expanded rows, and loaded results. Returning to the top of a reset list is the most common complaint about single-page applications.
Do not trap the user. Redirect loops and pages that immediately push forward again make the button useless and feel deliberately hostile.
Keep forward working too. Going back and then forward should return the user exactly where they were.

Back is the escape hatch users try first, and every product that breaks it teaches people to stop exploring.