| ▲ | danaris 2 hours 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. | ||
| ▲ | alentred an hour ago | parent | next [-] | |
I 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. | ||
| ▲ | graemep 2 hours ago | parent | prev | next [-] | |
I agree, but its not intrinsic to the approach of less JS and more pages. | ||
| ▲ | carlosjobim 2 hours ago | parent | prev [-] | |
You 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? | ||