The complete loop in under 60 seconds.

Notification → pick a photo → guided reaction → optional context → saved.

Tested in the wild. 20 participants. Zero onboarding.

We built an MVP web app and approached strangers in public with no prior explanation — no pitch, no context. We handed them a QR code and waited three seconds after they finished before saying anything. Two rounds of testing. The signal was clear: users were willing to reflect when the loop felt quick, private, and guided. Most still needed a clearer reason to return.

Designing around existing behavior.

Most memory products ask users to build a new habit. "Open the app every day and journal" competes with rest, routine, and everything else — and loses almost every time. The problem isn’t motivation. It’s activation energy at the wrong moment.

Recallia stacks onto something that already happens: taking photos. A nudge surfaces while the context is still fresh — not hours later when the feeling has been replaced by whatever mood the user is in now. The product doesn’t ask users to remember to reflect. It meets them at the moment.

Every decision traces back to one principle.

Reduce friction. Reflection without pressure. Capture context over content. If a decision couldn’t be justified by one of these, it was cut.

How observations became product choices.

Each finding maps directly to a decision. Nothing in the flow was added without a behavioral reason to exist.

The problem wasn’t getting people to save more memories.
They were already doing that.

The problem was preserving context before it disappeared. A photo proves something happened. Context is what makes it worth returning to — and context has a half-life measured in hours, not days.

Testing on strangers with zero explanation produced "therapeutic" and "this makes it feel more alive" without prompting. The loop worked. The open question was always re-engagement — whether captured moments would pull people back on their own. That became the brief for Sunday Reveal.

Moment Creation is an exercise in minimum viable reflection. The behavior was already there. The product just needed to meet it at the right moment, with the lowest possible ask.

From moments to meaning, once a week.

Timeline growth → anticipation → Sunday unlock → personalized reflection.

Reflection is delayed gratification.

Same starting point, two different systems. One fades by Wednesday. One compounds toward Sunday.

Visual progress creates motivation.

Feedback doesn’t need to be numerical. It needs to feel alive — four sources, one direction.

Designing for anticipation, not obligation.

One operating principle. Five rules that protect it.

Directional signal from early testers, not a study.

People work harder the closer they get to the reward.

Same behavior, just visible. Sunday Timeline doesn’t manufacture urgency — it surfaces the curve that was already there.

Not a journey map. A loop that compounds.

Six stages, no exit. Memory Value feeds directly back into the next Moment Creation.

Six memories, a countdown, and a reveal card. One screen, no scroll.

This screen was harder to design than it looks. A title, six memory cards, a countdown, and the Sunday reveal card all needed to fit on one screen — without scrolling. Multiple layouts were explored before arriving at the current composition.

Lo-fi — six ways to format the countdown

Day/hour/minute counters, bracketed timers, a progress bar, two ‘ready to open’ treatments. Each explored how much urgency the reveal card should communicate without tipping into pressure.

Lo-fi — how much to reveal before Sunday

Left surfaces moment tags — a preview of what’s been captured. Right keeps it blurred, withholding everything until the reveal. Both test the same question: how much should the system show before the reward arrives?

Sunday Timeline wasn’t designed to archive memories.

It was designed to make meaning visible before the reward arrives. Instead of asking users to remember why they should come back, the product gives them something to anticipate.

Reflection isn’t automatic.

The goal wasn’t efficiency. It was ceremony.

Opening the letter should feel like opening mail — not loading a screen.

Friction wasn’t removed here. Tiny moments of slowness were preserved on purpose — rituals are remembered, instant content isn’t.

Five pages. Each one earns the next.

Information architecture, not layout — what each page is for, what it’s trying to make the reader feel, and what it’s built from.

Orchestration, not generation.

Five pages of the Sunday Letter are assembled from a fixed pipeline — not a single prompt asked to improvise.

AI doesn’t invent meaning here. It synthesizes existing context — the system adapts tone instead of manufacturing depth.

No two letters should feel identical.

The same six inputs shape six different decisions in how the letter gets written.

The goal isn’t perfect accuracy. It’s recognition — the reader thinking “this sounds like my week,” not auditing it for facts.

Finding the right medium.

Three explorations, each closer to the final feeling than the last.

V1 — Single Page

One long scroll. Everything on a single page.

V2 — Refined

Same scroll idea, tightened inside a real frame.

V3 — Letter System — Won

Broken into discrete pages with Back/Continue — a sequence to move through, not a feed to scroll past.

Designing meaning taught me more than designing AI.

From an idea between friends to a shipped product.

Recallia started on May 1, 2025. Five months later, Joshua Jenkins and I launched on the App Store.

People wanted to remember more. Journaling made that feel like work.

Recallia started with a simple observation: people want to remember their lives more intentionally, but the tools for doing that feel like homework. Journaling asks for a discipline most people don’t have on a given Tuesday night. Photos pile up by the thousands and get revisited by almost no one.

Charlie Wang and Joshua Jenkins had been friends for over a decade — through Berkeley, USC, and the years between — before either of them thought of Recallia as more than a shared curiosity. Started in May 2025, it began less as a startup idea and more as a question two friends kept circling back to: why does something almost everyone says they value get abandoned so easily?

The early hypothesis was narrow on purpose. If capturing a moment could happen in the same instant someone was already taking a photo, reflection might not need its own habit — just a lower bar to clear.

Neither was a guarantee. Both were a direction worth testing.

What people say and what people do are different signals.

The first version of Recallia was built on one assumption: if capturing a moment was easy enough, people would do it. Reduce the friction, and the habit takes care of itself.

In conversations, that assumption held up well. People nodded. People said they wanted exactly this — a way to hold onto the small stuff before it disappeared. It was easy to mistake that enthusiasm for validation.

Behavior said something else. Users downloaded the app, created a handful of moments in the first sitting, and quietly stopped. Not because anything broke — because nothing was pulling them back. What people say in an interview and what they actually do a week later turned out not to be the same signal, and the gap between them was where the real product question lived.

A few problems surfaced once we looked past the interviews: Recallia was hard to explain in one sentence, it didn’t sit cleanly in a category people already understood, and there was no mechanism creating a habit — capture depended entirely on a user’s own discipline, in a category already crowded with apps asking for exactly that.

We stopped explaining Recallia and started watching people use it.

No download, no account — just a QR code and thirty seconds with a stranger. We said as little as possible going in. We cared more about what someone’s face did than what they told us afterward.

A strong reaction in the moment, and no evidence yet of a reason to come back. That distinction — not the praise, not the confusion alone — became the question the rest of the product had to answer.

The reward can’t be the reason someone captures a moment.

The original loop was simple: capture a moment, save it. It made sense on a whiteboard and fell apart in practice. Capturing took effort, and saving gave nothing back. There was no transformation between the two — no sense that the moment had become something more than a record. Without that, there was nothing to close the loop, and nothing to make someone want to open the app again.

The first realization was that reflection wasn’t a feature people were missing. It was already something they wanted — they just didn’t want the effort traditionally attached to it. People weren’t rejecting journaling because the idea was bad. They were rejecting the work.

The second was that a photo alone couldn’t carry that weight. A photo proves something happened. It doesn’t say why it mattered, and without that, there was nothing for the system to reflect back.

The realization that reordered everything was about sequence, not features: the reward couldn’t be the reason someone captured a moment, or capture would feel like a transaction. The reward had to arrive later, separated from the effort, so it could feel like a gift instead of a receipt. That’s the realization Sunday Reveal came from — not a feature to add, but the answer to where the missing payoff in the loop needed to live.

Every card has a story.

Marketing, for us, was curiosity first: where do memories already matter to people, in a way we could learn from? One answer was a trading card show — collectors already understand that a card’s value is rarely about the card. It’s the memory attached to it.

The line that carried the booth

The raffle — reason enough to stop walking

The booth stayed deliberately small: a raffle to get people to stop, a QR code to skip the download, and someone walking each person through it live instead of handing over a phone and stepping back. The reactions echoed what we’d already heard — warmth, and the same unanswered question of when someone would use it on their own. Two different rooms, the same open question.

Recallia existed outside Figma, too

USC ↓ Berkeley — posters went up at both, by hand.

Shipping was permission to start learning, not a finish line.

We avoided accounts, downloads, and onboarding for as long as we could. Each one adds a step between an idea and finding out if it’s true — and a QR code can test a concept on a stranger faster than an app store listing ever could.

The product didn’t change because we ran out of ideas. It changed because our understanding of the problem kept changing underneath it.

Liking something and building a habit are different problems.

The hardest realization wasn’t a failure. It was closer to a contradiction — and the same sessions kept producing both halves of it.

We had real evidence the emotional experience worked. We had no evidence it would find its own way into someone’s ordinary week without us standing there. That gap moved the question — less “what should we add,” more “what makes someone come back.” Features couldn’t answer a behavior problem.

Underneath that was a bigger one we couldn’t engineer around: people procrastinate, emotion fades within hours, and reflection is one of those things almost everyone agrees is good for them and almost no one sustains without help. So the questions got more basic, not less — were we solving a problem people actually had? Was a photo even enough to anchor a memory worth revisiting? We didn’t have clean answers. We treated that as information, not a setback.

Small enough to know our users. Large enough to keep learning.

We don’t have a dashboard to optimize. We have conversations and behavior we can watch directly — and the ability to make a meaningful change quickly instead of waiting on a sample size.

People don’t talk about Recallia in terms of capturing moments. They reach for meaningful, therapeutic, appreciation — language that pointed to a sharper framing: simple reflections that make everyday photos more meaningful. Not a new place to put photos. A layer on top of a habit that already exists.

Memories aren’t meaningful because they’re rare.

Most of what’s next is still a question rather than a roadmap.

Can appreciation become a habit the way productivity or fitness has? What actually triggers someone to reflect without being asked to? Is there a version of reward that encourages consistency without turning reflection into another metric to chase? Can AI help someone understand themselves a little better without quietly writing the self-understanding for them? And underneath all of it: who is this actually for — the person already inclined to look back, or someone who’s never had a reason to until now?

We don’t have settled answers to any of these, and we’re not in a hurry to manufacture them.

If there’s a single idea underneath all of Recallia, it’s this: memories don’t become meaningful because they’re rare. They become meaningful because we return to them.