[verdict][curated prompt][source: shotomatic.com]
Can I vibecode Shotomatic?
// buildable in a weekend, but real gaps stay open
A personal timed screenshot loop is a realistic weekend build. Matching reliable capture across Mac apps, permission recovery, website batches, guide editing, and polished exports is a much larger product.
confidence: high
what it is: Automated Mac screenshots, website batches, guides, and local exports
Buildability index · an editorial game
- Price 7.99 $/month weight: plus 1
- Time weekend weight: plus 2
- Category screenshots no weight
- Moat execution quality weight: minus 1
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site shotomatic.com (si apre in una nuova scheda) no weight
They cancel out. This is where it comes down to how much the subscription annoys you.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Pick a display or window, capture it on an interval, keep the session local, and export the ordered images.
what you need
- macOS 14 or later
- Xcode command line tools
- Screen Recording permission
- Accessibility permission for optional keypress automation
The basic loop is buildable; dependable native automation and workflow breadth are the paid product.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build me a local macOS screenshot automation app covering Shotomatic's basic loop.
Requirements:
- Use SwiftUI and ScreenCaptureKit in a native macOS 14+ app with no third-party packages.
- Provide a source picker for one display or one visible window, with thumbnail previews.
- Let me set an interval in seconds and stop after a screenshot count or elapsed duration.
- Show a three-second countdown, live running status, captured count, and a clear Stop button.
- Save every capture as PNG or JPEG in ~/Pictures/Capture Sessions/<timestamp>/.
- Keep a local session list with thumbnails; open a session in Finder or delete it with confirmation.
- Add one optional keypress after each capture using CGEvent so paged content can advance.
- Check Screen Recording and Accessibility permission before starting; explain how to grant each.
- Never upload files, add accounts, or collect telemetry. The app must work fully offline.
- Handle a display or window disappearing mid-session without losing images already captured.
- Include a small unit-tested state machine for idle, countdown, running, stopping, and failed states.
- Include a README with build, permission, and signing notes plus a manual smoke-test checklist.
- Out of scope: custom-area capture, website batches, guide editing, annotations, PDF/ZIP/MP4 export.
- Produce an Xcode project that builds and runs, then run the unit tests before finishing.Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- polished display, window, and custom-area selection
- reliable macOS permission setup and recovery
- Action Capture guide editing and annotations
- batch website capture with per-URL settings
- integrated PDF, ZIP, and MP4 export workflows
Why people still pay
They want repeatable capture across Mac apps without maintaining native permission handling, automation edge cases, session history, and several export pipelines themselves.
moat: Execution quality what a moat is
native polish/permissions/workflow breadth
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Flameshot (opens in a new tab) — mature cross-platform screenshot capture, but not a timed Mac automation workflow
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
