Being that we are all students in the final year of secondary school, we’ve seen what teachers have to go through (at least in our area) to deal with Covid-19. Just focusing on keeping track of students is a headache in and of itself. This is fundamental to preventing spread of Covid-19 as they need to be aware of who has been in contact with who. As of right now, it is done through—hundreds of—paper logs filled in by the students as they leave or enter the classroom. The times that are filled in are inaccurate, and the students are required to fill out a physical log (leading to contact).

Instead, we believed a modern approach where students can fill out these logs electronically would be safer and more efficient. They could track the times more precisely and would allow the administrators to easily store and view the logs without sifting through hundreds of physical logs. We thought that only applying this to schools would be silly, so generalizing it to workplaces and other areas was a natural step.

What it does

It is designed not to just help teachers, but other workplace administrators as well. It is a convenient tool to help track where people are going, and at a precise time. While useful as a general tool, it is also particularly useful today with dealing with Covid-19. When the inevitable does happen and someone in the administration catches it, TrackerInout allows the administrator to effectively see the activity of this individual. It is then much easier to quickly see who could have reasonably come into contact.

In terms of functionality, our project allows administrators to sign in using Google. They can then create a room (using a code). Anyone with such code and sign in and out, sending a log including the time, reason, and direction to the administrator.

How we built it

For this project, we started by coding in HTML, CSS, JavaScript, and Firebase for backend.

Challenges we ran into

As none of us were experienced with Firebase, it required a lot of effort and time to learn the necessary tools to keep the site running smoothly. This ate a lot of our time and required us to work faster for the remainder of this hackathon.

We were only able to get the login function to work when signing in with Google. We also created a quick UI so that we could focus on the backend, and learn how to write and read from the database using JavaScript.

Accomplishments that we're proud of

As this is the first hackathon for all the members of our team, we did not know what t expect coming into this challenge. We are all also relatively new to backend programming. We are extremely proud of being able to learn how to use firebase to an extent within 12 hours, and then be able to read that data.

What's next for TrackInOut

Because Google is so ubiquitous, having a sign in with Google option is convenient. However, we would like to implement a feature where administrators can log in using any type of email, allowing a better varied login experience.

Other features include different tools to help administrators view the logs. We would like to implement a search feature that allows administrators to see all the logs for a particular person. This could help check who they’ve been in contact with, or if they’ve been taking too much break time. A feature that allows them to download the logs in an excel or google spreadsheet format would also allow them to effectively view their logs independently.

Because time was so short, we didn’t get to create the clean design we wanted to. This would be a natural step to include as we work on the site in the future. optimization of backend

+ 2 more
Share this project: