Blog

Notes on building a small, fast tool.

Workflow ideas, design decisions, honest comparisons with other capture tools, and the occasional retrospective. One designer's perspective.

Most recent

For QA engineers: workflows that make repros stick

A QA engineer I interviewed for this post told me her job is "20% finding bugs, 80% convincing engineers the bug is real." That ratio sounds right based on the four other QAs I've talked to.

July 24, 2026·use-case · qa

For designers: faster Figma feedback with DrawShot

I'm a designer. I spend a lot of time in Figma, both producing work and reviewing other people's. Feedback is the bottleneck — not the design itself, but the coordination of leaving comments, sharing…

·use-case · designers · figma

For developers: faster bug reports with DrawShot

If you work on a software team, you file bug reports. If you file bug reports, you take screenshots. If you take screenshots, you know the depressing math: a single bug repro is maybe 90 seconds of "…

·use-case · developers

⌘⇧4 isn't enough — when to graduate from native

The native macOS screenshot tool is good enough for most people. I want to say that clearly before this post sounds like an argument it isn't.

·workflow · native-macos

Best free macOS screenshot tools in 2026

I'll be upfront: I build one of the tools on this list (DrawShot). I've tried to write this fairly anyway, because the alternative — pretending DrawShot doesn't exist — would be silly, and pretending…

·comparison · listicle · free-tools

DrawShot vs Shottr — an honest comparison

Shottr is the most direct comparison to DrawShot. Both are macOS-native, both are free for individuals, both prioritize speed. If you're choosing between them, here's the honest breakdown.

·comparison · shottr

DrawShot vs the paid alternative — an honest comparison

The leading paid macOS capture app is the polished, well-built tool that I used myself for two years before building DrawShot. This is going to be an honest comparison — what the paid alternative doe…

·comparison · paid-alternative

Why local-only — and what it costs

DrawShot does not have a server. There is no account, no telemetry, no analytics, no cloud sync, no team workspace. The only network connection the app makes is an optional once-a-day update check, w…

·privacy · product-decisions

Designing the toast stack

The toast stack is the row of small annotation cards that float at the bottom-right corner of your screen after you take a capture. It's the part of DrawShot I'm most proud of — and it took the longe…

·design · ux · craft

Building a native macOS app in 8 weeks, solo

DrawShot is built in Swift with SwiftUI for the UI shell and AppKit for the annotation canvas. It's a 12,000-line codebase. I started March 14 and shipped 1.0 on May 14.

·engineering · native-mac · solo-build

4 seconds to clipboard — the north-star metric

Every product needs one number that, if it gets worse, means the product got worse. For DrawShot, that number is time-to-clipboard (TTC) — the elapsed milliseconds between pressing the capture hotkey…

·metrics · product-thinking

Screenshots aren't files

Open your ~/Desktop folder. Count the files starting with Screenshot.

·product-thinking · design

Why I built DrawShot

For the past three years I've taken roughly 40 screenshots a day. Most are for Slack messages — "this button is broken," "look at this number," "the copy on this page is off." A few are for design re…

·launch · founder-story · product