← writing

What I learned building FrameMark

FrameMark started as a frustration. I kept needing to annotate frames from video files for client feedback - timestamps, notes, visual markers - and every tool I found either required an upload, a login, or a subscription.

So I built one that runs entirely in the browser. No server. No upload. You open the file locally, annotate, export. That’s it.

The constraint that made it better

Deciding early that there would be no backend forced every decision to be simpler. No auth to design. No storage to manage. No privacy policy to write. The constraint wasn’t a limitation - it became the product’s entire identity.

“No upload” is the feature. It’s the first thing on the page. It’s why people trust it.

Shipping before it’s ready

I had no formal dev background when I started this. I’ve been vibe-coding my way through React and browser APIs, learning as problems appeared. The honest truth is the code is messy in places. But it works, it’s live, and real people are using it.

Waiting until the code was clean would have meant never shipping.

What’s next

Annotation layers, better export options, and eventually a way to share annotated frames without losing the “no upload” positioning. Still figuring that last one out.

If you do video work and have an opinion on what’s missing - I’d genuinely like to hear it.