Skip to content
Contact

Case studies / Myra · Jan 2025 – 2026

She controls what they see

Myra was a women's-health concept for Nepal. I led it as founder and designer. A 171-response, two-sided survey moved it from a broad AI-health pitch to one testable question: consent-first sharing with a partner or family member. 3rd at Hult Prize at Kathmandu University 2025; first prize at Project YuwaXcel 2026.

ResearchPrivacyHealthConcept, paused · 2026

Role

Founder, UI/UX design, brand and marketing, web frontend

Timeline

Jan 2025 – 2026

Team

Three student co-founders (research and healthcare strategy, technical, data)

Platform

Concept (mobile), landing and launch sites

Not mine

No mobile app was built; the questionnaire was written with the team

Measured outcome

None measured (no app released)

the key decision

She shares interpretations, never raw logs: every grant starts off, is chosen item by item, and can be stopped without the other person being told why.

how deep do you want to go?

Research lead
Diagram from the case study. Product screenshots are being added.
That's the brief. Switch to Story for the full argument, or Deep for states, iterations and implementation.
Chapter 01

Support, without losing control

In early 2025, Myra was a student pitch for a women's-health app in Nepal. It promised a lot: AI cycle prediction, risk flags for conditions, lab testing and a donation portal. It also had one idea that nobody on the team could answer from our own experience:

Would a woman let a partner or family member follow her cycle, and on whose terms?

The idea was called Companion Mode. A boyfriend, mother or sister could learn when she might need rest, and help. The question was whether that would feel like support or like surveillance, in a place where many young women are still restricted during their period, and where a phone is often picked up by other people in the house.

We ran a survey to find out. 171 people answered, in two branches: women answered about sharing, and men answered about following. The answers turned the product from a broad pitch into one narrow, testable claim:

This is the research lead of my portfolio. Myra is a paused concept. No app was released, and nothing here was tested with users. What I can show is how the evidence changed the design, and where the evidence stops.

Chapter 02

What Myra was, and what it is not

My role

I started Myra and led it as founder, with three student co-founders: a biotechnology student who worked on research synthesis and healthcare strategy, and two computer-engineering students on the technical and data side.

I didThe idea; product and UI/UX design, including the 2026 pitch concept screens (Figma "Myra – Final"); brand; marketing and survey outreach; the 2025 landing-page design; the 2026 launch site, mostly built by hand
With the teamThe questionnaire, the pitches
Nobody didA mobile app, a usability test, a clinical review
StatusConcept, paused in 2026

From a bundle to one question

The 2025 pitch bundled five businesses into one product. By 2026 we had narrowed it to a staged companion, with a core that the survey actually supports.

2025 · EARLY PITCH “AI period tracker”, five pillars Cycle prediction (LSTM) “92% prediction accuracy” PCOS / endometriosis risk assessment Companion Mode Biomolecular testing with a research-institute partner Philanthropy portal pad donations tracked on a blockchain Also claimed: “impacted 100+ lives”, “50+ data points”. Struck through: claims removed as unprovable. narrow, cut claims 2026 · YUWAXCEL PITCH Staged companion, four life stages Cycle& TTC Pregnancyflagship Postpartum Infant carephase 2 Survey-backed core (what the data supports) ● Consent-first Companion Mode ● Mood tracked beside the cycle ● Nutrition and fitness content ● Access to a clinician ● Free core, narrow premium Prediction as a range with confidence, not a %. Pregnancy-first is a hypothesis the survey does not test (88.7% of women respondents were 18–24).
DiagramStrategy evolution, not shipped versions. Struck-through items are claims we withdrew. Source: the 2025 public project page and the 2026 pitch.

Three early claims have to be named once, because they were public: "92% prediction accuracy" from an LSTM model, a biomolecular testing partnership with a research institute, and "impacted 100+ lives". None was ever measured or signed, and all three are withdrawn. The 2026 plan replaced the accuracy figure with a literature-based target that Myra never measured either, so the concept shows prediction as a range with a confidence label, never as a percentage.

Chapter 03

Method and sample

The instrument

We fielded an online survey on a Tally form in April–May 2025. The team wrote the questionnaire. It asked about tracking habits, symptoms, emotion and restriction, Companion Mode, help channels, feature priorities and price. The form branched on gender:

  • Women's branch, n = 106 (105 women and 1 non-binary respondent): how they track, how they feel, whether they would share, and with whom.
  • Men's branch, n = 65: whether they would use Companion Mode, for whom, and what they would want to receive.

Alongside the survey we held informal interviews and conversations. I didn't keep notes, so findings here come from the survey.

Who answered

A · Age by branch (count)Women94106Men5565Under 1818–2425–34No respondent was over 34. 149 of 171 (87.1%) were 18–24.B · Preferred language (count)Women6140106Men343065EnglishBothNepaliOnly 6 of 171 (3.5%) prefer Nepali alone.C · How they found the surveyn = 80 who answeredFriend or colleague27 · 33.8%Named a team member14 · 17.5%Email13 · 16.2%Instagram6 · 7.5%LinkedIn6 · 7.5%Other social / online6 · 7.5%Non-answer4 · 5.0%Student org / competition3 · 3.8%Instagram + email1 · 1.2%
ChartSample profile, n = 171; panel C n = 80 who said how they found the survey. Convenience sample, network-recruited, student-heavy and skewed to ages 18–24. It does not represent women in Nepal.

The sample is young (87% aged 18–24, no one over 34), comfortable in English (only 3.5% prefer Nepali alone) and recruited through our own networks: half of those who said how they found the survey named a friend, colleague or team member. That shapes everything that follows.

Before analysis, one row that had shifted by a column was realigned, and one exact duplicate is kept and noted. Free-text answers (price amounts, "what's missing") were grouped into themes afterwards, for this write-up, by one reader. Only aggregates appear here.

Chapter 04

How women track, and how they feel

Most women in the sample already track their period: 61% with an app, and more than half of those with Flo. The problem was not getting them to track. It was what they track.

Tracks it (share of 106 women)Experiences it often (rated 4–5 of 5)0%25%50%75%100%Dates87.7% tracknot a symptomMood29.2% track65.1% oftenCramps / pain31.1% track50.0% oftenMood-tracking interest: 69.8% rate it 4–5. The question offered no bloating, fatigue or anxiety tracking option.
ChartThe tracking gap. Women's branch, n = 106. Convenience sample, student-heavy, 18–24 skew; not representative of women in Nepal.

88% track the date. Under a third track mood or pain, even though mood swings are the most frequent symptom they report: 65% rate them 4 or 5 on a 0–5 frequency scale.

0 never12345 very often75%50%25%0%25%50%75%Mood swings65.1% at 4–5Cramps50.0% at 4–5Bloating43.4% at 4–5Fatigue40.6% at 4–5Anxiety / stress39.6% at 4–5Headaches11.3% at 4–5← rarelyoften →
ChartSymptom frequency, 0 = never to 5 = very often, sorted by the share at 4–5. Women's branch, n = 106. Same sample limits.

Three more answers set the tone for the design:

  • Emotion dominates. Asked which emotions they associate with their cycle, 74% chose irritation and 45% sadness; 3% chose empowerment.
  • Restriction is common. 75% have been restricted from doing something because of their period. Two more described a religious restriction in their own words instead of ticking an option.
  • Mood tracking is wanted. 70% rate their interest in mood and mental-wellbeing tracking at 4 or 5.
Chapter 05

Companion Mode, from both sides

This is the result the whole case rests on.

Women (n = 106)Comfortable if a partner or family could follow your cycle?Yes, definitely52 · 49.1%Maybe, if I control34 · 32.1%No11 · 10.4%Not sure9 · 8.5%did not tick “manage alone”also ticked “I prefer to manage it alone”39 of 106 women (36.8%) ticked “manage alone”,including 10 who said “yes, definitely”.Share interpretations,never raw logsMen (n = 65)How important to know? share rating 4–5Physical symptoms86.2%When she needs rest86.2%Start / end of period78.5%Her mood changes69.2%Ovulation / fertility67.7%What would you want to receive? share choosingDaily mood / health summary63.1%Expected-period notifications53.8%Emotional-support tips50.8%Meal / exercise suggestions41.5%Educational resources23.1%Gift / care reminders15.4%Symptom updates10.8%Chat / check-in prompts3.1%Want to understand symptoms: 86.2%. Want a symptom feed: 10.8%.Emotional-availability reminders “only if she chooses to share”: 52.3%.
ChartThe two-sided result. Women n = 106, men n = 65. Convenience sample, network-recruited, student-heavy, 18–24 skew; not representative. The men's 'what would you want to receive' item was an untitled field on the form; options are shown as published.

Women were split. 49% said yes outright to a partner or family member following their cycle. Another 32% said maybe, if I could control what they see. And 37% of all women also ticked "I prefer to manage it alone", including 10 of the 52 who said yes. Control was the swing vote.

Men wanted to understand, not to watch. 86% rated knowing her physical symptoms and knowing when she needs rest at 4–5 in importance. But only 11% wanted "symptom updates". They asked for interpreted outputs instead: a daily summary (63%) and emotional-support tips (51%). And without being prompted towards it, 52% said reminders to be emotionally available should come only if she chooses to share that info.

A · Who would share (women) and who would follow (men)Women: would trust (share of 106)Men: would use it for (share of 65)0%25%50%75%Romantic partner / girlfriend58.5%66.2%Mother24.5%58.5%Sister22.6%53.8%Friend23.6%44.6%Wifenot an option for women26.2%Prefer to manage alone36.8%not an option for menB · Men’s attitudes to consent and prompts (n = 65)Greys: answer options (darkest = the consent-conditional answer)App suggests supportive actions?Yes 44Maybe 18No 3Reminders to be emotionally available?Only if she shares 34Yes 29No 2Ever used a tracker for someone?Yes 16No 49
ChartRelationships and consent. Women n = 106, men n = 65. Same sample limits.

It isn't only partners. Men would use Companion Mode for their mother (58%) and sister (54%) almost as often as for a girlfriend (66%). Women trust a romantic partner most (58%), then a mother, a friend or a sister. So a companion is a person with a relationship, and there can be more than one.

Chapter 06

From findings to requirements

Each requirement below points back to a number. Where a requirement came from the planning documents rather than the survey, I say so.

Finding (sample as above)Requirement
32% would share only with control; 52% of men defer to her choiceR1 Sharing is per data type, off by default, and she can stop silently
Men want summaries (63%), not symptom feeds (11%)R2 The companion sees interpretations and one suggested action, never her logs
Men would follow a mother or sister almost as often as a partnerR3 Several companions, each with separate grants
Mood swings are the top symptom; 70% want mood trackingR4 Mood is logged beside flow and pain, not in a separate app
Nutrition and fitness ranked first of five featuresR5 Phase-aware food and exercise content, with local foods
58% want to talk to a doctor in the app, but 27% would pay for telehealthR6 Clinician access as an explicit, honest service, with a free core around it
Open answers complained about embarrassing notifications and false "late" alarmsR7 Discreet lock-screen copy; prediction as a range with confidence
One respondent asked for Bikram Sambat datesR8 Nepali (BS) date first, AD second
Chapter 07

The consent model

R1 and R2 together define Companion Mode. A companion never sees her data. They see what she has chosen to let Myra say about it: "She may need more rest this week", with one suggested action. Every grant starts off. The first one the concept recommends is the rest signal, because it is the thing men most wanted to know (86%) and the least revealing thing she can share.

Linking a companion, step by step

Step 1 / 6

Not sharing

Nothing is shared

The Companion screen says so plainly. Using Myra alone is a normal state, not an empty one.

Companions
0
Status chip on Home
Not sharing
Interactive reconstruction, fictional dataConcept, not built or tested. Names, code and relationship are fictional.
All steps as a table
#StateWhat happens
1Not sharingNothing is shared. The Companion screen says so plainly. Using Myra alone is a normal state, not an empty one.
2Code issuedShe invites one person. She picks a relationship and gets a short, single-use code she can read aloud or send. The screen says nothing is shared yet.
3PendingShe confirms it is them. Entering the code is not enough. She sees who entered it and confirms. A code shared under pressure still opens nothing by itself.
4Linked · 1 grantShe chooses what they can see. Every item starts off. She turns on the recommended first grant. Private notes are listed but can never be granted, and the screen says so.
5LinkedThey see a signal and an action. The companion's screen shows an interpretation and one suggested action, with two alternatives. No calendar, no symptoms, no notes.
6RevokedShe stops sharing. Two taps from her settings, and it takes effect at once. The companion sees a neutral 'Sharing paused', never a reason.

What can be shared, and with whom

DataCompanion defaultCan she grant it?
Needs-rest signal (derived)OffYes, recommended first
Period dates and current phaseOffYes
Mood summary (weekly, derived)OffYes
Raw symptom logsOffYes, one symptom at a time, with a warning
Fertility windowOffYes, with a second confirmation
Private notesNeverNo
Messages with a clinicianNeverNo

These defaults are proposals. The survey justifies their direction; it doesn't validate their details.

Chapter 08

Four ways to build a companion

Before settling on the interpretation layer, I compared it with the obvious alternatives. The scoring below is a retrospective, qualitative judgement, not a numeric score.

Survey demand Safety Feasible for 4 Pitch clarity Low build cost gates 1 · Full mirrorshe shares her calendar and logs out 2 · Partner only, one persona single romantic partner out 3 · Interpretation layerper-type grants, several people, silent stop chosen 4 · Two-way companioncompanion logs care actions too later strong partial weak
DiagramCompanion Mode options, scored qualitatively in retrospect. Two criteria act as gates: survey demand and safety. Design reasoning; survey figures from chapter 05.
  1. Full mirror. The companion sees her calendar and logs. It is the cheapest to build and the easiest to pitch, and it fails both gates: the women who said "maybe" said so on the condition of control.
  2. Partner only. One romantic partner. It fails the survey, because men would follow a mother or sister almost as often.
  3. Interpretation layer. Per-item grants, several people, silent stop. Chosen.
  4. Two-way companion. The companion can also log care actions or check in. One open answer asked for this. Kept for later, because it adds a second person's data to a system built around one person's consent.
Chapter 09

The concept screens

I designed the 2026 pitch concept screens in Figma ("Myra – Final"). By then the pitch had moved to a staged companion with pregnancy as the flagship, so the three pitch screens show pregnancy, not the cycle. The consent line, "She controls what you see", is the same.

Figma designPregnancy Home. Concept, not built or tested.
Figma designCompanion Mode, the partner's side. Concept, not built or tested.
Figma designSymptom check. Calling and directions come before any messaging option: an inbox with a reply window is the wrong tool for an emergency. Concept, not built or tested; the triage copy has had no clinical review.

For the survey's own population, I redrew the companion flow for the cycle, both sides, as wireframes.

YOU › COMPANION Partner Mother What they can see Everything starts off. Needs-rest signalRecommended first Period dates, phase Mood summary, weekly Symptomsone by one, with a warning Fertility windowasks twice Private notes · never shared Stop sharing They won’t be told why. 1 2 Invite someone Who are they to you? Partner Mother Sister Friend 482 917 code expires · single use Copy code Share link Nothing is shared yet. When they enter the code, you willconfirm it’s them and choose whatthey can see. 3 4 COMPANION’S PHONE This week She may need morerest this week. From what she chose to share. TODAY’S ACTION Send a kind message Give space Help with a task About this phase → No calendar. No symptoms.No notes. She controls what you see 5 6 7 Code and relationships fictional.
Reconstruction, fictional dataCompanion Mode, both sides, for the cycle. 1 A person switcher: each companion has separate grants. 2 Notes can't be granted, and the screen says so. 3 A short code. 4 The invite states that nothing is shared yet. 5 A derived signal, not a symptom. 6 One action with two alternatives. 7 The consent line on every companion screen. Concept, not built or tested; fictional data.
Chapter 10

Recognition, results and the pause

  1. Jan 2025First conceptAn AI menstrual-health platform, pitched for the Hult Prize.
  2. 2025Hult Prize at Kathmandu University: 2nd Runner-Up (3rd place)Then selected for the first-ever Hult Prize national competition in Nepal.
  3. Apr 2025Landing pageBuilt from my high-fidelity design, with an early-access sign-up.
  4. Apr – May 2025Survey fielded171 responses, two branches.
  5. 2026Pitch rebuilt around consentNew brand, three concept screens, and the line 'She controls what you see'.
  6. 13 Jun 2026Project YuwaXcel (USYCN): first prizeGrand finale. Total prize NPR 75,000.
  7. Sep 2026Launch siteA multi-page site for users, partners and clinicians, mostly built by hand.
  8. 2026Paused

The Hult Prize organisers announced the Kathmandu University result on Instagram.

PhotoHult Prize at Kathmandu University 2025.
PhotoProject YuwaXcel 2026, first prize.

What exists, and what doesn't

What exists: a 171-response two-sided survey, a consent model derived from it, concept screens, a brand, two pitches that won recognition, and a launch site. In the survey, 139 of 171 people (81%) said yes to early access. That is stated interest, not sign-ups.

Measured outcome: none. No app was released, so there is no usage, no retention, no prediction accuracy and no usability result. The consent model was never tested with a single linked pair.

Why it paused

We lost direction after the 2026 pitch, especially around the pregnancy-first idea, and all of us were working full-time jobs. I'd rather pause a health product than keep adding promises to one that nobody has time to build carefully.

Chapter 11

What I learned

  1. 01

    A share button is a consent system

    The two branches disagreed in a useful way: men wanted to understand, women wanted control. An interpretation layer (signals and actions instead of logs) was the design that answered both.

  2. 02

    Cut claims before adding features

    The accuracy figure, the lab partnership and 'first in Nepal' all had to go. Each withdrawal made the pitch smaller and easier to defend.

  3. 03

    Research the population you pivot to

    The survey speaks for 18–24-year-old students. The pregnancy idea needed its own sample, and not having one is part of why it stalled.

Deep dive 13

Prediction, tone and the survey's complaints

Two tone complaints about existing apps came up in the open answers: notifications that assume sexual activity, shown at embarrassing moments, and "your period is late" alarms after a single day. Both became rules in the concept:

  • A range, not a date. "Next period likely 28 Jestha – 1 Asar", with a word label for confidence ("learning, low confidence until 3 cycles"). The range widens when cycles vary. No percentage, because Myra never measured one.
  • No presumed causes. A late or irregular cycle is described, never explained by guessing at her behaviour.
  • A way out for irregular cycles. When cycle lengths vary a lot, the concept stops predicting and says that this can be normal, and that a doctor can help her understand the pattern. It refers; it doesn't diagnose.
  • Bikram Sambat first. The official Nepali calendar leads, with AD second.

These are concept rules, not built or validated, and non-clinical.

Deep dive 14

The instrument: what changed, and what I'd fix

The live form differed from the team's draft questionnaire in three ways, and each one affects how the data can be read:

  1. A men's branch was added. It is what made the two-sided result possible. Two of its fields were left untitled on the form (a 0–5 scale and a multiple-choice list), so I report the options as published and don't interpret the scale.
  2. Price became an open amount. The draft had fixed tiers. The live form asked for a free-text monthly amount in NPR, framed as "basic features stay free". Among the 70 women who named a positive amount, the median was NPR 225; 52% chose only the "completely free app" option in a separate question. Free-text coding makes these numbers soft.
  3. A device question was added late. Only 21 people answered it, so I don't use it.

The scale for "how openly are periods discussed" has no labels in the export. Respondents who had been restricted scored lower (mean 3.30) than those who hadn't (4.13), which fits 5 meaning "very open", but that direction is inferred.

A · Feature ranking, count of women giving each rank (n = 106)Rank 1Rank 2Rank 3Rank 4Rank 5Mean rankNutrition & fitness plans3632181642.25Doctor consultation via app20223022122.85Pregnancy tracking & reminders26152215283.04Period-product refill reminders20201424283.19Community support space4172229343.68Pregnancy tracking is polarised: 26 ranked it first, 28 ranked it last.B · If your pattern changes suddenly, how would you like help?multi-select, n = 105Talk to a doctor in the app61 · 58.1%AI suggestions29 · 27.6%None of the above25 · 23.8%Quick surveys20 · 19.0%
ChartFeature ranking and help channels. Women's branch; ranking n = 106, help channel n = 105. Convenience sample, student-heavy, 18–24 skew; not representative. Pregnancy tracking is polarised: 26 ranked it first, 28 last.

What I'd fix next time: title every field; pilot the form with five people before fielding; record the fielding dates and the consent text with the export; keep interview notes, even short ones; and recruit outside our own networks, with quotas for age and language.

Deep dive 15

How I would validate it

STAGE 1 · FIXSTAGE 2 · UNDERSTANDSTAGE 3 · BEHAVESTAGE 4 · DECIDE Truthful waitlistsplit success statesend-to-end test Corrected screensno clinician name, no4-hour promise, no amounts Permissions prototype5–8 moderated sessionsincl. Nepali-only readers Stop-sharing tasksuccess, time, taps Linked-pair diary2 weeks first; the planwas 30–40 couples “Late” copy A/Banxiety, comprehension Pregnancy samplewomen 20–35, pregnantor postpartum Restart or stay pausedwith evidence either way gate: promises true gate: visibility understood gate: no harm reported Stages are ordered, not dated. A failed gate sends the work back one stage rather than forward.
DiagramValidation plan with go/no-go gates, cheapest and riskiest first. A proposal; nothing here has been run.

The order matters. First, make every promise true: remove the fictional clinician and reply-time promise from the concept screens, and make the launch site's early-access form say "you're on the list" only once a sign-up is actually stored. Then test whether people understand visibility: 5–8 moderated sessions on a permissions prototype, including Nepali-only readers, where the measure is whether a participant can correctly explain what a companion will see. Then test behaviour with linked pairs, starting with two weeks. Only then decide whether to restart.

Deep dive 16

Notes on sources

  • Survey: the anonymised Tally export, 171 rows. All numbers are my recomputed aggregates; no individual answers or free text that names anyone are shown.
  • Interviews: informal, alongside the survey, with no notes kept. Nothing on this page relies on them.
  • Concept screens: my Figma file "Myra – Final" (exports to add). Redrawn wireframes are labelled as concepts.
  • Awards: first-party, with the Hult Prize at KU organiser post linked above. Certificates and photos are to be added.
  • Planning documents: the Companion Mode specification and the 2026 cycle-module plan informed the consent defaults and the prediction rules. They are stated intent, not completed work.
  • Collaborators appear by role only.
Deep chapters (states, iterations, implementation) are hidden in Story mode. Switch to Deep at the top to read them.