I saw an article about how a 21 year old brand logo (Lao Gan Ma 老干妈 chili sauce) became a fashion icon[0] for Chinese Fashion Week and wondered what the Western world would be like if companies didn't rebrand so often. The Lao Gan Ma logo certainly wouldn't have the same cachet if it was a 2 year old logo that looked nothing like the original[1].
Is it possible to make brands (or software) that's just "done?"
Notably the brand is for a chili and condiment company. In that field, recalling nostalgia and your grandma's recipes makes sense. But no one wants to use their grandma's old software
Why do sites continue to use the hamburger menu??? (and also hide the menu if we don't decide to allocate 1200px of real estate to basically empty website!?)
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?
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.
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.
Same with Chrome and Firefox in Win10. Even Chrome's device/touch emulation doesn't work. It does work on iOS Safari. Can't say I've seen such weird event handling in a while.
I do know that is the default for many popular Wordpress themes. The hamburger break-point is usually too generous. It looks like its just a poor use of spacing that leads to premature hamburgerization:
@charleyma, why does the company go with that vector art style that _every_ website has these days? It is no longer unique or recognizable.
It looks cool, and management is probably going to be super happy. But that's not what a brand is about. It should be identifiable and recognizable. This does nothing of that.
Is it possible to make brands (or software) that's just "done?"
[0]: http://www.sixthtone.com/news/1002903/face-of-chinese-chili-...
[1]: https://www.reddit.com/r/firefox/comments/9ewvb7/firefox_log...