![]() Instead of fixing the problem for a particular layout or key, users across the globe can set any shortcut to whatever works on their end. Giving these users the ability to change the default shortcuts provides an elegant solution for any keyboard layout. With web apps becoming increasingly complex and replacing desktop applications, complaints about this problem have become a recurring theme in support forums. The reasons are that their keyboard layouts simply do not contain the required keys and that processing key presses with JavaScript is complicated and error-prone. ![]() And because remapping is easy, they can change their shortcuts as their own usage changes and they start using a different subset of features heavily.Įven worse, many software users across the globe are unable to use a good portion of web apps’ keyboard shortcuts on their keyboards. Customizable shortcuts allow users to choose which commands should be shortcut-able based on their own usage. With non-customizable shortcuts, an app is stuck catering to the average user. But some users may use some commands more often than others. Not every command in an app can have a shortcut shortcuts should be reserved for commonly performed actions. ![]() The second issue is one-size-fits-all shortcuts. Giving users the option to change apps’ default bindings enables them to use the same set of shortcuts across the different apps they use professionally, significantly reducing their mental overhead. What often ends up happening is users will learn shortcuts only for the apps they use most often and ignore the others. Even the most advanced users struggle to learn dozens of different keyboard shortcuts for every web app they use. However, as mentioned, in web apps these shortcuts are rarely customizable. A list of keyboard shortcuts frequently takes a prime spot in documentation pages. To the delight of many users, modern web apps are starting to embrace keyboard-driven navigation. This gap can be a serious roadblock for anyone who uses the app a lot and wants to take advantage of shortcuts.Īt CommandBar, we build UX infrastructure for modern apps, we’re uniquely positioned to bring shortcut customization to a massive amount of users across many popular web apps. In contrast to desktop applications, web applications almost never allow users to customize the default bindings. Shortcut customization in the Logic Pro X desktop application That could mean changing a specific shortcut to use a convention we prefer (like G THEN for navigation) or attaching a shortcut to an action we perform a lot that may not have had a default shortcut. Those of us who’ve worked with complex desktop applications are used to being able to edit default keyboard shortcuts to make our workflows as efficient as possible. ![]() It also provides a much-needed solution for international users who often cannot take advantage of default shortcuts engineered for English keyboards. Today, apps using CommandBar can enable their users to change the default keyboard shortcuts for all of their commands, or attach shortcuts to commands that didn’t have any default.Įnabling this feature gives anyone interested in shortcuts the ability to make an app feel like home, customizing shortcuts according to how they use the underlying app. And we still recommend apps set these default shortcuts, since sensible defaults can greatly increase shortcut adoption and usefulness. ![]() This was a great first step in making more apps keyboard-friendly. Previously, CommandBar allowed apps to set default shortcuts for commands. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |