Why resource cards are different from screenshots
A screenshot preserves pixels. A resource card preserves intent. If the screenshot represents a GitHub repo, event, invoice, place, product, travel booking, or article, the card can store the type and fields that make that resource useful later.
In SnapAction, resource cards are stored locally with SwiftData after cloud-assisted AI analysis. Cards can keep titles, URLs, tags, descriptions, metadata, read/favorite state, and references back to the screenshot asset IDs.
Example card fields
GitHub card: title, canonical URL, tags, description, source screenshot, and Open action.
Event card: event title, date/time, location, notes, screenshot group, and Add to Calendar action.
Invoice card: vendor/title, amount, invoice number, screenshot reference, and copy actions for extracted fields.
How SnapAction creates resource cards
- PhotoKit reads selected or recent screenshot assets.
- A Convex-backed AI agent analyzes the screenshot through OpenRouter.
- Serper search can recover canonical URLs when a visible title or name is enough.
- SnapAction saves the resource, metadata, tags, scan records, and screenshot references locally with SwiftData.