UI/UX Design — Team project, Rhine-Waal University of Applied Sciences
The Pause
An app that helps people out of doomscrolling shouldn't trap them in another app. That's why there's no sign-up.
90 seconds
That's how long an emotion actually lasts. Everything after is the story we tell about it.
Begin- Context
- University team project, Rhine-Waal University of Applied Sciences
- Team
- Maryam, Tai and Navid
- My part
- Research, flowchart and user journey
- Focus
- Interaction design, UX research, UI
- Platform
- Mobile app concept
- Status
- Concept — high-fidelity prototype in progress, testing with real people next
Principle
No sign-up, no trap
An app that helps people out of doomscrolling shouldn't pull them into another app. So The Pause asks for nothing before it helps: no account, no email, no profile to fill in. You open it, you take your ninety seconds, and you leave. Every other decision in the project was checked against this one.
Problem
The scrolling hole
Feeds are built without a natural stopping point. A scroll often begins as a small escape from something uncomfortable — boredom, stress, a hard conversation — and twenty minutes later the feeling is still there, now with the added weight of lost time.
Most tools that try to help answer with the same mechanics they are fighting: streaks to protect, badges to earn, notifications to pull you back, guilt about screen time. We wanted the opposite — a tool that meets the feeling underneath the scroll, then lets you go.
Core moment
Ninety seconds with the feeling
The heart of the app is one moment: you sit for ninety seconds with the emotion behind the urge to scroll. Not to fix it, and not to judge it — just to notice it. It is a small nudge to recognise what you were really looking for when you reached for the feed.
We took the timeframe from the "90-second rule" described by neuroanatomist Jill Bolte Taylor in My Stroke of Insight (2008): the chemical surge of an emotion passes through the body in about a minute and a half, and what keeps it going after that is the story we tell ourselves about it.
We use it as a design premise, not a clinical claim. Ninety seconds is short enough that someone mid-scroll will agree to it, and long enough to interrupt the loop — a container with a clear beginning and a clear end.
Principles
An app that wants you to leave
Every decision was checked against a short set of rules, written to keep the app from becoming one more thing to scroll:
- No sign-up. Nothing stands between opening the app and the pause itself.
- One ritual, then out. Each session ends with a clear exit back to your day — never a feed, a suggestion or "one more".
- No streaks, no scores. Missing a day costs nothing. There is nothing to protect.
- No pull notifications. The app only appears when you open it, or at a time you set yourself.
- No guilt. Copy never comments on screen time or judges what you were doing.
- Calm by default. One element on screen, slow motion, no red badges, no counters.
Research, flow & journey
How we got there
My part of the project was the research, the flowchart and the user journey. I reviewed existing mindfulness, screen-time and emotional-regulation apps to see how each handles the moment someone wants to stop, and found that many rely on rewards, streaks or warnings to change behaviour.
I then mapped the flow end to end — from noticing the scroll, through naming the feeling and the hold, to release — and the user journey around it, before the team touched any visual design. The design decisions that followed were made together by Tai, Navid and me.
Iterations
From a mascot to a single ring
The interface went through three passes: a low-fidelity wireframe to test whether the flow held up on its own, a higher-fidelity version with a visual personality, and a dark-mode variant for use at night — when scrolling is often at its worst.
The first high-fidelity version used a mascot and a chat-style conversation. On review it worked against the goal: a character to talk to is one more thing asking for attention. We removed it and rebuilt the experience around one element — a ring.
Final design
Name it, hold it, release it
What's bringing
this up?
In one word,
what is it?
47 seconds left.
Press and hold.
Let it move through.
You're here.
The ring is the whole interface: calm before you start, filling slowly as you hold, empty again at release — ninety seconds made visible without a word of explanation.
Holding…
Holding…
Interaction
The hold, in detail
- Press and hold, not tap. Holding keeps a thumb on the screen and off the feed; the physical effort is small but deliberate.
- Letting go pauses, it never fails. The ring waits where it stopped. There is no "try again", no lost progress.
- A slow pulse. A soft haptic every few seconds gives the body a rhythm to breathe with, without needing to look.
- Silence by default. No sound unless the user turns it on — people often scroll in public.
- A clean exit. Release offers one optional line to write how you feel now, then returns you to your phone's home screen, not to the app.
Care
Accessibility and safety
- Reduced motion. When the system setting is on, the ring fills in calm steps instead of continuous motion.
- Screen readers. The ring announces progress at quiet intervals ("half way", "ten seconds left") instead of every second.
- One hand, any light. The hold target sits in thumb reach; light and dark modes both meet contrast guidelines.
- Not a treatment. The Pause is a small everyday ritual. If someone names a feeling that sounds like crisis, a quiet link to local support appears.
Next
Testing with real people
The Pause has not been tested with users yet, so this page makes no claims about results. I'm now building a high-quality prototype and will test it with real people over a few days: starting a pause from mid-scroll, naming a feeling, completing the hold, letting go early, and leaving the app.
What I want to learn: whether people complete the ninety seconds, whether they feel calmer afterwards, whether they go back to the feed or to something else — and whether anything in the app ever feels like it is asking for more of their time.
After the course — what I learned from testing, and what I changed, will be added here.