Jepreto Photobooth
Services
SaaS / Web App
Client
Jepreto.com
Year
My Roles
UI/UX Designer
Duration
1 Month
Project Overview
Key Impact / Metric: Translated 3 subjective complaints into a validated, severity-ranked issue list. Identified critical hidden bugs and defined a single source of truth for settings
Jepreto is about pure fun. Builds self-service photobooth software used by independent studios across Indonesia—from elegant wedding booths to many setups event. The client reached out with three suspected UX problems via Google meeting. Instead of treating them as a strict spec, I treated them as hypotheses: observe first, test with real users, then design.
The Problem
Initial Assumption: The client suspected three specific issues: a distracting element during photo capture, no obvious way to retake a shot, and a confusing template editor on the web dashboard.
The Real Problem: Video analysis, observation booth operator and user surveys told a different story. Two of the three "confusing" elements were already clearly labeled. The problem wasn’t missing functionality. It was that people didn’t know what a control did or what would happen when they used it.
As one user put it in a survey: "I thought I could just tap the photo, but there was a specific way to swap positions - so I didn’t get around to trying it."
I mapped out the exact micro-interactions causing the drop-off.
Insight 1 (The Yellow Button Fallacy): The client’s first request was to change a "distracting yellow button." Survey data showed almost nobody saw it as a problem.
Insight 2 (Interaction vs. Feature): Users hesitated over tap versus drag for swapping photos, assuming a feature was missing when it was actually an interaction clarity issue.
The Key
From “missing feature” to “unclear interaction.”
The Why: Clarity over Features. The retake and swap controls already existed. Instead of building a new feature, we added inline help text and a larger preview at the moment of action to resolve the tap vs. drag hesitation.
One path for settings.
The Why: Consistency & User Control. Printer and template settings lived in three different places across the desktop and web apps. We consolidated them into a single source of truth to eliminate confusion.
Say what a feature can’t do.
The Why: Error Prevention. The portrait setting only rotated the preview, not the actual print. We added a clear limitation warning inside the feature before it becomes a costly printing error for a paying customer.
Outcome
Three vague voice-note complaints became a severity-ranked list, prioritizing the two issues confirmed in every method: duplicated settings and unclear retake interactions. Beyond UX, I logged critical bugs (like session resets mid-QR download) for the dev team, and passed product ideas (dual-camera recording) to the roadmap. Jepreto now has the tools to keep validating on their own.
Reflection
It’s tempting to follow the loudest request because it feels decisive. This project reminded me to let a small but representative dataset change my first assumption.
What’s still open is more interesting than what’s solved: customers want sessions as long as possible, while owners want them short. No interface polish fixes that—it’s a business decision for Jepreto to make.
