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.
Role
Timeline
Team
Platform
Not mine
Measured outcome
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?
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.
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 did | The 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 team | The questionnaire, the pitches |
| Nobody did | A mobile app, a usability test, a clinical review |
| Status | Concept, 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.
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.
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
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.
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.
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.
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.
Companion Mode, from both sides
This is the result the whole case rests on.
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.
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.
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 choice | R1 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 partner | R3 Several companions, each with separate grants |
| Mood swings are the top symptom; 70% want mood tracking | R4 Mood is logged beside flow and pain, not in a separate app |
| Nutrition and fitness ranked first of five features | R5 Phase-aware food and exercise content, with local foods |
| 58% want to talk to a doctor in the app, but 27% would pay for telehealth | R6 Clinician access as an explicit, honest service, with a free core around it |
| Open answers complained about embarrassing notifications and false "late" alarms | R7 Discreet lock-screen copy; prediction as a range with confidence |
| One respondent asked for Bikram Sambat dates | R8 Nepali (BS) date first, AD second |
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
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
Arrow keys work too
All steps as a table
| # | State | What happens |
|---|---|---|
| 1 | Not sharing | Nothing is shared. The Companion screen says so plainly. Using Myra alone is a normal state, not an empty one. |
| 2 | Code issued | She 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. |
| 3 | Pending | She 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. |
| 4 | Linked · 1 grant | She 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. |
| 5 | Linked | They 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. |
| 6 | Revoked | She 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
| Data | Companion default | Can she grant it? |
|---|---|---|
| Needs-rest signal (derived) | Off | Yes, recommended first |
| Period dates and current phase | Off | Yes |
| Mood summary (weekly, derived) | Off | Yes |
| Raw symptom logs | Off | Yes, one symptom at a time, with a warning |
| Fertility window | Off | Yes, with a second confirmation |
| Private notes | Never | No |
| Messages with a clinician | Never | No |
These defaults are proposals. The survey justifies their direction; it doesn't validate their details.
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.
- 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.
- Partner only. One romantic partner. It fails the survey, because men would follow a mother or sister almost as often.
- Interpretation layer. Per-item grants, several people, silent stop. Chosen.
- 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.
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.
Asset to add
Figma: Myra – Final — Pregnancy Home (week 22), 2x PNG. Remove the fictional clinician name and any reply-time promise before export.
Asset to add
Figma: Myra – Final — Companion Mode, partner view, 2x PNG
Asset to add
Figma: Myra – Final — Symptom check, 'Please see a doctor today' with Call now and Directions, 2x PNG
For the survey's own population, I redrew the companion flow for the cycle, both sides, as wireframes.
Recognition, results and the pause
- Jan 2025First conceptAn AI menstrual-health platform, pitched for the Hult Prize.
- 2025Hult Prize at Kathmandu University: 2nd Runner-Up (3rd place)Then selected for the first-ever Hult Prize national competition in Nepal.
- Apr 2025Landing pageBuilt from my high-fidelity design, with an early-access sign-up.
- Apr – May 2025Survey fielded171 responses, two branches.
- 2026Pitch rebuilt around consentNew brand, three concept screens, and the line 'She controls what you see'.
- 13 Jun 2026Project YuwaXcel (USYCN): first prizeGrand finale. Total prize NPR 75,000.
- Sep 2026Launch siteA multi-page site for users, partners and clinicians, mostly built by hand.
- 2026Paused
The Hult Prize organisers announced the Kathmandu University result on Instagram.
Asset to add
Photo or certificate: Hult Prize at Kathmandu University 2025, 2nd Runner-Up (founder only, or team with consent)
Asset to add
Photo or certificate: Project YuwaXcel (USYCN) 2026 first prize, finale 13 June 2026
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.
What I learned
- 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.
- 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.
- 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.
Companion link states and difficult cases
The rule behind the diagram: anything that reduces access is silent. The companion never learns what was removed or why. Editing grants keeps the link; the companion simply sees less.
| Situation | Her side | Companion's side |
|---|---|---|
| No companion yet | "No one is following your cycle. That's fine." | — |
| Code expired or cancelled | Back to no companion; invite again | "This code has expired" |
| Wrong code entered | — | "That code didn't work"; no hint about whose it was |
| She turns on anonymous mode | Sharing is blocked, with the reason: sharing and anonymous mode can't run together | "Sharing paused" |
| She removes one grant | That item disappears from their view | No alert naming what was removed |
| She stops sharing | "Stopped. They won't be told why." | "Sharing paused" |
| Two companions | A person switcher; grants are per person | Each sees only their own grants |
| Life stage changes (for example, pregnancy) | Asked again before anything new is shared | Nothing changes until she grants it |
Notifications follow the same idea. Lock-screen copy is generic by default ("You have a reminder"), because the survey's open answers described embarrassing notifications at bad moments, and because restriction at home means other people see the phone.
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.
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:
- 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.
- 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.
- 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.
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.
How I would validate it
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.
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.