Hacker News new | comments | ask | show | jobs | submit login

The hamburger menu's entire value is that it's a simple default that you can generalize even programmatically across all websites. It's why the frameworks mentioned in the article can implement it for you. It's a place to start.

But it requires some deliberate thought, effort, and app-specific solutions to replace it with something better, and that planning makes you answer all sorts of hard questions you might've not ever had to answer about your website/product, like "how are my users actually using this?"

I'd wager that everyone agrees that their own site's hamburger menu is a sore spot, suboptimal.

But the next rung up is a taller order than these types of articles admit.

I think a good follow-up blog post would be "Design patterns for escaping the hamburger menu" that showcases a variety of real-world approaches.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact