Carea

Many pregnancy products concentrate on the baby and a predictable week-by-week path. Carea set out to support the woman as well—through fertility treatment, pregnancy, postpartum recovery, and pregnancy loss—including the physical and emotional moments that are often left outside the app.

That breadth created a sensitive interaction-design problem. Each journey needed its own language, inputs, reminders, and expectations, yet the product still had to feel coherent. A woman should be able to understand what matters today, record it without unnecessary effort, and return to a trustworthy history without navigating four disconnected products.

Support different journeys with care while keeping the product familiar enough to use on a difficult day.

My role was to create the UX/UI when Carea introduced or extended a feature. I translated the request into an end-to-end flow: where someone enters, what information they need, the decisions and states along the way, how errors or incomplete entries behave, and what should happen after confirmation.

I worked within Carea's existing product direction and collaborated with the founder, product designers, clinical contributors, and mobile engineering. Subject-matter expertise defined what information the product needed to handle; my responsibility was to make that information understandable, sequence it into a usable interaction, and carry the interface through implementation-ready states.

The available evidence documents the shipped product and client feedback, but not formal research sessions or controlled usability studies. I therefore describe the flow work and released scope directly without inventing research findings or claiming outcomes the product has not measured publicly.

The design task was not to decorate a requested feature; it was to define how a person would move through it.

As Carea grew, the product expanded beyond pregnancy and early postpartum into fertility treatment, pregnancy after loss, and dedicated healing-after-loss support. The current product also connects tracking with emotional wellbeing tools, expert guidance, and community support.

For design, each addition required more than another destination in the navigation. The entry points, language, empty states, reminders, and transitions had to respect the context a woman was in while remaining recognizably part of Carea. Reusing the interaction grammar made the system expandable; adapting tone and emphasis kept each journey from feeling generic.

Consistency came from a shared model. Care came from knowing where that model needed to bend.

Carea is live on iOS and Android. Its Postpartum Mum Tracker shipped in November 2025, and the current product presents four connected journeys: pregnancy, postpartum, trying to conceive through IVF or IUI, and healing after loss.

A verified client review reports a successful MVP launch followed by multiple releases and positive user feedback about the product's design and functionality. Carea's current website also publishes feedback that specifically values having support in one place, easy navigation, and a calm visual experience.

Those signals verify delivery and show that people respond positively to the experience, but they do not isolate the effect of my design work from clinical input, content, engineering, product strategy, or later releases. A stronger impact story would require flow-level measures such as completion, abandonment, reminder acknowledgement, support escalation, and repeat use after each feature launch.

The defensible outcome is a shipped, expanding product with positive user response—not an unsupported claim that design alone produced it.

This work reinforced that a feature request is only the beginning of the design problem. The useful unit of design is the complete experience around it: entry, context, decisions, edge cases, confirmation, and the path back into the product.

It also made the value of a shared interaction model tangible. Repeating familiar patterns reduced the amount a person had to learn, while thoughtful language and pacing let the same system support very different emotional contexts without flattening them into one generic journey.

In the next phase, I would pair every new flow with a lightweight measurement plan before release and combine behavioral data with focused conversations about confidence, tone, and perceived support. Those signals would help the team distinguish a flow that merely ships from one that genuinely helps.