Birth Control Mobile App

9 weeks | feb - mar, 2020
Evaluative Research
Design Research
We worked with a client from FemTech Collaborative to develop a medical mobile application that helps individuals choose a birth control method that aligns with their reproductive and lifestyle values.
My roles

Evaluative Research, Sketch, User Flow, Information Architecture, UI Design

Meet the team

Karen Escarcha, Carol Ho, Xuehui Zhang

The Objective
Design a mobile app for individuals to choose birth control methods based on their reproductive values and lifestyles
The Outcome
The nuances among all the 18 birth control options can overwhelm individuals when they are trying to make decisions. The process of choosing a birth control method often involves misguided information, and confusion. Without a comprehensive understanding of people's reproductive values can lead to an unsuitable choice for them.
Expert Interview
Our client is the Director of the FemTech Collaborative at University of Pittsburgh, who is creating a suite of digital tools that helps people clarify their reproductive health goals and values, and navigate preference-sensitive decisions. We were able to learn about reproductive oppression, current frustration on decision making of birth control and sterilization, and the importance of reproductive autonomy. We meet with her multiple times to integrate her medical expertises into our design.
Competitor Analysis
In order to understand the available services/functions, languages and visual elements in current birth control tools, we analyzed the following 6 brands of apps, websites, or products. We identified a potential gap that target birth control options only through a friendly and approachable tone.
How might we help individuals choose birth control methods that align with their lifestyle and reproductive values?
Based on the information we gathered from previous research, we created the following 3 personas to help us better understand the “individuals” in our problem statement and guide us through our prototyping phase.
Information Architecture
Client's requirements:
  • Filter methods based on what's important to them
  • A comprehensive view of the methods available
  • Individual methods overviews and details
  • Comparing Methods
Early Wireframe Sketch
We started to brainstorm ideas, and investigated potential features and interfaces based on the assumptions we had so far. Through the process, we critiqued on each other's ideas, and build shared representation. Although many ideas were proven later, through research, not suitable for our design, it is still an important step for our team to reach certain consensus.
Evaluative Research
We drafted the evaluative research protocol and conducted interviews with 2 interviewees: a 18-year-old freshmen female, and a female in her 40s with 3 children.
User Testing Insights
Trustworthiness & Clarity
User were confused about reasons behind asking certain questions. Because our language was relatively more caring and personal compared to a doctor, users were confused on the emotion-oriented language rather than medical professional tone.
Concrete Representation on Reflection & Visual Elements
Open-ended reflection activities were confusing. Users preferred reflection activities with more guidance. Also, some visual element were abstract and hard to understand.
Inclusiveness in Language
The way we ask certain questions could potentially make assumptions on individuals who take the survey, and didn't consider edge cases.
Final Wireframe
Based on the insights from user testing, I modified the questionnaire wireframe:
High Fidelity Mockups
Inclusivity in UX languages
It was great to create a mobile experience that put an emphasis on inclusivity and diverse reproductive values. I learned that written language, not just visual, on interfaces is an essential part of users' experience. Especially for a survey and healthcare experience. In order to consider audience groups with various lifestyle and reproductive values, we kept modifying the languages and the order of the questions, and made sure our questions would not be offensive.