The Problem

Most menstrual tracking apps are built around narrow assumptions: predictable cycles, cisgender users, and a whole lot of pink. They miss the other 75% of the cycle entirely, lock useful features behind paywalls, and often make users feel judged rather than supported. Our team set out to design something better.

Our Research

We conducted 5 in-depth interviews and distributed a survey that received 98 responses from users aged 18–54. Key findings that shaped our design included: users tracking for medical reasons felt apps didn't serve them, inaccurate predictions caused disengagement, and paywalls blocked access to meaningful health data. Users consistently expressed a desire to understand and share their own data on their own terms.

My Contributions

I led the visual design system, building consistent components, selecting typography, and establishing the warm earthy color palette of sage greens and rusty browns. I also designed the home page, symptom logging flows, and recommendations screens, and conducted usability testing that directly informed our final round of iterations.

Interactive Prototype

Click through our high-fidelity Figma prototype.

Design Highlights

Rhythm was built around three core principles. First, personalization over prediction. Users can choose how much structure they want rather than being forced into a fixed cycle model. Second, fast and nonjudgmental symptom logging with clear iconography and no unnecessary friction. Third, holistic tracking that acknowledges mood, nutrition, sleep, and activity as part of reproductive health, not separate from it.

The visual identity deliberately broke from the stereotypical pink aesthetic of most cycle apps. We used a warm, nature-inspired palette and gender-neutral language throughout to make the app welcoming to users of all gender identities.

Iterative Process

We moved through individual sketches, cognitive walkthroughs, mid-fidelity wireframes, and two rounds of usability testing before arriving at our final prototype. Testing revealed navigation issues — users couldn't find settings, back buttons led to wrong pages, and some graph labels were unclear. Each round of feedback directly shaped the next version, resulting in a significantly more intuitive final prototype.

What I Learned

This project taught me how much user research shapes good design - every major decision traced back to something a real person told us. I also learned how to balance a large feature set with simplicity by making things optional and toggleable rather than forcing complexity on all users. And I got a lot of practice running and responding to usability tests, which is now one of my favorite parts of the design process.