Few visual patterns are as widespread on the mobile web as the burger menu. Almost every user today recognizes what the three horizontal lines mean, even if hardly anyone remembers which designer originally drew the icon.
Why did the burger menu become the default?
Screen space on a phone is tight. As soon as a site or app grows past three or four top-level sections, a visible navigation bar at the top or bottom starts to feel cramped. That is when teams reach for the burger menu almost by reflex: tuck the entire navigation into a drawer behind one icon in the corner, and the layout immediately looks clean.
Where does the burger menu help?
- Cleaner visual layout: Fewer elements compete for attention on the initial view.
- Less upfront friction in layout: It spares you the hard choices about information hierarchy early on, because everything seems to fit inside the drawer.
- Familiar convention: Most users recognize the three lines without needing a label.
What is the real problem with the burger menu?
Even though the burger menu saves us some hard thinking about information architecture, that convenience comes at a real cost: out of sight, out of mind. Everything tucked behind those three lines gets clicked noticeably less often than navigation items that stay visible on screen. In the worst case, visitors never make it past the landing page because nothing prompts them to open the drawer in the first place.
It also turns every navigation step into two taps instead of one: first open the menu, then scan the list and tap the destination. On desktop screens, where there is plenty of room for visible navigation, hiding the menu behind a burger icon mostly adds friction for the sake of minimalism.
My take
Personally, I am not a fan of the burger menu and avoid relying on it in client projects whenever a visible header or bottom tab bar can surface the core destinations directly. Why did I still experiment with it on my own site for a while? Mostly because it looked clean and I enjoy testing ideas on my own turf, with the goal of running an A/B test once traffic allows to see how much it really changes visitor behavior.

No comments yet. Be the first!