Collapse Key Mappings

[githubsterer]

Developer TODO (don't remove)

• update documentation
  The home screen should display just the key mappings in collapsed form to make it easier to find and manage (or at least have that option) displaying just the user given name and the trigger, hiding the actions and options. Small up and down arrow to the side would control.

[jambl3r]

The key maps in general are becoming more compact. Here is a before and after of the same key map.

Key Mapper 2

Upcoming Key Mapper 3

[githubsterer]

I think that looks great but still presents the same issue when scrolling through many of them.

Imagine only having the area showing look something like one of these small boxes below, with a title and also a small down arrow to the right side you press to expand the window downward full size, that is replaced by an up arrow to collapse it again.

You can then choose to keep one or more expanded like that or collapsed, as you wish. When you scroll through 20 of them it would make a huge difference.

[jambl3r]

I'll draw up a prototype of this and see what the reception is

[githubsterer]

After adding the necessary constraints for media and phone, this is how long the scrolling list becomes for just 8 key maps, where it is already too cluttered to visually distinguish them easily. Don't get me wrong, the layout of each key map box looks great, it's just that all the detail should be collapsible when desired.

[githubsterer]

This is how it would look (crude mock-up) with each of them collapsed to just show enough space to display their user named titles:

[jambl3r]

After some lengthy discussions, we are closing this as not planned.
There are three main reasons for this:

The first reason is that naming key maps is probably a symptom of a larger problem. The upcoming groups feature #320 allows for improved organisation by putting key maps into named folders. For users who have very large lists of key maps in those folders, we propose a search/filter function #670, where you can just filter for what you want and only the matching key maps will remain.

The second reason is that there is a long established paradigm of tapping on key maps to edit them, and long pressing them to select, delete, copy etc. If key maps were named #701 and collapsible #1486, then tapping key maps would realistically have to expand/collapse them and the simple tap functionality would be lost. We feel that this is overall damaging to the user experience and adds bloat to the UI.

The third reason is that naming key maps is a burden that we expect many users will find annoying. If a key map was not named then it would likely be given a placeholder, which takes up room on the UI that doesn't serve a good purpose. Key maps already have visual defining features: the summary in the box that identifies what the key map does.

Apologies for not meeting this request but it is in the interest of delivering better organisation and a lean user experience that is optimized for the use cases that a majority of our users have.

I encourage you to check out #320 and #670 which we hope will work to solve the underlying organisation difficulties that this issue has expressed.