jah-on / cifrot Goto Github PK

as a hearing user wearing bluetooth headphones, I gave this a try and noticed that, because i was able to hear the tones until they were rather quiet (i.e. low y values), i would sometimes click the spacebar too late and it would register the input for the next tone. (that is at least until i got bored a few frequencies in and started spamming the spacebar as you can see in the data haha)

I feel like it might help produce better data if the app waits for user input before moving onto the next tone

Seems like a cool app though! might also make for a fun tool for hearing users to compare different pairs of headphones and things like that with a little more empirical rigor than just subjective listening

Allow the user to use the standard musical note system of increments in places of frequencies and display them on the chart.

After my own experience playing around with the app (see #4) it seems as though these tests are designed to take a lot more time than I was expecting them to. Maybe people who are actually trying to test their listening devices have more attention span than I do, but I feel like it might be nice if the app gave users a sense of how long the tests are meant to take.

Some ideas:

• maybe change the wording on the directions to include some sense of scale (it says "The default is 200 Hz but you can set it between 1 and 1,000. The higher the value, the faster but less accurate the test will be." but having a few points that can be used to estimate the time - like saying that "a 200 Hz test will take about Y minutes to complete per ear/per run .etc" might help
• maybe adding a dropdown where users can select how long they have (i.e. 5/10/15 min test or short/medium/long) using presets, (with an option to specify the frequency interval manually as an extra/advanced option)

Tested both on dark mode and light mode