
About the project
Itura is a mental wellness app for creatives. It combines journaling, mood tracking, meditation sounds, oracle and astrology readings, and an AI companion. I joined as the sole product designer after a beta had launched. The product had strong visual momentum but wasn't easy to use or easy to build on. I worked with the founder, a product manager and two developers for 2-3 months.
The Problem
The beta looked impressive, but the screens were crowded. Too many elements competed for attention, so a new user landing on a screen couldn't tell where to look first or what to do. The files were also fragmented and the patterns inconsistent, which made iteration slow and risky for the team.
For this audience, that matters more than usual. People using a wellness app are often tired or overwhelmed. A busy screen adds to the load they came to put down.
The design question was: how do we make every screen obvious at a glance, and make the product easy for a team to keep building?
My Role
I audited the existing design, rebuilt the component library, restructured the user flows and wrote the developer handoff documentation, working with the founder, PM and developers.
What I designed, and why
An audit before a rebuild
I reviewed what existed and kept what was working. The dark, moody palette suited the audience and the brand, so it stayed. Underneath it, I rebuilt the structure: one component library, consistent patterns and clear documentation, so design and development could iterate without breaking things.
Less on screen, with a clear first action
The product felt "gamified" in its presentation, with many competing elements and no obvious starting point. I removed elements that served no purpose. I then used placement and proximity to group things that work together, so each screen has a clear first thing to look at. On the dashboard, for example, the week's mood sits at the top, followed by one gentle question: "Would you like to reflect in your journal?"
Earning trust, in order
I structured the experience by how much each step asks of the user:
Journal first, the lowest-effort, most private way in.
Mood tracking second, once someone is comfortable.
AI reflection by invitation. It's offered as a 'Continue with Ra' button, never forced.
Gentle motion
I used restrained motion instead of attention-grabbing animation. While an oracle reading loads, the screen shows a "Take a deep breath" prompt, so the waiting time becomes a calming moment.A foundation the team can build on
I delivered a full component library and handoff documentation, so developers could build consistently and the team could add features without redesigning what existed.
Working With The Founder
The founder had strong views on how the product should look. I looked for ways to keep her vision and still give users what they needed, so trade-offs stayed small and the conversation never became design versus preference. She was pleased with the result and with how quickly I turned around changes.
Outcome
Delivered a rebuilt component library, restructured user flows and developer handoff documentation.
The founder was pleased with the design and with the speed of iteration.
The project paused before launch metrics were available, so there are no usage results to report.
Client
Encompasswell
Stack
Figma
Timeline
2 Months
Year
2025





Visuals



