Problem

Fundamental Access Barriers 🚫

  • 37% of women worldwide lack internet access
  • 2.7 billion women cannot access digital health tools
  • 496 million women are illiterate
  • 129 million girls are not in school
  • 1 in 3 women face gender-based technology restrictions

Safety and Cultural Concerns ⚠️

  • Phone sharing common in many households exposes private health queries
  • Male family members often monitor device usage
  • Health topics considered taboo in many cultures
  • Women often lack privacy for health inquiries
  • Digital footprints can put women at risk in restrictive societies

Economic Barriers 🚫

  • Average woman in developing countries earns 50% less than men
  • Mobile data costs can exceed 20% of monthly income
  • Device ownership often controlled by male family members
  • Healthcare decisions often require male approval
  • Limited access to banking/payment systems

Inspiration

Access to quality healthcare information is a critical issue faced by women and girls worldwide, especially in underserved communities. Many face barriers like lack of internet access, illiteracy, cultural taboos, and economic constraints that prevent them from getting the support they need. We were inspired to build a solution that could overcome these challenges and empower women and girls to proactively manage their health.

What it does

Poppy is a multilingual health assistant designed to provide accessible, private, and culturally-sensitive healthcare guidance. It uses a conversational, voice-first interface to gather user symptoms and generate personalized decision trees and wellness recommendations. Poppy leverages offline capabilities, community partnerships, and privacy-preserving features to ensure safe and equitable access, even in resource-constrained settings.

How we built it

Poppy was built using a modular, extensible Python architecture that allows for easy integration of new interfaces, data sources, and contextual adaptations. The core functionality includes:

  • Culturally-sensitive content generation using the Gemini API
  • Localized language support and dialect adaptation
  • Privacy-preserving data handling with encryption and quick-delete features
  • Integration with community health workers and women's support networks
  • [TODO] Voice-based interaction using IVR and speech recognition
  • [TODO] - Offline-first design

Challenges we ran into

Some of the key challenges we faced in building Poppy included:

  1. Accessibility barriers: Ensuring the application was truly accessible for women and girls with limited literacy, technology access, and cultural constraints.
  2. Privacy and safety concerns: Designing features that protected user privacy and security, especially for sensitive health topics.
  3. Lack of localized data: Integrating regional health practices, terminology, and cultural norms to make the solution relevant and trusted.
  4. Bandwidth and device limitations: Optimizing the application for low-bandwidth environments and feature phone usage.
  5. Sustainable distribution: Developing a model for distributing and maintaining the application in resource-constrained communities.

Accomplishments that we're proud of

We're proud of several key accomplishments in building Poppy:

  1. Culturally-adaptive design: The application integrates local health knowledge, language support, and gender-sensitive features to ensure cultural relevance and safety.
  2. Privacy-first approach: Poppy incorporates privacy-preserving data handling, quick-exit functionality, and emergency response features to protect user security.
  3. Sustainable distribution model: The solution leverages community partnerships, local health workers, and low-cost distribution channels to ensure long-term availability and maintenance.

What we learned

Through the development of Poppy, we gained several valuable insights:

  1. Importance of intersectional design: Healthcare technology solutions must consider the unique needs and constraints of marginalized communities, especially women and girls.
  2. Power of local community integration: Partnering with community organizations, health workers, and women's groups is crucial for building trust and ensuring relevance.
  3. Challenges of data and content localization: Adapting health information to diverse cultural contexts requires significant research and effort, but is essential for effective solutions.
  4. Significance of privacy and safety: Prioritizing user privacy and security, especially for sensitive health topics, is non-negotiable for building inclusive and trustworthy applications.

What's next

Moving forward, we have several key priorities for the Poppy project:

  1. Expand access channels: Integrate additional distribution methods like radio programs, print materials, and community mesh networks.
  2. Enhance privacy and safety features: Strengthen the quick-exit functionality, emergency response system, and data protection mechanisms.
  3. Deepen community partnerships: Collaborate with more women's groups, health workers, and local leaders to ensure Poppy meets the unique needs of each region.
  4. Develop advanced health guidance: Incorporate reproductive health, maternal care, and gender-specific symptom tracking to provide more comprehensive support.
  5. Implement sustainable monetization: Explore revenue models like sponsorships, government/NGO partnerships, and user contributions to ensure long-term viability.

Built With

  • Python
  • Google Generative AI (Gemini)
  • Rich (console library)
  • SQLite
  • Asyncio
  • Dataclasses
  • Enum
  • Typing
  • JSON

Built With

Share this project:

Updates