[mlyle]

> That's a bit of a straw man.

It's not a straw man; it's nuanced agreement. It's a shame that people expect argument so much that they can't see where the edges of one opinion are being offered.

> However, there's no reason those menus need to be touchscreen menus.

Might as well be touchscreen menus. Using up and down buttons to pick things in a modal interface isn't clearly superior to a touchscreen for experienced users and worse for new people.

A good button menu system is better than a bad touchscreen, especially with experience. But in a rental car, I appreciate the touchscreens to pair my phone, etc.

[tablespoon]

> It's not a straw man; it's nuanced agreement. It's a shame that people expect argument so much that they can't see where the edges of one opinion are being offered.

I understand that, that's why I said it was "a bit" of one.

> Might as well be touchscreen menus. Using up and down buttons to pick things in a modal interface isn't clearly superior to a touchscreen for experienced users and worse for new people.

IMHO, if you have the space, f-key/button menus (e.g. the hardware shown at https://www.informatique-mania.com/en/tutoriels/quest-ce-que...) are better than touchscreen menus.

[mlyle]

> IMHO, if you have the space, f-key/button menus (e.g. the hardware shown at https://www.informatique-mania.com/en/tutoriels/quest-ce-que...) are better than touchscreen menus.

I like avionics and ATMs where you see these. They're great for experienced users with relatively fixed functionality.

You can't tradeoff UI factors so easily, though. If you usually have 5 options, and found you have 6 somewhere-- you need to break up the section or add a page, etc. And if you add an option the user UI workflow completely changes.

While, with a touchscreen you could accept a smaller target for the least-used option, and adding a new target on a page doesn't change things too much for users (and is arguably more discoverable).