dream-detective.case
← Desktop
js-os://work/dream-detective

Dream Detective

Cracking the Sleep Code.

  • UX Design
  • Product Design
  • Prototyping
  • Behavior Design

A narrative alarm app for college students — wake up to unlock the next clue, or snooze and lose today's chapter forever.

Most alarm apps ask for willpower. Dream Detective asks for curiosity — a daily audio mystery where snoozing doesn't pause the story, it kills today's chapter forever.

I owned this solo from research and behavioral framing through visual system, AI-assisted art direction, PRD, and interactive prototype.

Project Overview

Client

Concept · IXD Behaviors (Academic)

Industry

Health / Wellness · Behavior Change

Timeline

3 weeks · Solo

My role

End-to-end product design

Core insight

Sleep isn't a tracking problem for students — it's a motivation problem at wake-up time.

Key mechanic

Cold Trail — snooze once and that morning's chapter is permanently locked.

Strategic gap

Competitors use streaks or gamification, but none pair narrative pull with loss aversion.

What I'd validate next

Whether missing story beats outperforms a standard alarm in real wake-up tests.

Overview

Problem

Problem framing — college students and sleep behavior.

College students know sleep matters — but staying up late feels low-stakes, and alarms offer no reason to get up early. Snooze wins because nothing is at stake.

The brief: design an app that creates lasting behavior change. I reframed it as motivation design, not notification design.

Competitor analysis

Competitor analysis — behavioral design patterns across adjacent apps.

I mapped behavioral patterns across Duolingo, Forest, Pokémon Sleep, Finch, and others. Duolingo's streak loss hurts more than consistency feels good (loss aversion). Forest makes you protect something you've built. Pokémon Sleep and Finch turn sleep into collectible output.

The gap: no one combined narrative pull with irreversible consequence. Data and cute mascots exist — but nothing makes waking up the only way to find out what happens next.

Solution

Proposal — episodic audio mystery alarm with Cold Trail penalty.

Replace the alarm with a daily episodic audio mystery. Each morning unlocks the next clue — unless you snooze, in which case that chapter is gone permanently.

The Cold Trail penalty isn't shame or a broken streak. You don't fall behind — you miss the beat. That distinction keeps the mechanic fair while making oversleeping costly.

Ideation

Visual direction

Mood board — film noir, Art Deco, and adventure game references.

Wellness apps default to clean minimalism. Dream Detective needed atmosphere — film noir contrast, Art Deco ornament, and adventure-game UI that feels like a world, not a dashboard. Typewriter typography reinforces the case-file metaphor.

Exploring two directions

Sketches — Version 1 and Version 2 mobile flow explorations.

Version 1 was a minimal alarm + clue reveal — conceptually clear, but indistinguishable from a standard alarm app. Version 2 introduced the Office as home base, Evidence Board navigation, Stakeout sleep audio, and Detective Rank progress. That version sold the world.

Wireframes

Wireframes — main screen, stats, navigation, and notification states.

Low-fidelity frames for home, stats, navigation, and the morning alert — structure before style. The goal was hierarchy: where sleep data lives, how users move between Office, Evidence Board, and Stakeout, and what the wake-up moment actually looks like.

Design

UI system

UI elements — card frames, navigation notebook, and Detective Dossier panel.

Art Deco card frames, gold-on-crimson actions, and a handwritten navigation notebook carry the detective world across screens. Sleep stats become case metrics — Rest Logged, Evidence Secured, Cases Solved — so data feels native to the fiction.

Final screens

Final screens — Office, Stakeout, New Breakthrough, and Evidence Board.

Environment art was generated with Gemini and Grok; UI and interaction design were built in Figma. Background illustration was scoped to AI — hand-illustrating full scenes wasn't feasible in three weeks.

The morning alarm state is deliberately tense: high contrast, pulsing waveform, copy that signals a broadcast fading fast. The Evidence Board collects clues on a corkboard with red string — where the larger mystery takes shape.

User flow

User flow chart — day/night modes and wake-up decision logic.

Day and night modes split at 6pm — the Office changes, and different actions unlock. Night path: Stakeout sleep audio → wake-up check → briefing + mini-game or Cold Trail. Day path: stats, alarm settings, and case notebook. Everything anchors back to the Office.

When AI wasn't enough

FigmaMake explorations — Simulate Morning, Intel Secured, and Sleep Audio player.

FigmaMake accelerated individual UI elements, but couldn't handle the core interaction — spatial, first-person navigation through the Office. I built that prototype manually in Figma, covering both wake-up outcomes: Intel Secured vs. locked out.

Interactive prototype

Two-minute walkthrough of the core loop: alarm → mini-game → Evidence Board update, plus the locked-out path when you sleep in.

Morning flow — success path vs. Cold Trail

Process

PRD

Product Requirement Document — problem, solution, and feature specs.

I wrote a full PRD before high-fidelity screens — problem, features, user flow, and design specs. It kept scope honest: gamify curiosity, not guilt.

Full deck · PDF

Full slide deck — download for the complete presentation.

Full slide deck (PDF, 17 pages)

Reflection

This project shows how I work: start from behavioral research, find a defensible angle competitors missed, then design a world coherent enough to carry a punitive mechanic without feeling unfair. The concept is strong on paper — the next step is testing whether narrative FOMO actually beats an annoying alarm with real users. I'd also explore whether a social Detective Rank layer reinforces the habit or dilutes the solo mystery.