Would have to search to find the exact studies, but it's been found that a hamburger menu will lower engagement and result in shorter user sessions (particularly, the user will visit less pages). The intuitive answer as to why is that you're burying a very important navigation menu by making it an extra click away (and hidden from view by default).
Anecdotal side note, but when I was working on a startup in some industry, we found that our largest competitor by an order of magnitude had a navigation bar at the bottom in their mobile app, while everyone else in the space used the hamburger menu. The experience made it seem like this is common knowledge at the higher levels of app design.
Even Apple has come out and explicitly spoken against the hamburger menu as a design element for iOS apps, and instead recommends tab bars.
Most modern responsive design doesn't specifically target mobile vs. non-mobile devices, but rather simply the width of the browser window. In my experience a width of 900px is generally considered pretty low for a desktop browser, and toward the high end for tablets and large smartphone.
Bootstrap, for instance, uses 992px as the low end of its "large" media query, which is intended for desktops.
900px is not normal - that's tiny by today's standards. The only plausible alternative at a width that small would be to shrink the size of the text in the menu, otherwise it simply won't fit. Doing that would be worse to me for usability than switching to the hamburger.
> 900px is not normal - that's tiny by today's standards.
Wait what? That's tiny for a screen, but not for a (resizable!) browser window. Here's a shout-out for folks like me who run browser windows side-by-side.
Side-by-side windows are simply not used by normal users, which the vast majority of websites are designed for. The real question here is why don't you have a second monitor?
The mindset around here is "everyone should design things for my extremely specific use case that 99% of users don't share". Find me stats about the % of users with desktop browser windows narrower than 900px and then we can talk.
And I don't think you're correct. There are 5 menu items + log in + the API docs button on the main header. If you want all those to fit in a sub-standard width page, you're going to end up sacrificing readability in text. If you want to propose removing a menu item to make more space, that's an option, but just saying "I don't like the hamburger - they could fit the menu somehow" is not helpful.
What you do is fit the important stuff and hide the rest under a "more..." just because it ALL can't fit doesn't mean hiding everything is the only solution.
What is "important" in this context? Resources and About? Do you just hide stuff under "More" from right to left as you run out of space? How many people are actually going to click or hover on "More" to find out what's under there? There's a reason design trends have been shifting toward hamburger menus for smaller layouts - it's the best design choice for usability and lack of confusion once people get used to what the hamburger icon means.
since I don't use facebook I didn't know you were supposed to click on them until I started seeing articles about how bad they were. It opened a whole new world of menus.
Anecdotal side note, but when I was working on a startup in some industry, we found that our largest competitor by an order of magnitude had a navigation bar at the bottom in their mobile app, while everyone else in the space used the hamburger menu. The experience made it seem like this is common knowledge at the higher levels of app design.
Even Apple has come out and explicitly spoken against the hamburger menu as a design element for iOS apps, and instead recommends tab bars.