Architect & Developer
Opticampus School
The daily life of schools: attendance, grades, parents, fees.
01
The need
The school didn't need another brochure. The day already overflows: who is in class, which grades land, what parents should know, what the fees desk takes in.
When those gestures live in notebooks and scattered files, the day comes apart. It needed one place, where the team finds the class without hunting for it.
02
What the product carries
Four things, held in the same place. Attendance. Grades. The link with parents. Fees. Nothing decorative: these are the gestures people use from morning until close.
The product doesn't narrate the school. It runs it. Every screen has to stay obvious for someone who has no time to be trained.
03
How I set it down
I held the architecture and the build. React in front, so the screen stays clear when tasks follow one another. Django behind, so the school's data stays ordered, consistent, and ready to grow without hitting a ceiling.
The aim was not a mockup to present. It was a tool the teams open, and no longer have to work around.
04
Where it stands
The project is in production. The teams use it. It didn't stay a demonstration: the school day goes through it.
We trusted him with the daily life of the school: attendance, grades, parents, fees. It didn't stay a mockup. The teams use it.