BabyDex
| Role | Founder / Product Designer. Solo project: I owned the concept, the visual direction, the build, and the public launch. |
|---|---|
| Context | BabyDex, a baby milestone tracker that reframes logging as collecting: babies level up and learn moves as they hit milestones, in the spirit of a Pokédex. |
| Users | New parents, and the family and friends they share milestones with. |
| Timeframe | Personal project, self-directed. |
| What I owned | Concept and positioning, the core mechanic, the retro pixel visual direction, the AI-assisted design and build, and the launch at babydex.es. |
| Status | Live and public at babydex.es. Early stage, gathering first real usage. |
The idea
BabyDex started as a joke with friends. Watching a baby hit a new milestone felt like a little creature evolving or learning a new move, and the idea of collecting those moments like a Pokédex stuck. Logging the milestone and showing it off became one act instead of two.
I kept it playful on purpose. The product is milestone cards you log and share, with a retro pixel look. Most trackers I had seen present logging as a form: date, description, done. I wanted the sharing moment to feel like the point, not the admin after it.
My role
Solo project, so every decision was mine: the concept, the core mechanic, the visual direction, the build, and the launch.
- Concept and positioning: milestone logging as collecting and sharing.
- Visual direction: trials of retro pixel colour palettes, with the final direction chosen with AI help.
- Build and launch: AI assisted the concept, the design, and the build, and the site went public at babydex.es.
Outcome
BabyDex is live and public at babydex.es. That is the honest claim: it shipped. It has not been validated with users, and I have not measured whether families actually use it or pass it around. The sharing framing is still a hypothesis.
Reflection
Working solo removed the usual excuses. There was no stakeholder to wait on and no team to blame, just decisions and their consequences. The rule I set was that good enough to show counted as the design constraint, not the compromise, and that is what got it out the door. The next real test is whether parents want to share milestones this way at all.
Methodology grounding: Playful concept development; AI-assisted design and build; live public launch.