A Photobooth of Our Own
Mar 2025 · 2 min read
Our school was already using photobooth software when I decided to build one. I wanted us to have a tool we could control and use for free, so after finishing Grade 11, I started working on OdizeeBooth.
Before Grade 12 classes began, a classmate brought me into the Odizee Student Council, or OSC, as an officer. I proposed using the photobooth, and we used it during Balik Eskwela.
That gave the project a specific job. We needed to run a booth where students could have their photos taken and leave with a printed strip. The software would be part of a setup that we had to prepare and operate ourselves.
Getting the booth ready
Finalizing OdizeeBooth was one of the hardest parts. I tried a lot of features, and some of them didn't work. Automatic printing was one of those features, so during the event, we printed manually.
Preparing the physical setup also took work. I had to think about how we would actually run the booth alongside getting the software ready.
At the same time, I still had schoolwork to do and documentation duties for that same school event. Building the system was one responsibility among several that I was trying to manage. Getting it ready meant fitting the development work around those other responsibilities.
Running it at Balik Eskwela
Students came into our booth and got ready for their photos. I operated the software, while an extended monitor in front of them let them see the screen.
Then we captured their photos, printed, and handed them their strips. They could get their printed strip within a minute.
The event went well, even with the manual printing step. We were able to use the system for the booth, but there was still work for us to handle around it. Automatic printing was a clear example: I had tried to make that part easier, and the team still had to do it manually.
Looking back, that is the most important lesson I took from the project. A tool like this needs to help the people running it and reduce the work they have to do. Trying features is part of building, but I also need to ask whether the result actually solves the problem I started with.
From OdizeeBooth to Kisap
After graduating, I opened the project to people beyond our school and renamed it Kisap. I wanted a broader identity for something people could use on the internet, while allowing the school to keep using it too.
OdizeeBooth began with a need I could see around me. Kisap grew out of that same project, with a wider audience in mind.
The lesson I want to carry into my next projects is to stay close to the problem. If I'm building something to help with a task, I need to pay attention to the work people still have to do when they use it. The result should make that task easier for them.