-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frontend Memo #10
Labels
scope: frontend
Regarding the frontend side
Comments
@elianiva jangan lupa, endpoint buat secret page yang kemarin. isinya list data yang bisa di download + nama user nya |
oh yeah. and a give up button. see https://t.me/c/1691679327/21713 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Data Collection Checklist
Keyboard
Timing Features
The duration of user.
How long a user doesn't do anything.
Typing Features
We can calculate the user's WPM. Average person usually types around 40-60WPM.
The duration of a user holding down the same key. The way we calculate this is by sending a keypress event with its timestamp (ms) to the backend.
How fast the user presses the backspace button.
The duration between the start of keypress and response.
These are the keys that are probably unrelated to the coding question. Possible keys are:
any keys outside the editor
F keys (F1-F12)
emit from frontend
Video
A plain simple video, no need for face tracking or fancy stuff.
using WebRTCMouse
We could probably reuse some logic from https://codepen.io/ronnygunawan/pen/wvrojXg
Movement Features
Calculate total movement.
Average movement. How fast a mouse moving from point A to B.
Mouse acceleration. How fast the acceleration when moving the cursor.
Amount of pauses between mouse movement. We'll store how many times a user pauses every 3s, 5s, and 10s.
Click Features
How many time the user clicks the cursor.
How long the user holds the mouse click.
Scroll Features
How many times the user scrolls the page.
How far the user scrolls the page.
How fast the user scrolls.
Pages Checklist
This page is going to be used for the user's form. A simple form with multiple input fields.
This page is where the user will spend most of their time. It consists of 6 pages where each page contains one coding problem they needed to solve. We'd do most of the tracking here.
This page contains several options that the user can choose to determine how they feel before and after the test.
This page is used after the user has done the test. We want this because it gives the user some sort of a reward after doing the test.
Misc Features Checklist
doesn't have the balls to continue the testwants to give upThe text was updated successfully, but these errors were encountered: