WadiClasses

The carving algorithm to set how important an assignment or a quiz is. (Carving more from the original schedule block means more important)

Inspiration

Personally, I've always felt a bit disconnected from the way we usually get notified about assignments, quizzes, and so on. The idea came to me when we had a quiz in a hard subject that my friend didn't know about, because that class didn't have a WhatsApp group. He didn't do as well as he'd hoped.

What it does

Our web app lets class reps create a class. They can also add sections to it, since some classes have both a lecture and a practical side. When a class rep creates a class, a code is generated that they can share with their classmates. Entering the code once adds that class's schedule to yours. From then on, whenever the class rep adds a quiz or an assignment, it shows up for everyone who used that code.

How we built it

Since we're a team, we divided the work. One teammate researched what existing apps already do, and another did a feasibility study on what we could realistically add. Then we got together to share how we each pictured the app, and once we agreed, we made an Excalidraw sketch to share the styles we had in mind.

Working back and forth with an AI agent is mostly suited to a single developer, so one of us took on building the app, while making sure to include the whole team's ideas and vision

Challenges we ran into

It was our first time working with a coding agent, and describing the visuals and design to it was a lot harder than we expected.

Displaying assignments and quizzes on the schedule was also implemented poorly at first. The quiz or assignment label would take up part of the class's space, so it ended up covering the course name.

Accomplishments that we're proud of

We're proud that we turned an idea into something we can interact with. Even though it's only a prototype, it was great to see what we had written on paper become a program we can run and use.

What we learned

We learned how to communicate clearly and quickly as a team. Within two days, we completed a research gap analysis and a feasibility study, divided the work, and shared our files.

From working with the coding agent, we learned about file structures and project management. And after going through several rounds of design, we learned how to explain our design choices more clearly.