Teacher Dashboard UI
Landing Page
Student UI (after pressing button)
Student UI

Inspiration

Tune In: Know when your class tunes out.

We've all been in a lecture where the professor asks, “Does everyone understand?” and the room stays completely silent. You could assume that half the class is probably lost.

Instead of waiting for students to speak up, Tune In lets professors see when they're losing the room so they can get everyone back on the same wavelength.

What it does

Tune In gives students an anonymous way to signal the moment they stop following. With one tap on their phone, they send a real-time signal to the professor's dashboard, where confusion across the classroom is monitored live.

How we built it FINISH

We built the front end in React and used Vite to run and bundle it. There is no custom back end: the app connects directly from the browser to a Supabase Postgres database, which stores each student tap and uses Supabase Realtime to push it to the professor's dashboard instantly.

Challenges we ran into

LLMs coding most of the project and handling all of the code, and use handling editing the code using the LLM made debugging trickier because we became really dependent on the LLM to fix bugs because we didn't write 99% of the code personally and because of that we don't understand the code or business logic well enough to personally debug it.

Another challenge was having our team work on macs and windows made some of the lower level logic not work on the other machines. I.E I built a beautiful bash script that worked on my Linux machine to configure out environments but it didn't work on the windows machine and I would've needed to create a equivalent power shell script or something (Idk bruh. I HATE windows. I also hate qbasic and MSDOS but thats a story for another day. I think the real moral of the story is I have beef with Microsoft especially so after this one bloke called me from there asking me for my social security and the name of my first pet and the street I grew up on. Coincidentally, my bank account was emptied the next day. I don't know if these events are correlated but I blame them for my misery. CURSE YOU BILL GATES الله يخرب بيتك )

Another challenge we ran into was simple logistics. We had never done a hackathon before and it took us a bit to get going as far as picking an idea that we could bring to a MVP state in 24 hours. That was stressful. We got lucky that we chose a simple idea but if we would've picked one of the more challenging ideas we had in our list of ideas we might not have a MVP to present.

Accomplishments that we're proud of

We built a full fledged app and brought an idea from our minds into a tangible product in 24 hours. That is so badass.

What we learned

We learned how easy it is to develop a idea and use a LLM to develop it, we also learned the limitations of Vibe Coding in that you lose a lot of the agency and dexterity over the code you have when you code all of it yourself.

What's next for Tune In

It would be nice to actually go through and understand what all of our code does for starters. Later on add multithreading through C++ POSIX threads not cuz its particularly useful but because it would help me understand threads in C/C++. Another thing is to actually develop and publish a web and app version. "MOVE OFF OF LOCAL HOST!!!" as all the SF techie Y-Combinator ppl like to say. Perhaps have a way to integrate into a whiteboard or canvas or something; find the best medium to make our simple app accessible to students and professors.

If somebody wants to pay us for this software, we'll further develop it and make it robust and sell it to you wink wink nudge nudge.