[verdict][curated prompt][source: capture.sir.studio]
Can I vibecode Capture - Quick Notes?
// buildable in a weekend, but real gaps stay open
The core capture inbox is a weekend build: everything runs on public Apple frameworks, so SwiftData plus CloudKit sync, a share extension, and a menu bar capture window cover the loop on iPhone and Mac. What is not a weekend is Capture's real surface: five Apple platforms and a catalog of 40+ destination exporters whose URL schemes, APIs, and content rules shift independently. Build the two-platform inbox with a handful of exporters you actually use and it is genuinely yours; chase full parity and you have signed up for the maintenance.
confidence: medium
what it is: Catch notes, links, images, and files now, then send them to the app where they belong
Buildability index · an editorial game
- Price one-time weight: zero
- Time multi-day weight: plus 1
- Category notes and knowledge no weight
- Moat execution quality · integrations weight: minus 2
- Confidence medium weight: zero
- What you lose 5 items weight: minus 2
- Site capture.sir.studio (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Catch text, links, images, and files on iPhone and Mac, sync them through your private iCloud, organize them into lists, then send each item on to the apps you actually use via destination-specific export actions.
what you need
- Xcode
- Apple Developer account for iCloud and App Group entitlements
Submitted by Capture's maker. The entry uses the US lifetime purchase and covers the complete multi-platform capture and export workflow.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build me a native quick-capture inbox for iPhone and Mac to replace Capture. Requirements:
- Swift 6 + SwiftUI, one Xcode project: an iOS app and a macOS menu bar app sharing a
Swift package for the model, persistence, search, and export logic. SwiftData for
storage, synced through my private CloudKit database.
- A capture is text, a URL, an image, or a file, with a list, archive state, and
created/edited dates. Run NSDataDetector on text so URLs, phone numbers, and dates
become tappable.
- iOS: a share extension so anything can be sent in from any app, plus a WidgetKit
widget for one-tap capture. Mac: a menu bar item with a global hotkey opening a
compact capture window.
- Inbox, Archive, and lists, with full-text search and undoable archive/delete. JSON
export of everything so my notes are never trapped.
- Export actions for the destinations I actually use: Reminders and Calendar via
EventKit, a Mail draft, Things and Bear via their URL schemes, and copy-as-Markdown.
One small adapter file per destination so more are addable later.
- Offline-first: SwiftData writes locally and CloudKit retries when back online.
Last-write-wins conflict handling is fine, say so in the README.
- No accounts, no telemetry, nothing leaves my devices except private iCloud sync and
the exports I trigger.
- Out of scope: Apple Watch and Vision Pro apps, and Capture's 40+ destination catalog.
Keeping that many exporters alive is the paid product's job, not mine.
- README: the entitlements to enable (App Groups, iCloud/CloudKit), and a plain warning
that CloudKit sync needs a paid Apple Developer account.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
- App Store-ready polish across iPhone, iPad, Mac, Apple Watch, and Apple Vision Pro
- years of CloudKit migration, conflict, and offline-sync edge cases
- ongoing maintenance for more than 40 destination-specific export integrations
- the localization, accessibility, and device test matrix
- fast compatibility updates when Apple or a destination app changes behavior
Why people still pay
People buy Capture to avoid maintaining the same workflow across Apple's platforms. The one-time purchase includes iCloud sync, deep system integration, and more than 40 third-party export destinations whose URL schemes, APIs, Shortcuts, and content rules can change independently.
moat: Execution quality Integrations what a moat is
maintenance across Apple platforms, CloudKit, system integrations, and more than 40 destination-specific exporters
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- FSNotes (opens in a new tab) — Open-source notes manager for macOS and iOS with plain-text storage.
- NoteTaker (opens in a new tab) — Open-source Swift notes app for macOS and iOS with CloudKit sync.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
