What I'm working on, what's coming, what's deliberately not.
Roadmaps lie. This one might too — but updated honestly as priorities shift. Last reviewed: 2026-05-14.
Now (in progress, May–June 2026)
These are actively in the build:
Window capture (⌘⇧W)
A click captures the focused window with its drop shadow preserved. Faster than drawing a rectangle every time. Target: 1.1.0, late June 2026.
OCR copy (⌘⇧C)
Press the shortcut while a capture is on screen — text inside the image is extracted and copied to clipboard. Uses Apple's Vision framework locally; no network calls. Target: 1.1.0.
Scrolling capture
Capture a long page (a Notion doc, a chat thread) by clicking and letting DrawShot auto-scroll. Stitches into a single tall PNG. Hardest one technically — the seam detection is what makes or breaks it. Target: 1.2.0.
Next (3–6 months out)
Committed but not started:
Pro tier (~$4/month or $40/year)
Subscription that funds continued development. Free tier stays fully featured for individuals. Pro adds:
- Brand palette presets (replace the 6 defaults with your team's brand colors)
- Export presets (WebP, AVIF, custom JPEG quality)
- Library mode — keep a searchable archive of saved captures with auto-tagged content (OCR'd text, detected app names)
- Priority email support
No feature that exists in 1.0 will be paywalled later. Pro adds new things; it doesn't gate old ones.
Target: Q4 2026.
Templates for repeat workflows
Define a "QA bug report" template — capture, then auto-apply a red rectangle around the error region, drop a step marker, and a text field for repro steps. Save as a one-key workflow. For users who report the same kind of thing 20× a day.
Linear / GitHub / Jira issue creation
One-click "send this capture as a new bug" to your tracker. Opens a panel where you fill the title + description, and the image attaches automatically. Local OAuth — credentials never touch a DrawShot server. Target: 1.3.0.
Later (someday, no commitment)
Ideas I like but haven't sized:
- iPad companion app — accept a screenshot mirrored from your Mac, annotate with Pencil, sync back. Apple Pencil for arrows would be much nicer than a mouse.
- Video clips — short (≤30s) screen recordings with annotation. Risk: this is what every "screenshot tool" eventually does and it usually drifts the product. Watching to see if users actually ask for it.
- Plugin API — a small extension surface so someone can write, e.g., a "Send to Slack channel X" action. Only after the core tool stabilizes.
- Linux / Windows ports — I'd love to. But macOS-only is the right scope for a solo dev shipping in 8 weeks. Maybe a year out.
Not on the roadmap (and why)
Things people have asked for that I've decided against. Stating reasons so you can disagree publicly:
Cloud sync of toast stack
Asked for by 4 people in beta. I'm not building it because:
- It would require a server (kills the "no backend" stance).
- It would require an account (kills the "no login" stance).
- The toast stack is a session pad, not an archive. Cross-device archive is the cloud product — Dropbox, iCloud Drive, etc. handle it.
Team workspaces / shared libraries
A "DrawShot for Teams" SaaS where everyone's captures land in a shared inbox. Pretty obvious next move, but:
- It changes the product identity from "fast capture tool" to "collaboration platform."
- The market for that already has 5 entrenched players (paid capture clouds, Droplr, Markup.io, etc.).
- I'd rather be the best capture tool than the 6th-best collaboration platform.
If demand is there, I'll revisit — but not in 2026.
AI annotation suggestions
"Smart" annotations that detect UI elements and pre-draw arrows. Tried it as a prototype in week 5; the suggestions were wrong often enough that they slowed users down. Not shipping until the model is right ~95%+ of the time.
Custom shapes / SVG import
"Let me drop my company's logo into a screenshot." Way out of scope. If you need that, Figma is the tool. DrawShot is for in-flight communication, not designed assets.
Telemetry / usage analytics
Even anonymized. The privacy posture is part of the product. If I genuinely need to learn how the app is used, I'll run a user research interview — same way I did pre-launch.
Auto-upload to imgur / cloud
Was in the 0.9.0 beta. Removed before public release. Cut for the same reasons as cloud sync — server, retention policy, abuse vectors. Not worth it for a free tool.
How decisions get made
I prioritize based on:
- What I see in user research. I do 2–3 interviews per month with people who downloaded the app.
- What email feedback asks for repeatedly. A single mention doesn't move the needle; the same ask from 5 different people does.
- What I want to use myself. I dogfood DrawShot all day; pain that I hit gets fixed first.
If your idea isn't here and you want it to be — email [email protected]. Concrete use cases beat abstract feature names.
drawshot.dev · v1.0 · macOS 13+ · free