A little more support for life with PMOS.
Product designer
Women’s health / Healthtech
Figma, Codex
1 Week
Ovaia began as an academic project exploring how a digital experience could support people navigating PMOS. The concept brought several parts of day-to-day health management together in one place.
I returned to the project independently to revisit the original experience, make more intentional design decisions and develop a more cohesive interface. This time, I built the redesign entirely through vibe coding, using prompt engineering to guide the output and refine what needed changing.
Before redesigning Ovaia, I looked at the original screens and reconsidered how people would move between tracking, resources and support. The goal was to make the experience feel clearer and more connected, without losing the breadth of the original concept.
I vibe coded the redesign from start to finish. I used prompts to describe the interface and its intended behaviour, reviewed what was generated, identified where the experience fell short, and wrote more specific prompts to improve it.
Translate a design intention into a prompt, including content, layout and interaction expectations.
Review the generated screens for clarity, consistency and unnecessary complexity.
Use targeted follow-up prompts to improve the experience and carry decisions across related screens.
I started with the structure of the whole app: onboarding, daily tracking, health records, recipes and community. I used prompts to work through the journeys, screen hierarchy and how those parts should connect before worrying about visual polish. The first-use Today wireframe is one example of that early exploration.
I wanted the redesign to feel welcoming without making health information harder to navigate. I built a shared visual language for reading, taking action and understanding feedback across health records, recipes and community.
Rose and clay give Ovaia its identity. A deeper red is reserved for actions, helping interactive elements stand apart from decorative colour.
One typeface, with size and weight creating hierarchy. Longer notes stay comfortable to read.
I considered what happens when people make a choice, complete an action or encounter an error. Persistent labels, clear selected states and written feedback make those moments easier to understand.
A solid fill marks the selected date. Checkmarks are reserved for multiple selections.
A repeatable spacing scale keeps related information together and gives separate tasks room to breathe.
Colour supports the message, but never carries it alone. Feedback is specific enough to help someone take their next step.
Cream surfaces, white cards and plum text bring consistency to different kinds of content. Health records and recipes can feel related without looking identical.
The cream page establishes the background. White cards group related content. Primary text leads, secondary text supports, and rose identifies actions.
Rather than asking everyone to track the same things, Ovaia lets people choose which symptoms matter to them. I kept the daily check-in focused on those choices, so recording how they feel doesn't become another task to manage.
Tracking is only useful if people can make sense of what they've recorded. I brought history and health information into a dedicated space, with clear labels and a structure designed for finding past entries without digging through the app.
Recipes and community discussions were part of the original idea. In the redesign, I treated them as supporting journeys, making them accessible without competing with the main tracking experience.
This project let me explore what it means to design directly through AI-generated implementation. Prompt engineering helped me move between an idea and a tangible interface quickly, but each iteration still needed careful evaluation and clear design direction.
The next step would be testing the redesigned flows with people navigating PMOS and using what I learn to challenge my assumptions.
Take a look around the prototype and explore how the different parts of the experience connect.
A little more support for life with PMOS.
Product designer
Women’s health / Healthtech
Figma, Codex
1 Week
Ovaia began as an academic project exploring how a digital experience could support people navigating PMOS. The concept brought several parts of day-to-day health management together in one place.
I returned to the project independently to revisit the original experience, make more intentional design decisions and develop a more cohesive interface. This time, I built the redesign entirely through vibe coding, using prompt engineering to guide the output and refine what needed changing.
Before redesigning Ovaia, I looked at the original screens and reconsidered how people would move between tracking, resources and support. The goal was to make the experience feel clearer and more connected, without losing the breadth of the original concept.
I vibe coded the redesign from start to finish. I used prompts to describe the interface and its intended behaviour, reviewed what was generated, identified where the experience fell short, and wrote more specific prompts to improve it.
Translate a design intention into a prompt, including content, layout and interaction expectations.
Review the generated screens for clarity, consistency and unnecessary complexity.
Use targeted follow-up prompts to improve the experience and carry decisions across related screens.
I started with the structure of the whole app: onboarding, daily tracking, health records, recipes and community. I used prompts to work through the journeys, screen hierarchy and how those parts should connect before worrying about visual polish. The first-use Today wireframe is one example of that early exploration.
I wanted the redesign to feel welcoming without making health information harder to navigate. I built a shared visual language for reading, taking action and understanding feedback across health records, recipes and community.
Rose and clay give Ovaia its identity. A deeper red is reserved for actions, helping interactive elements stand apart from decorative colour.
One typeface, with size and weight creating hierarchy. Longer notes stay comfortable to read.
I considered what happens when people make a choice, complete an action or encounter an error. Persistent labels, clear selected states and written feedback make those moments easier to understand.
A solid fill marks the selected date. Checkmarks are reserved for multiple selections.
A repeatable spacing scale keeps related information together and gives separate tasks room to breathe.
Colour supports the message, but never carries it alone. Feedback is specific enough to help someone take their next step.
Cream surfaces, white cards and plum text bring consistency to different kinds of content. Health records and recipes can feel related without looking identical.
The cream page establishes the background. White cards group related content. Primary text leads, secondary text supports, and rose identifies actions.
Rather than asking everyone to track the same things, Ovaia lets people choose which symptoms matter to them. I kept the daily check-in focused on those choices, so recording how they feel doesn't become another task to manage.
Tracking is only useful if people can make sense of what they've recorded. I brought history and health information into a dedicated space, with clear labels and a structure designed for finding past entries without digging through the app.
Recipes and community discussions were part of the original idea. In the redesign, I treated them as supporting journeys, making them accessible without competing with the main tracking experience.
This project let me explore what it means to design directly through AI-generated implementation. Prompt engineering helped me move between an idea and a tangible interface quickly, but each iteration still needed careful evaluation and clear design direction.
The next step would be testing the redesigned flows with people navigating PMOS and using what I learn to challenge my assumptions.
Take a look around the prototype and explore how the different parts of the experience connect.
A little more support for life with PMOS.
Product designer
Women’s health / Healthtech
Figma, Codex
1 Week
Ovaia began as an academic project exploring how a digital experience could support people navigating PMOS. The concept brought several parts of day-to-day health management together in one place.
I returned to the project independently to revisit the original experience, make more intentional design decisions and develop a more cohesive interface. This time, I built the redesign entirely through vibe coding, using prompt engineering to guide the output and refine what needed changing.
Before redesigning Ovaia, I looked at the original screens and reconsidered how people would move between tracking, resources and support. The goal was to make the experience feel clearer and more connected, without losing the breadth of the original concept.
I vibe coded the redesign from start to finish. I used prompts to describe the interface and its intended behaviour, reviewed what was generated, identified where the experience fell short, and wrote more specific prompts to improve it.
Translate a design intention into a prompt, including content, layout and interaction expectations.
Review the generated screens for clarity, consistency and unnecessary complexity.
Use targeted follow-up prompts to improve the experience and carry decisions across related screens.
I started with the structure of the whole app: onboarding, daily tracking, health records, recipes and community. I used prompts to work through the journeys, screen hierarchy and how those parts should connect before worrying about visual polish. The first-use Today wireframe is one example of that early exploration.
I wanted the redesign to feel welcoming without making health information harder to navigate. I built a shared visual language for reading, taking action and understanding feedback across health records, recipes and community.
Rose and clay give Ovaia its identity. A deeper red is reserved for actions, helping interactive elements stand apart from decorative colour.
One typeface, with size and weight creating hierarchy. Longer notes stay comfortable to read.
I considered what happens when people make a choice, complete an action or encounter an error. Persistent labels, clear selected states and written feedback make those moments easier to understand.
A solid fill marks the selected date. Checkmarks are reserved for multiple selections.
A repeatable spacing scale keeps related information together and gives separate tasks room to breathe.
Colour supports the message, but never carries it alone. Feedback is specific enough to help someone take their next step.
Cream surfaces, white cards and plum text bring consistency to different kinds of content. Health records and recipes can feel related without looking identical.
The cream page establishes the background. White cards group related content. Primary text leads, secondary text supports, and rose identifies actions.
Rather than asking everyone to track the same things, Ovaia lets people choose which symptoms matter to them. I kept the daily check-in focused on those choices, so recording how they feel doesn't become another task to manage.
Tracking is only useful if people can make sense of what they've recorded. I brought history and health information into a dedicated space, with clear labels and a structure designed for finding past entries without digging through the app.
Recipes and community discussions were part of the original idea. In the redesign, I treated them as supporting journeys, making them accessible without competing with the main tracking experience.
This project let me explore what it means to design directly through AI-generated implementation. Prompt engineering helped me move between an idea and a tangible interface quickly, but each iteration still needed careful evaluation and clear design direction.
The next step would be testing the redesigned flows with people navigating PMOS and using what I learn to challenge my assumptions.
Take a look around the prototype and explore how the different parts of the experience connect.