[GH-ISSUE #277] Feature: Count keystrokes and mouse clicks #237

New issue

Open

opened 2026-05-05 05:08:48 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:08:48 -06:00

Owner

Originally created by @julianriise on GitHub (Sep 22, 2023).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/277

Having the ability to count clicks and keystrokes and reset the count. This would benefit anyone trying to improve their web app ('How many clicks are needed to order an item?' for example).

Originally created by @julianriise on GitHub (Sep 22, 2023). Original GitHub issue: https://github.com/keycastr/keycastr/issues/277 Having the ability to count clicks and keystrokes and reset the count. This would benefit anyone trying to improve their web app ('How many clicks are needed to order an item?' for example).

gitea-mirror commented

2026-05-05 05:08:50 -06:00

Author

Owner

@akitchen commented on GitHub (Oct 19, 2023):

Sounds like an interesting use case but it's a bit beyond the problem this app helps to solve. Sounds like a use case for a custom visualizer -- contributions are welcome!

@akitchen commented on GitHub (Oct 19, 2023): Sounds like an interesting use case but it's a bit beyond the problem this app helps to solve. Sounds like a use case for a custom visualizer -- contributions are welcome!

gitea-mirror commented

2026-05-05 05:08:52 -06:00

Author

Owner

@jcyh0120 commented on GitHub (Oct 30, 2023):

I got similar use case, too. There are some keystrokes that I'm not familiary with now. A keystroke counting and export to any kind of data format helps improve productivity without having to lookup to documentations in every related applications and manually write down memos.

Here's a proposal:

Add a local file, such as csv, to store statistic data on user's device. Every time a keystroke is triggered displaying on the screen, add a row data to csv with it's keystroke, createdAt, Application(if possible).

The only settting required is enable/disable this feature. That would be super useful to reduce manually counting those keystrokes I forgot and had to lookup the documents again and again and again...

From a nodejs background not able to contribute in a short time. An entry point to the code that trigger the keystroke display on screen gives a boost to test the idea.

@jcyh0120 commented on GitHub (Oct 30, 2023): I got similar use case, too. There are some keystrokes that I'm not familiary with now. A keystroke counting and export to any kind of data format helps improve productivity without having to lookup to documentations in every related applications and manually write down memos. Here's a proposal: Add a local file, such as csv, to store statistic data on user's device. Every time a keystroke is triggered displaying on the screen, add a row data to csv with it's keystroke, createdAt, Application(if possible). The only settting required is enable/disable this feature. That would be super useful to reduce manually counting those keystrokes I forgot and had to lookup the documents again and again and again... From a nodejs background not able to contribute in a short time. An entry point to the code that trigger the keystroke display on screen gives a boost to test the idea.