Build
Turn an idea about exam preparation into a coherent product experience: routines, progression and an interface people could understand without a manual.
EdTech · 2025–2026 · Transitioned
Preparly
A gamified exam-preparation platform co-founded with the belief that difficult study routines could feel more structured, immediate and motivating.
What I worked on
I worked across product, UX and engineering—from early prototypes to the infrastructure needed to keep a real product running. The job was rarely a clean hand-off between “design” and “technical”; it was deciding what to simplify, what to build next and what to change once users made the gaps obvious.
Preparly’s learning loop — an editorial representation of the product process, not a reconstructed interface.
Study behaviourA learner needs a reason to return, a clear next step and feedback that is not distracting.
Product iterationPrototype, ship, observe the friction, then redesign the path instead of defending the first idea.
A case study in four verbs
Ship
Carry the product beyond a prototype. The technical work included separate frontend and backend codebases, production deployments, Supabase infrastructure and automated end-to-end testing.
Users
At peak, Preparly reached approximately 5,000 monthly active users. That changed the standard: edge cases, performance and the clarity of a single screen suddenly mattered more than a promising feature list.
Learn
The lasting lesson was not a growth number. It was that product decisions become more interesting—and more accountable—once people depend on what you made.
Case-study material: product screenshots, historical demos and anonymized analytics are retained privately for a visual case study. The source repositories and operational infrastructure are intentionally not linked or exposed here.
/ What carried forward
Preparly made the consequences of product choices visible.
Building for users created a sharper question than “can this work?”: what happens when it does, and people make decisions inside it every day? That question now connects product practice to the reliability work behind Aurels and the research.