Behind Locker
Meet the Creator
Locker started with a simple idea: school software should make life easier for the people actually using it.
Rajveer
Founder & Developer
The story
It started as a problem I actually had.
Locker began as a student project, not a business plan. School communication is scattered by default — homework lives in one group chat, project teams in another, and whatever you actually accomplished outside class rarely gets tracked anywhere at all. I got tired of that, so I started building something to fix it.
The first version was built for students, because that's the side of school I actually understood. As real people started using it, the product changed — not because of a roadmap, but because of what people actually said, asked for, and stopped using.
Locker is now growing to support teachers and schools too — but the goal hasn't changed. Schools already run on ERPs for attendance and official records, and Locker isn't trying to replace that. It's trying to be the layer where the actual people in a school — students and teachers — collaborate, without turning into another bloated system someone has to maintain.
The journey so far
Built one real step at a time.
- 1
Idea
Noticing how scattered school life actually was — homework, groups, and achievements all living in different places, none of them talking to each other.
- 2
First prototype
A simple shared space for one class. Homework and a marketplace, nothing more — just enough to see if the idea actually held up.
- 3
Student platform
Groups, achievements, rewards. Built around one question: would a student actually open this again tomorrow?
- 4
Real user feedback
Real students meant real opinions. Some ideas got cut, some features only exist because someone specifically asked for them.
- 5
School + teacher platform
Roles for teachers and Principals/IT Admins, real class ownership, parent-teacher meetings — the same platform learning to speak to a whole school, not just one class.
- 6
Continuous development
Still being built, still changing based on what people actually use — this page will look outdated the moment it stops.
Lessons
What building this has actually taught me.
A real product isn't a demo
Handling real accounts and real data is a different job than shipping something that just works once in a demo.
Feedback changes direction, not just details
Some of the most useful parts of Locker exist because a real user asked for exactly that, not because it was planned.
Performance is a feature
A slow page feels broken even when nothing is actually wrong with it. Speed isn't a nice-to-have, it's part of the product.
Simple beats more
Adding a feature is easy. Deciding what not to build is harder — and usually matters more.
Schools aren't one audience
A student, a teacher, and a Principal/IT Admin want genuinely different things from the same app. Designing for all three at once is the actual hard part.
Solve the real problem first
It's tempting to keep adding before the core thing even works well. The boring, unglamorous stuff has to come first.
Why I'm building this
Why Locker exists.
Less scattered communication. Less repetitive work. Better collaboration between students and teachers. Simpler workflows, not more of them. That's the whole point — a school already has enough systems. Locker is meant to be the one that actually makes the people in it feel less alone in getting things done.