UX Case Study

She Barely Checked the App. But still completed her hydration goal.

An AI water habit tracker designed around real human behavior — forgetful, imprecise, busy — where the AI fills the gaps instead of punishing you.

My Role
UX / Product Designer — end-to-end from research through prototype
Duration
3 weeks — concept, design, and Figma prototype
The Problem
Existing water trackers demand precision. Users guess, feel inaccurate, and quit within a week.
The Insight
People remember by vessel, not volume. AI can estimate what they forget. Rewards should feel earned.
The app works because it adapts to how people actually behave — and the AI fills the gaps instead of punishing them.
The Solution

See it in action

Watch the prototype walkthrough before we dive into every decision.

Sudha — the persona
Meet Sudha

Sudha is a busy professional. She cares about her health but forgets to drink water most days.

She's tried trackers before — they made her feel guilty, so she uninstalled them.

This is the story of one evening where everything changed — because the app was designed differently.

Busy professionalDismisses remindersThinks in bottles, not mlMotivated by small wins
Moment 1
A Fruit Shop Rewired Her Brain Before She Even Opened the App

Sudha had a busy day. She dismissed every reminder. But then, she walked past a fruit shop — and the app's reward system kicked in without a single tap.

What usually happens

She walks on by

She's exhausted. She walks past the fruit shop — no thought about hydration crosses her mind. Maybe she grabs chips or nothing at all. The day ends dehydrated and she doesn't even realize it.

Sudha walking past fruit shop
What I designed

An internal trigger fires

Something fires internally: "I should take care of myself." But there's a second thought — "I'll get NOURISH points in the app." She buys orange juice. She hasn't even opened the app yet, but it's already working.

Sudha buying juice
🎯 Design Decision

Tiered Goals — Nourish / Streak / Power

"Designed for progress and building conscious effort of hydration."

Instead of pushing 100% every day, the app rewards small wins:

  • Nourish — counts all hydration sources including fruits and juices
  • Streak (70%) — a realistic daily goal that builds consistency
  • Power (90%+) — aspirational, for those who want to go further
The goal tiers are behavioral anchors that live in the user's mind outside the app.

Power, Streak, Nourish tiers>
Moment 2
She Opened the App for Dopamine, Not Discipline

She drank the juice. A normal tracker would never see it. But a blob mascot made her want to come back.

What usually happens

She never opens the app

She's home. She drank the juice earlier, had some water at the office. But there's nothing pulling her to open a tracker. No reason to log. No visual she's curious about. The app sits untouched on her phone, and everything she drank today disappears from her health record.

Sudha watching TV forgetting to log
What I designed

Anticipation pulls her in

She opens the app — out of pure anticipation. She wants the dopamine hit of earning NOURISH points. The vessel row is right there: her juice icon, one tap, 300ml logged. The blob perks up. She's already winning.

Logs it in 1 tap
🎯 Design Decision

Living Mascot Blob

The motivation to open comes from reward anticipation. The living blob mascot creates a visual pull — she wants to see it fill up, perk up, react to her input.

  • Water fills up inside the blob as a progress indicator
  • Mascot has expressions/moods tied to hydration level
  • Tracking feels like nurturing, like caring for something alive

Living Mascot Blob
Moment 3
She Said "1.5 Bottles" — and the AI Knew Exactly How Much That Was

She logged the juice. Now she tries to recall everything else — but this time, she's not guessing.

What usually happens

Guessing in the dark

She opens AI Chat and tries to log the rest of her day. "I think I had... some water at the office? Maybe a few glasses?" She feels uncertain. Whatever she types feels inaccurate. That dissatisfaction quietly erodes her trust in the whole system.

Guessing in the dark
What I designed

Confidence all the way

She's already saved her regular bottle in the app. She confidently tells the AI: "I finished about 1.5 bottles today, maybe 2 glasses in the morning." No ambiguity. She's speaking in her own units. Both she and the AI are working from a shared, accurate foundation.

AI chat interface
🎯 Design Decision

Vessel-Based Logging

"People drink in their bottle. So the app speaks their language."

Users upload photos of the vessels they regularly use and track intake accordingly. The whole system is designed around how people naturally measure water.

Vessel-based logging creates confidence. When the user trusts their own input, they trust the app's output. Accuracy becomes a two-way contract between user and AI.

Vessel-based logging UI
Moment 4
The AI Remembered the Water She Forgot — and Did All 8 Taps for Her

She logged what she could. But what about the desk sips, the cooler trips, the refills she'll never recall? The AI already knew.

What usually happens

Cognitive overload

A normal app would force her to remember — 7-8 more taps, mental math, second-guessing. That's cognitive load she doesn't have energy for after a long day. She closes the app with an incomplete, frustrating log.

Cognitive overload
What I designed

One tap. Done.

The AI already knows her office-day pattern. It estimates the extra intake she'll never consciously remember: "1.5 bottles + 2 morning glasses + ~1 extra glass (estimated)." She taps "Approve Estimation." The AI absorbed the entire cognitive burden in one interaction.

AI estimation approve
🎯 Design Decision

AI Pattern Learning + Visual Agency Signal

The AI learns your daily patterns and estimates what you forgot. Users tap "Approve Estimation" and they're done — the AI handles the remembering, the math, the tapping.

When the AI is working autonomously, the screen visually transforms — a clear signal that the app is actively thinking. This builds trust by making the AI's effort visible.

Moment 5
7 Days Later, the Paywall Felt Like a Trophy

She barely tried hard. The app met her where she was every single day. And the premium offer didn't feel like a sales pitch — it felt earned.

What usually happens

Goalless and drifting

She's been logging on and off. Some days 60%, some days she forgot entirely. No sense of progress. The app shows flat data — "here's your week." It feels goalless. By week 2, the app feels like dead weight on her phone.

Goalless and drifting
What I designed

7-day streak. She earned it.

The celebration screen hits: a fire icon, a week of checkmarks, a feeling of "I actually did this." And then — the premium offer appears. Not on day 1. Not as a cold paywall. It appears at her moment of accomplishment. She thinks: "Might as well level up my health for sure."

7-day streak celebration
🎯 Design Decision

Streak-Gated Premium

Premium unlocks through your streak. You earn access by building the habit — so the offer arrives at a moment of pride, when you're already feeling the value. Pricing tied to achievement (₹999 at 7-day streak).

Features: Google Fit Sync, AI Voice Input, New Level Mascots, Smart Watch Sync, Dark Mode, Streak Shields.

This flips the typical monetization model. The app proves its value first, then invites you to go deeper. Conversion becomes emotional — a natural next step.

The Spark
How a YouTube Video About "Hooked" Changed This Entire Project

I was scrolling through YouTube one evening when I stumbled on a video about Nir Eyal's Hooked: How to Build Habit-Forming Products. The core idea — the Hook Model — hit me immediately. It's a four-step loop: Trigger → Action → Variable Reward → Investment. The more a user runs through this loop, the stronger the habit becomes.

I couldn't stop thinking about it. Every feature in Emocean maps directly to this framework. The tiered goals create internal triggers. The vessel logging reduces friction for action. The blob mascot delivers variable rewards. And every interaction — saving vessels, building streaks, training the AI — is an investment that makes the next loop stronger.

This framework became the backbone of every design decision. I kept asking myself: does this feature strengthen the loop? If it did, it stayed. If it didn't, I cut it.

Reflection
What I Learned Designing Emocean

The biggest lesson from this project was simple: design for who people actually are. Tired, distracted, imprecise. Start there.

Every decision in Emocean came from the same question — what would Sudha actually do? After a long day. When she's already dismissed every notification. When she barely remembers what she drank. That's the user I designed for.

That question shaped the whole product. The app logs in bottles because that's how she thinks. The AI estimates her intake because she'll never remember every sip. The premium offer shows up after her streak because that's when she's ready to commit. I followed the behavior — the features followed naturally.

One principle I'll carry into everything I build from here:

Design for the tired user — and make them succeed anyway.

How I think about design

  • I design behavior first. Every UI choice here traces back to a real behavioral insight about how people track habits.
  • I think in systems. Tiered goals, AI estimation, vessel logging, and streak-gated premium all feed into each other — they compound retention as a loop.
  • I use narrative as a design tool. Sudha's story is how I tested every feature. If she couldn't succeed in the story, I went back and redesigned.
  • I own the full process. Research, behavioral framing, interaction design, high-fidelity prototyping — this is how I think about product.