The making of Corder

Corder today is a notarized, paid macOS product with a landing page, checkout and auto-updates. Built solo, finished deliberately. First shipped build on the left, today's on the right. Move the line.


The archive

A modal that covered your transcript became a drawer beside it. Rows restore in place, retention is stated in plain words, and the window underneath stays visible and usable.

A finished meeting

Same transcript, same speakers, same timestamps. The early view dumped turns under a breadcrumb. The current one gives the meeting a title, tabs for summary and chapters, sharing, and a timeline you can read at a glance.

Settings

From a paste-your-API-key field to a system: grouped cards, one switch style, one accent color, every row written in the same voice. Boring in the best way.

First launch

The first build opened to a blank pane and a note to go press Start somewhere in the menu bar. Today the first screen is the product: one clear action, your first recording sketched in, nothing to figure out.

Corder started as AI output: it worked, it looked like a prototype. Every window is the real interface with the same data.


I do this for AI-built products

You bring a product an AI helped you build. In about 2 weeks I make it consistent, branded and shippable: components, spacing, states, copy. Async process, written updates, before-and-after pairs like the ones above.

See Corder live