ReMind

OVERVIEW

ReMind is a prevention first mental health app. It helps you notice what actually makes you feel better, and then reminds you about it the next time you need it.

ROLE

UX Researcher & Designer

TIMELINE

6 weeks

PLATFORM

Mobile, concept

SCOPE

End-to-end Product Design

7

Interviews

32

screens designed

6

flows mapped

5

usability sessions

THE PROBLEM

Everyone I interviewed could name something that helped them. Almost none of them could remember when.

Most mental health apps are built for after things go wrong. I was more interested in the week before that, when nothing feels urgent yet.

7/7

Never adopted a mental health app, or tried one and abandoned it

6/7

Said their last check-in happened spontaneously, not on any schedule

5/7

Only act once burnout or discomfort is already visible

Counted across 7 semi-structured interviews, ages 21 to 27.

Chapter 01

WHAT THEY COULDN'T REMEMBER

I thought people needed help staying consistent. That wasn't actually the problem.

Nobody asked me for more structure. Most of them had already quit an app that nudged them too much, so what they actually wanted was proof that the effort was worth it.

"Prompts feel like homework."

KENJI, 24

"It seems like a lot of work for very little results"

KOKI, 26

POINT OF VIEW

I wanted to explore ways to help people track their emotional growth, because without a record of what has helped before, they lose touch with what works for them.

HOW MIGHT WE

How might we help people recognize the impact of what has already helped them, so they stay engaged in caring for their wellbeing before burnout hits?

Chapter 02

TWO REASONS TO OPEN IT

People open this with very little energy left. The navigation had to ask nothing of them.

Instead of organizing around features, I organized around the two reasons someone would open the app at all.

"I want to do something"

->

Sessions

Do something now

Start a session

Text, voice, or photo

Saved kits

"I want to understand what's happening"

->

Insights

Understand yourself

Trends & dips

Favorites

Build-a-kit

Chapter 03

PROOF ON DAY ONE

The product runs on personal evidence. New users don't have any yet.

Insights like these normally need weeks of data behind them, and telling someone to come back in a month is the same problem I started with. The fix was simpler than I expected. I ask twice, once before the session and once after, so a single session produces its own evidence.

Before check

Mood, energy, stress

Guided action

Two minutes of breathwork

After check

The same 3 questions

Recorded

Surfaces next time in Insights

Mapping the full flow is where I checked the loop actually held together.

USER FLOW: LOGGING A SESSION

Chapter 04

WHERE BUILD-A-KIT LIVES

Build-a-Kit is an action, so it probably belongs in Sessions. I put it in Insights instead.

HUB 01

Sessions

Do something now

Build-a-kit

Where it would normally go

HUB 02

Insights

Understand yourself

Build-a-kit

Where I put it

DESIGN PRINCIPLE

You can't put together what helps you until you've seen what helped, so understanding has to come before the routine.

Learn how it works

Choose what helps

Name and save

SAFETY AND BOUNDARIES

This is a wellbeing app, not a medical one.

People hand this app something personal on a bad day, so I set three limits before designing anything else.

BOUNDARY 01

Not a medical device

No diagnosis, no clinical claims, and it isn't a replacement for therapy.

BOUNDARY 02

Always a tap away

Reachable from anywhere in the app.

BOUNDARY 03

Won't sell your data

Nothing shared with third parties, in plain language instead of a policy link.

KEY DECISIONS

Testing with five people changed three things I was confident about.

ITERATION 01

Renamed "Kit Tray" to "Kit Cart"

I picked "tray" because it was neutral, and shopping language felt wrong for a mental health app. But nobody knew what a tray was for and everyone knew what a cart was for, so I went with the word people understood.

BEFORE

→

AFTER

ITERATION 02

Fixed times became editable ones

I thought a set time would make a kit feel like a real routine. Users read it as an obligation instead, which is the guilt my research told me to design out, so I surfaced their own dips and let them pick a time that already fit.

BEFORE

→

AFTER

ITERATION 03

The navigation bar had to say more

Five silent icons kept the interface as quiet as I wanted, but it also meant nobody could predict what was behind them. Now only the tab you're on shows a label.

BEFORE

→

AFTER

— THE COMPONENTS —

OUTCOME

Prevention over reaction

A lot of the decisions I'm happiest with are ones you wouldn't notice while using it, and I think that's right for an app like this.

LIMITATIONS

What I still don't know

01

UNTESTED

Claiming an action helped you

How much data makes that honest?

UNDERTESTED

"Kit Cart" tested well once

Does it hold up after a month of real use?

02

UNDER-RESEARCHED

Everyone I talked to was 21 to 27

Older or higher-risk users may need something different.

03

NOT DESIGNED

Privacy is a principle, not a feature

Consent, export, and deletion still need real screens.

04

Designed by Shu Watanabe · 2026