Paths Subjects Questions Quizzes Pricing Search
Intermediate Open Pro

Defending (or Rejecting) a Hamburger Menu in a Design Review

In a design review, a stakeholder pushes back on your proposed bottom tab bar (Home, Search, Saved, Profile) for a mobile app, suggesting instead: "let's just put everything behind a hamburger menu, it'll look cleaner and we won't have to decide what makes the cut for the tab bar."

  1. What is the stakeholder's proposal actually trading away, stated precisely?
  2. Under what circumstances would the hamburger menu actually be the right call here, if any?
  3. How would you respond in the review — what data or reasoning would you bring, rather than just asserting a preference?

Share this question

← Back to Information Architecture and Navigation practice

We use cookies for product analytics to improve OmniAtlas. See our Privacy Policy.