ClassBoard

Inspiration

My mom is a mathematics teacher at an academy, and I noticed there are only a few apps available with a clean and simple UI—and none of them are free. This inspired me to build ClassBoard, a teacher-focused scheduler and classroom management app.

What it does

ClassBoard is a scheduler and record-keeping app designed specifically for teachers. It allows teachers to:

Manage classes – create classes by grade, add titles/descriptions, and schedule them in a calendar with detailed checklists and student lists.

Track attendance & behavior – mark student attendance, record absence reasons, and note classroom behavior.

Schedule meetings – manage meetings with students, parents, or other teachers, with future potential to record transcripts and generate AI summaries.

Maintain student records – track student abilities, attendance, test results, notes, and parent contact information.

Handle tests – link tests to classes, record scores or absences, calculate averages, and add notes.

How I built it

I started with a frontend UI repo and worked with Kiro to restructure the frontend code for scalability. Using a spec-driven approach, Kiro helped me plan and generate the backend (API, database, infrastructure) based on my preferred stack.

I used agent hooks like auto-install dependencies, import cleanup, and document setup to save time and keep the repo clean.

The frontend and backend were integrated step by step, and I deployed the final working version on my own.

Challenges I ran into

One of the biggest challenges was integrating the frontend with the backend. Many routes initially returned errors, and debugging imports across multiple components took significant effort. Using Kiro’s cleanup hooks helped fix many of these issues.

Accomplishments that I am proud of

Successfully deploying the app by myself.

Completing a working version of ClassBoard with no errors.

Building both frontend and backend from scratch while keeping the structure clean and scalable.

What I learned

I learned the importance of incremental development and testing. By validating each component as soon as it was built, I caught integration issues early and avoided large-scale debugging later.

What's next for ClassBoard

The next step is to implement a signup feature for registered customers, so that teachers can securely access their own classes, student records, and schedules. This will allow the app to support multiple users while keeping each teacher’s data private. Longer-term, I’d also like to explore AI features, such as auto-generating meeting summaries from transcripts and integrate with aws later.

Built With

• express.js
• node.js
• postgresql
• railway
• react
• tailwind
• terraform
• typescript
• vercel
• vite