3 ms·
It's not just about "About". I often want to revisit a web page and the same logic applies there. In Safari, the "History" menu is always right at the top of th
by gurkendoktor 8y ago
It's not just about "About". I often want to revisit a web page and the same logic applies there. In Safari, the "History" menu is always right at the top of the screen. With a single click, I can look at recent pages, and hover over previous days.
In Firefox on Linux, I needed to learn to click on the bookshelf icon (?!) in the menu bar, then History. Then the menu acts like a wannabe iOS app and slides the history into the menu with an animation. It feels a lot more cumbersome for no good reason at all.
Both app and web designers have quickly understood that mystery meat navigation is a dead-end[1] now matter how clean it looks. I don't understand why the GNOME and elementary teams keep doubling down on it.
[1] https://thenextweb.com/dd/2014/04/08/ux-designers-side-drawer-navigation-costing-half-user-engagement/ https://thenextweb.com/dd/2014/04/08/ux-designers-side-drawe...
- Ads20000 8y agoFrom that article: 'My take-away from all of this is that if most of the user experience takes place in a single view, and it’s only things like user settings and options that need to be accessed in separate screens, then keeping the main UI nice and clean by burying those in a side menu is the way to go.' That article is saying that A/B testing shows that if you have different content views etc then you should have visible navigation, if it's options then sure, tuck it away in a side menu. I don't think the History menu is a 'view' per se...