Skip to content
Barsky Design
All case studies

Health

NudgeMe

Natural-language reminders, designed to actually reach you

Behavior DesignAI ParsingFull-StackShipped
NudgeMe landing — 'Type it once. NudgeMe remembers.' above a single natural-language reminder field
Hiram Barsky

By Founder & Principal Designer

Role

Product Design · Full-stack · AI

Timeframe

2025

Published

July 2026

Outcome

1 typed sentence in → 5 delivery channels out

Built with

Figma Design · Claude Code — built end to end; confidence-tiered parsing · Next.js, Supabase, PWA · Netlify

The result

Live: type one plain sentence — 'call mom tomorrow at 5pm' — and NudgeMe schedules it, then actually reaches you across five channels: in-app, email, a calendar mirror, and true background push even when the app is fully closed.

Overview

NudgeMe turns a sentence like "call mom tomorrow at 5pm" straight into a scheduled reminder — no form, no date picker, no setup screen. The core promise, and the design constraint everything else answers to: type it once, NudgeMe remembers.

The problem

Reminder apps fail two ways, not one. Setup friction kills adoption before a habit even forms — every extra field is a reason to quit. And even for the reminders people do set, delivery is unreliable: most apps only notify while the app itself is open, so a due reminder in a closed tab just quietly never arrives. Solving only one of those problems isn't enough.

NudgeMe's one-field interface — typing 'call mom tomorrow at 6pm' into the 'What do you want to remember?' box, with a Remind me button below
The entire interface is one sentence. Type 'call mom tomorrow at 6pm' in plain language — no forms, no date pickers, no setup screens.

Research

Reminder apps don't lose people at one point — they lose them at two.

NudgeMe's Delivery Channels page — 'Choose how NudgeMe reaches you': push notifications, email with a test-send, and a Google Calendar mirror, each toggled independently
The answer to silent-delivery failure: layered channels — in-app, email, and a calendar mirror — each shipping and failing independently, so a reminder always has another way to reach you.

Setup friction

Every extra field is a reason to quit. Habits die in the gap between intending to set a reminder and finishing the form.

→ Drove: One typed sentence as the entire interface — parsing over forms, zero setup screens.

Silent delivery failure

Most web apps only notify while they're open. A due reminder in a closed tab just never arrives — and the user blames themselves.

→ Drove: Layered delivery: in-app, email, calendar mirror, and background push, each shipping and failing independently.

Wrong guesses destroy trust

One reminder scheduled for the wrong day teaches a user to double-check everything — which defeats the product.

→ Drove: Confidence tiers: act when certain, ask exactly one question when unsure, never silently guess.

The approach

  • 1

    Designed a confidence-tiered AI behavior model instead of a rigid form. High-confidence input creates the reminder with zero interruption. Medium confidence asks exactly one follow-up question. Genuinely unclear input asks the user to rewrite rather than silently guessing wrong and scheduling the wrong thing.

  • 2

    Treated delivery as a layered system to de-risk it, not one perfect channel to get right on the first try. Foreground in-app alerts shipped first, then email, then a Google Calendar mirror, then true background push once the app is fully closed. Each channel ships and degrades independently, so a failure in one never silently loses a reminder.

  • 3

    Designed the freemium model around a trust constraint, not just a pricing one. Free-tier limits apply only to new usage going forward. A feature a user already relies on for free never gets retroactively cut off just because a paid tier now exists.

NudgeMe's Confirm-reminder dialog — the parsed reminder ('call mom'), the guessed time (Aug 4, 6:00 PM), and a Repeats field, all editable before you confirm
The confidence tier in action: NudgeMe shows what it parsed and the time it guessed, and asks once — it never silently schedules the wrong thing.
NudgeMe's 'Time to Nudge' alert — the due reminder with its title and time, and Snooze / Done actions
Then it actually reaches you: when a reminder comes due, NudgeMe nudges — snooze it or mark it done, right where you are.
The My Reminders list — Active and Done tabs, each reminder with its schedule and a one-tap complete
Everything you've told it lives in one list — Active and Done, one-off nudges and recurring ones alike, each a tap from complete.

Our thought process

The whole app answers to one sentence: type it once, NudgeMe remembers. Every decision — parsing, confidence tiers, delivery layers, even the pricing model — got tested against whether it kept or broke that promise.

What didn't work

The first instinct was a smarter form — fewer fields, nicer pickers. It was the same old friction with better paint, so it went in the bin and parsing became the whole front door. Treating delivery as one perfect channel failed the same way: a notification that only fires while the app is open isn't a reminder, it's a coincidence. That failure forced the layered system.

The outcome

A reminder that reaches you whether the tab is open, the app is fully closed, or you're just looking at your calendar — and a monetization model that never breaks a promise it already made a user.

NudgeMe's Plans page — a Free tier with everyday reminders and recurring nudges, and a paid Plus tier that adds account sync and extra delivery channels
The trust-constrained freemium, shipped: everyday reminders stay free forever — Plus adds sync and more channels without ever clawing back a promise already made.

What this means for your project

Have an AI feature that has to act on messy human input? This is the pattern we'd bring: behavior tuned to confidence — act when it's sure, ask exactly one question when it isn't, never guess wrong — paired with a system that degrades gracefully instead of failing silently.

One of the most talented designers I have had the pleasure to work with.
Attila Bodi · Lead Product Designer, Cloudera
DAE Search results — a sortable table of 350 found data assets with therapeutic area, platform availability, and last-updated columns; real clinical datasets made findable at a glance
Next case studyDAE Search