Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add metric to help assess awareness of key binding customizability #94
Description of the Change
Building on the effort kicked off in #90, this pull request continues our quest to better understand the awareness and approachability of Atom's "hackability."
Atom's hackability comes in multiple forms, but for many users, custom keyboard shortcuts will be the first thing they look for. The Flight Manual describes the steps for defining custom keyboard shortcuts, but we don't currently have a way of knowing whether that translates into users actually setting up custom keyboard shortcuts. To assess the awareness and approachability of defining custom keyboard shortcuts, this pull request adds a metric to report the number of user-defined key bindings that are present.
Equipped with this information, we'll be able to assess the effectiveness of our efforts to increase the awareness and approachability of keyboard shortcut customization. For example, does describing custom keyboard shortcuts in the welcome guide increase or decrease the percentage of users that define custom keyboard shortcuts?
Implementation-wise, this pull request sends an event that reports the quantity of user-defined key bindings that get loaded at Atom startup.
Instead of reporting this metric at startup, we could report it each time a user adds, removes, or changes a user-defined key binding. Doing so would require that we subscribe to the
The screenshot below shows the metrics resulting from my testing.
You can view metrics by various dimensions, and this particular view shows the average number of user-defined key bindings loaded by Atom version. In a VM running Atom 1.30.dev-2f827bf, you can see that I have no user-defined key bindings. And on my main dev machine running Atom 1.30.0-nightly2, you can see that I have 29 user-defined key bindings.