Hooowrite

Typing page
Waiting page
Landing page

Inspiration 💡

There is a skill that everyone should have in this day and age. That ability is quick typing. Typing is no longer limited to data entry specialists or clerics. It is now mandatory for everyone to learn this skill. Everyone uses a computer or laptop, or even a smartphone with a keyboard. Whether for chatting, working, or simply browsing the internet. Being unable to type quickly makes such tasks frustrating and irritating. That is why everyone should learn to type quickly. However, keep in mind that, like any other skill, learning how to type quickly can take days, weeks, or even months of practice. If your job requires you to sit in front of a computer all day, having fast and good typing skills will be of the utmost importance.

Our main inspiration is that we want to improve developers, software engineers, and coders' typing skills by actually writing code. Most websites prepare you with plain English but we want to have a developer-specific typing test.

What it does ⚙️

It's a nicely made web app that has some programming languages to choose from and also a time limit where users can type and see how they do in that specific language. It also helps them to increase their speed as it is made for programmers. It has a real actually syntax and not just a bunch of words. Screenshot 2022-09-18 131151

How we built it💻

Keystroke dynamics, or typing dynamics, is the obtaining of detailed timing information that describes exactly when each key was pressed and when it was released as a person is typing at a computer keyboard for biometric identification, similar to speaker recognition. Data needed to analyze keystroke dynamics is obtained by keystroke logging.

Challenges we ran into 🙆

The main challenge that we spent 80% of our time was fixing the bugs that we haven't thought we would face. The first is implementing the logic using the javascript keywords index and matching it with the right time. The second issue was when we tried to implement the quiz to stop right after the sentence is done rather than wait until the timer stops.

The third issue was, as 2(50%) of our members were entirely new to hackathons, one coming from a high school background, it was hard to collab and have a common ground. It took us a while to get acquainted and work seamlessly.

Accomplishments that we're proud of 🏆

50% or 2 of our members were first-time hackers and they are happy that they made our debut at Impratcial hackers. We are happy we made everything from the ground up and try to come up with features that we see are missing from other typing test websites. The main key takeout that we learned from this hackathon is that we learned a lot about react hooks, states, and props in a very new way. Even though it was front-end heavy, it was the toughest logic we have implemented so far.

What we learned 📚

We thought this problem was an easy task but by implementing it we learned a lot about the use state and use effect a lot. We have used them extensively. We learned to use the

What's next for ✈️

We currently support java, javascript, and python however we want to add more languages like C, C++, Go, and many more. The other main thing we didn't implement is storing the scores in our database and we want to do that next and have a nice backend.