You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Monkeytype for a daily 30-minute training routine using Master difficulty and Confidence mode. Because these modes result in an immediate "fail" upon an error, I would like a way to track my daily success rate and session volume more effectively.
Proposed Feature
I would like to see a "Session Summary" or "Daily Goals" dashboard that tracks:
Total Tests Taken: Including both completed and failed/aborted tests.
Success Rate: The percentage of tests "Passed" (reached the end) vs. "Failed" (stopped due to Master/Confidence mode triggers).
WPM Floor Filter: The ability to set a custom WPM target (e.g., 50 WPM). If a test is completed but falls below this WPM, it counts as a "fail" for the session statistics.
Why this would be useful
For users doing high-stakes practice, raw WPM isn't the only metric that matters—consistency is key. Knowing that I had an 80% success rate over 50 tests today is a different and valuable way to measure progress compared to just looking at a peak WPM graph.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am using Monkeytype for a daily 30-minute training routine using Master difficulty and Confidence mode. Because these modes result in an immediate "fail" upon an error, I would like a way to track my daily success rate and session volume more effectively.
Proposed Feature
I would like to see a "Session Summary" or "Daily Goals" dashboard that tracks:
Total Tests Taken: Including both completed and failed/aborted tests.
Success Rate: The percentage of tests "Passed" (reached the end) vs. "Failed" (stopped due to Master/Confidence mode triggers).
WPM Floor Filter: The ability to set a custom WPM target (e.g., 50 WPM). If a test is completed but falls below this WPM, it counts as a "fail" for the session statistics.
Why this would be useful
For users doing high-stakes practice, raw WPM isn't the only metric that matters—consistency is key. Knowing that I had an 80% success rate over 50 tests today is a different and valuable way to measure progress compared to just looking at a peak WPM graph.
Beta Was this translation helpful? Give feedback.
All reactions