4 ms·
Thankyou. I’ve been using computers for 35 years (I grew up using xtree to navigate folders on DOS). It would never have occurred to me that both sides of that
by josephg 2y ago
Thankyou. I’ve been using computers for 35 years (I grew up using xtree to navigate folders on DOS). It would never have occurred to me that both sides of that view options dropdown do different things. Perhaps it’s intuitive for others, but I’ve never seen that before in my life.
I’m increasingly of the opinion that I hate almost all novel interaction patterns in user interfaces. UI components and flows should stick as close to common patterns / system defaults as possible - and no, your app, whatever it is, is not an exception
- lbschenkel 2y agoExactly. The traditional design language is that an arrow besides a button indicates that the button will show a drop-down when pressed (traditionally without a line separating the two), or that clicking on the button will do the default action while clicking on the arrow will show all the actions (traditionally with a thin line separating the two). Reusing that design language but making the button and the arrow two completely different buttons with their own actions sets wrong expectations for no good reason.