Where the names came from

Two of the names in this app, Catchlight and Obie, come from old film-lighting craft. I went looking for where they started, and found a small, tender story I didn’t expect.

Craft · 3 min read

We’ll start with the catchlight, it’s the easiest to see. Look closely at a good portrait, or a still from an old film, and you’ll notice a tiny bright point in each eye. That’s the catchlight. It’s just the reflection of a light source, caught in the wet curve of the eye, and it does an enormous amount of work for something so small.

Take it away and a face falls flat. Cinematographers have a blunt way of putting it, without that little glint, they say, a face can look dull, lifeless, even dead. Put it back and the same face is suddenly alive, and your eye goes straight to it. A spark in the eye is the difference between a person looking out at you and a mask.

Obie is a nickname for a light. It earned that name due to the real person behind the story. In 1944 a cinematographer, Lucien Ballard, was shooting the film “The Lodger”. Its star was Merle Oberon, though her real name was Estelle Merle O’Brien Thompson. Either way, it’s where “Obie” comes from, said to be her nickname on set. The couple fell in love on that set and married a year later.

As the story goes, Oberon had been in a bad car crash seven years before, in London in 1937, and it left some small scars on her face. Ballard built her a light. A small, soft source, mounted right up by the camera lens, angled to wash gently over her face and quiet the marks down. The crew started calling it the Obie, after her, and the name stuck. It stuck so well that, the better part of a century on, cinematographers still call any little light by the lens an Obie, most of them with no idea there was ever a woman called Oberon.

I’ll be straight that the tender version of this, a man building a light to make the woman he loved look her best, is more legend than documented fact. The people who know the craft tell it with a wink, “as cinema legend has it”. The crash was real. Whether the scars were ever bad enough to need hiding, nobody can quite agree. I’ve decided I don’t mind. Some stories are true in the way that matters, even when the details have gone soft.

Here’s the part that made me want both names. Because Ballard’s little light sat so close to the lens, it did something he may never have planned. It put a catchlight in her eyes. Every time. The soft fill that smoothed her face also lit the spark that made her look alive. The Obie and the catchlight turned out to be the same gesture, seen from two sides. One is the light you add. The other is the life it brings.

That’s why they’re here. A Take you lift to the top, the single most important thing right now, is your Obie. It’s the one you point the light at. And the whole app is named for the catchlight, the small bright thing that makes the rest feel alive. A pile of notes you never look at is a vacant stare. The idea was always to put a little light back on them, so your own thoughts look out at you again.

None of this is on the screen, of course. A catchlight is invisible when it works. That felt like the right thing to name an app after.

## §Flags, worth your eye before this ships

1. **All seven titles are now colon-free** (the style card bans colons in your voice). Post 2 uses a full stop, “One Take. Why notes, tasks and reminders belong together”, per your edit. Nothing else to do here.

2. **”We” vs “I”, now RESOLVED from your #1 edits.** You moved Catchlight’s stated positions and promises to “we” (“For us”, “Why we made it”, “We think”, “we don’t hold your keys”) and kept the personal reflection as “I”. I applied that same rule across posts 2-7. **”we” for our stance, promises and design decisions, “I” for personal anecdote, confession and the reader-hypothetical (“if I forget my password”)**. Specific I to we changes I made, post 3 (“we never have to make you the thing being sold”), post 5 (“we’d not build one any other way”, “we chose your side of that trade”, “We think it’s the right call”), post 6 (“We never wanted Catchlight to make you work”), post 7 (“that includes us”, “we don’t hold your key... we can’t read”, “we wanted a name that respected that”, “one promise we’ll make”, dek “why we refuse to call it a seed phrase”). I left personal lines as “I” (e.g. post 5 “harder for me, the builder”, post 7 “I’d be lying if I dressed that up”). You took post 2’s lede the other way (“We think that’s entirely the wrong question”), which fits, it’s the product thesis, not a private aside. Revert any you’d rather were personal.

2b. **I preserved your direct edits to Post 1.** The file already had your hand-edits (the lede’s “telling the truth, yet still read your notes”, “often holding the key”, “gets your work back”, “in the cloud”, “leaves your device”, “felt fair to deliver”). I did NOT overwrite them with your chat paste, I only finished the last “I”→”we” in the closing paragraph so the whole post is consistent. If you had the file open in an editor, reload it so your copy matches disk.

2c. **Privacy Phrase capitalisation, resolved.** Your #7 capitalises Privacy Phrase throughout, matching the locked product-noun taxonomy, so it stays capitalised site-wide.

2d. **Refinement from your #3.** You put “which means I never have to make you the thing being sold” back to “I”. The rule is finer than company-equals-we, a **personal moral promise stays “I”**, a **technical fact about the app stays “we”** (“we don’t hold your keys”). Worth a specific look when you reach **#7**, where I set a few promise/naming lines to “we” (“one promise we’ll make regardless”, dek “why we refuse to call it a seed phrase”, “we wanted a name that respected that”) that by this rule you may well prefer as “I”.

3. **Apple Notes post (4).** I deliberately did NOT claim a long personal history of using Apple Notes, since I can’t confirm that’s genuinely yours. It’s written as a fair assessment plus a reader-applies-it test, not a lived anecdote. If you DID use it for years and want to say so in your own words, that would only strengthen it, but I won’t put the anecdote in your mouth.

4. **”A small team” / “us”.** Posts lean mostly solo-founder (“I”), with light “we/us” for the craft. `/story` says “I have a small team”, so this is consistent. Adjust if the team framing has changed.

5. **Product claims, confirmed by owner 2026-07-04.** Privacy Phrase is 12 words (yes), no account/email (yes), export to plain Markdown and never locked out (yes). The encryption-timing claim was CORRECTED, a Take is encrypted **the moment you save it**, not literally the first keystroke (owner: encryption happens at first save). #1 now reads “encrypted the moment you save it”. Still end-to-end, key only you hold.

6. **Nothing here entered from a warming context** and no pitch line was pulled into anything warming-facing. This is site copy, kept separate from the Reddit lane by design.

7. **Read-times** are inherited from the design cards. Once you’ve edited, I’ll recount and correct them (post 4 is the long one at 7 min, the rest 4–6).