Loading...
Two years of building a school management platform for Nepal taught us more about real-world software than any tutorial. Lessons on offline-first design, Nepali dates, and listening to users.
When we started building Vidyasetu, our school management platform, we assumed the hard part would be the code. We were wrong. The hard part was understanding how a school in rural Nepal actually works.
The first lesson was connectivity. Many schools have unreliable internet, so the system had to work when the connection dropped and sync when it came back. Features that assumed always-online simply didn't survive first contact with a real school.
The second lesson was the Nepali calendar. Attendance, exams, and fees all run on Bikram Sambat dates. A system that only understood the Gregorian calendar was useless for a headteacher planning the academic year. We built BS date support into the core, not as an afterthought.
The third lesson was the most important: sit with the users. We spent days in schools watching how attendance is actually taken, how fees are collected in cash, how exam results move from paper to report card. Every workflow in Vidyasetu maps to something a real person does, not something a textbook says they should do.
Today Vidyasetu runs in schools across the far west, handling attendance, exams, fees, and reports. The code matters, but what made it work was humility — building for the user in front of us, not the user we imagined.
If you're building software for Nepal, start by visiting the people who'll use it. The requirements document writes itself after that.
