3 ms·
OK...and what does that look like on a desktop browser? Because if I click on a menu button on a desktop browser, I generally don't expect it to take over the
by danaris 6mo ago
OK...and what does that look like on a desktop browser?
Because if I click on a menu button on a desktop browser, I generally don't expect it to take over the entire page with a menu.
This seems like an example of unhelpfully mobile-centric website design, which has been becoming more prevalent in recent years.
- graemep 6mo agoI agree, but its not intrinsic to the approach of less JS and more pages.
- carlosjobim 6mo agoYou should of course not have a menu button on a desktop view. There is plenty of space to show the menu without hiding it behind a button. Maybe it is you who are mobile centric?
- alentred 6mo agoI just tried it on their website, using the desktop browser, and the experience is absolutely OK: you just get the menu as in any web app, and you can close it to go back, etc. Just an old-school page which is blazing fast ... because it is an old-school page. It renders faster than a typical animation to open a sidebar.
- pibaker 6mo agoBut you don't need to open a menu to navigate to another page on an old school web page. Web pages in the 00s just showed you links to other parts of the website on a navbar that is always there. I agree this website is optimized for phones and works poorly on desktop — there is absolutely no reason to hide your links behind a burger menu when I have more than enough pixels on my monitor for all your links.