Sanju Varghese

Esme, a private daily couple journal

milestone ·

Today on a mock-auth build, unpaired. The prompt card is up. No names, no answers.
Today on a mock-auth build, unpaired. The prompt card is up. No names, no answers.

Esme is a private daily couple journal. Each day there is one prompt. You each write an answer the other person cannot see yet. Then you reveal together, and those two answers become a memory. It is not a chat thread, and it is not therapy.

Couple software keeps growing into a messenger or a coach. I wanted a ritual that stays the same size tomorrow. One question. Two sealed answers. One shared look.

The iPhone app now runs that loop. Today assigns the prompt and holds the answers until both people have written. Notes let you send something unscheduled. Two home screen widgets show status without showing journal text. You can leave the pair or delete the account. There is an in-app privacy policy. Analytics send event names only. An optional Face ID or passcode lock stays on the phone.

I have not put Esme on the App Store. There is no paywall. There is no export. There is no public web reply. I have not bought a domain. The still on this page is Today on a mock sign-in, unpaired. The prompt card is up. No names. No answers.

The part I keep coming back to is the reveal. Each person writes alone. The other person cannot read that answer until both have written. Then both answers open at once and become a memory. Think of two envelopes opened at the same time. That is the product. If I can read your answer while you are still thinking, I have built the wrong app.

Data lives on a server scoped to the pair. I do not claim the journal is encrypted so that only the two of you can read it. Privacy here is who is allowed to see an answer, a phone lock you can turn on, widgets and notifications that never quote what you wrote, and analytics that do not carry the words.