I read every message, but I'll give you a straight answer faster if you include three things. A one-line “hey it's broken” means I have to play email ping-pong, and I'm usually staring at a render bar while I wait for your reply.
- The app name and the exact version shown on its page. Some pages list multiple builds for older Macs — grab the number next to the one you clicked.
- Your macOS version and chip. “Sonoma 14.2.1, M1 Max” or “Monterey 12.7, Intel iMac.” This matters more than the app name half the time.
- What you saw versus what you expected. A crash log snippet is gold. A screen recording is even better. If it's a download problem, tell me the browser and whether you're behind a VPN or corporate firewall. I can't guess your network setup.
What happens next
I triage mail around edits, not the other way around. Some days I reply in an hour; if I'm on set or color-grading until 2 a.m., it might be a couple of days. I don't ghost anyone — if you haven't heard back after three weekdays, nudge me. I'd rather get a polite bump than have a broken tool sit in your dock.
Before you email
Two things save us both time.
Is this a “how do I…?” question
Check the comments on the program's page first. That's where editors swap workflow tips, known bugs, and “this setting fixed it for me” gems. Questions asked there also help the next person who hits the same wall. I read every comment before it goes live and sometimes jump in with a note.
Found an outdated version
Tell me. Developers push silent updates, and I miss one now and then. Include the app's official release notes link if you have it — that speeds things up.
Everything else goes to [email protected]. I keep zero marketing lists, so you'll never get a newsletter or a pitch from me. Just a reply from a bleary-eyed editor in Austin who wants the toolbox to work as hard as you do.