Keyboard shortcuts or clickable controls? What's your preference?

While testing different new photography applications, I occasionally come across small interface puzzles. For example, how do you hide or restore a filmstrip when there is no visible arrow, button or handle? The solution might be a keyboard shortcut, but you first need to know it exists.

This got me thinking about how people prefer to interact with their software.

Some examples:

  • Keyboard shortcuts to show or hide panels, toolbars and filmstrips.
  • Visible buttons, arrows or handles that you can click.
  • Both options available.
  • Context menus or other ways of accessing these functions.
  • Or perhaps you prefer a minimal interface without too many visible controls.

What’s your preference? Do you prefer keyboard shortcuts, clickable controls, both, or neither?

I think this is particularly interesting for developers working on new applications. Knowing what users actually prefer can help them make better interface decisions from the start. These small choices can determine whether an interface feels clean and intuitive, cluttered and chaotic, or even unnecessarily difficult to use.

So, what’s your take? I’d be interested to hear from both everyday users and those developing the software we use.

This is incredibly individual: For me it is Keyboard shortcuts all the way. The only reason I don’t have any more shortcuts setup in darktable is that almost every single key is already taken including modifiers :smiley: .

1 Like

So, for you it’s not just keyboard shortcuts, but being able to customise and assign them to the functions you use most. That’s another level of flexibility! I can certainly understand that, especially in an application as feature-rich as darktable. Although I suspect finding an unused key combination is becoming an art in itself! :grin:

Clickable controls for me. I have trouble remembering a plethora of keyboard shortcuts.

4 Likes

I’m with you, Tim! My brain is already like a sieve. If I had to remember all those shortcuts, I’d need to keep a book beside my computer. And knowing my luck, I’d probably forget where I put the book! :joy:

2 Likes

I’m in between of the extremes. I do love keyboard shortcuts and use the a lot. I like to and do assign them myself as well. But my brain is not able to remember it all. leaving me happy with clickable controls and very important tooltips to remind me of - self assigned - shortcuts.

I love dt for the vast flexibility it offers in this respect.

1 Like

Keyboard shortcuts for me. They are faster and more ergonomic than using the mouse.

(And ā€œviā€ is the ultimate text editor.) :slight_smile:

1 Like

Clickable buttons for me 90% of the time. I understand the benefits of keyboard shortcuts but struggle to remember them or even remember that they exist :joy:
I do have ADHD so the (highly debatable!) ā€œobject impermanenceā€ may have something to do with it.

(If you don’t want to look it up it basically means an overdose of the normal human propensity towards ā€˜out of sight out of mind’)

1 Like

Interesting to see the different preferences already emerging. Some prefer keyboard shortcuts, others clickable controls. And I suspect there are plenty of people who like having both.

But here’s why I think this discussion is worth having, especially for developers working on new applications.

These seemingly small decisions can have a considerable impact on the user experience. A function that can only be accessed through a keyboard shortcut isn’t particularly discoverable if you don’t know that shortcut exists. On the other hand, filling an interface with buttons and controls isn’t necessarily the answer either.

The challenge is finding the right balance between a clean interface and one that remains intuitive and easy to use.

And this is where your feedback matters. The applications being developed today will be the tools we use tomorrow. What users prefer, what frustrates them and what makes their workflow easier can actually influence how future software is designed.

So don’t be shy about sharing your preferences, even if you think they’re rather ordinary. That’s precisely the kind of feedback developers should hear!

2 Likes

Depends. If it’s a super frequent action a keyboard shortcut is better. Otherwise a button / widget / whatever.

2 Likes

Sorry, cannot resist. Ctrl-** EMACS all the way :slight_smile:

1 Like

I’m with @lphilpot - depending on the situation I use both

1 Like

I think we all prefer ā€œthe fastest method.ā€
Now let’s think about what’s faster for each of us?. Allocate time to each micro-step…

Shortcuts:

  • I need prior knowledge and to internalize it.
  • I have to search my memory for the combination.
  • My hands have to move, find the keys, and press them.

Mouse clicks:

  • My eyes have to locate the destination point within the interface.
  • My wrist has to move the mouse
  • and finally make N clicks on dropdown menus or buttons.

No one wins here overall. It depends on the specific case.

2 Likes

Some keyboard shortcuts I easily remember and use a lot, but I can only recall my commonly used ones so I like a clickable option as well. I also like how easy it is in GIMP to program keyboard shortcuts, but for some reason I find it not so ā€œintuitiveā€ in darktable

1 Like

The individual preferences are not static.

They change over time as one get to know an application and move from ā€œselection modeā€ where one need to search for and see things to be able to make things happen, towards more of a ā€œcommand modeā€ where we know precisely what action we want performed.

They also may change with the varying intensity the application is used, as repetitions of a certain frequency may be needed to establish the necessary remembrance for various non-visible shortcuts etc.

Software like darktable allow most things to be performed in selection mode by visual elements in the UI, but also have guides in several forms (pop-ups and context sensitive lists) that informs us of the possibilities to speed things up in command mode, plus an extensive system for personal adaption.

Suits me well.

2 Likes

One thing I’ve noticed is that both approaches have their supporters. The problem starts when you don’t use just one application, but several. When you introduce new software, or combine a photo manager with RawTherapee or Darktable, and perhaps a separate culling application, things can quickly become a bit of a command soup in my head!

Configurable keyboard shortcuts would be very useful here. Ideally, you could make different applications use similar shortcuts, creating a more consistent working environment instead of having to remember a different set of commands for every application.

Just my five cents, but I think it would make a real difference for people working across multiple applications.

Not only are there (too) many to remember, they (can) differ between applications. And I’ve had it happen that text I wanted to type in one window went as shortcuts to another (not a good thing in general; at best annoying, at worst…).

That’s where documentation comes in. If you have at least skinned the docs, you might remember there are keyboard shortcuts, and where to find them…
For me, documentation is an integral part of any program. It can vary from a single screen for a simple command line utility to a multi-MB pdf for e.g. C++ with all the librarie functions.

All functionality should be accessible in the GUI, not just with shortcuts. That said, there’s nothing wrong with relegating some obscure functions to, say, a menu bar menu. That way, it’s still discoverable, but won’t clutter up the UI.

A negative example is, for instance, Lightroom’s sharpening mask display. It shows up if you hold Alt while dragging the sharpening slider. That’s not discoverable at all. Technically, the right-click and double-click actions on darktable’s sliders fall in a similar category, but at least these are relatively ordinary UI actions.

Fairly obviously, it also depends on how much I use the software. Six hours every day? Then I know all the keyboard shortcuts. One hour a month? Then I won’t remember the shortcuts, and need the GUI.

1 Like

There are two factors not yet addressed.

The option to configure is essential for accessibility. Not everyone’s physical ability is the same. Not everyone’s hardware is the same either for keyboard, mouse, MIDI device, assistive device, etc. Some keyboards have special keys or multiple modes; others have dead or finicky keys.

Configuration is also handy when there are collisions on the OS level or among applications.