Definition

What is on-device processing?

On-device processing means data is handled locally on the user's device rather than sent to remote servers.

Last updated: 2026-05-09

gh repo clone ReScienceLab/SnapAction
Short answer

On-device processing handles data locally on the device. SnapAction stores resource cards locally with SwiftData, though AI analysis requires backend processing.

On-device processing means data is handled locally on the user’s device rather than sent to remote servers.

What SnapAction does on-device

What requires backend processing

Why the split matters

Local storage keeps your resource library fast, available offline, and under your control. Backend processing is required for the AI analysis that turns screenshots into structured cards. SnapAction is transparent about this split and does not claim fully offline AI analysis.

How to evaluate privacy claims

On-device processing is a specific architecture claim. A product should be clear about which steps happen locally and which steps require a server, model provider, search provider, identity provider, or subscription system. Saying “local” is not enough if important parts of the workflow still leave the device.

For screenshot tools, the distinction matters because screenshots may contain private messages, receipts, travel details, work documents, or account information. Users should know whether the app stores the library locally, whether AI analysis is remote, and which screenshots they should avoid scanning.

Sources

FAQ

What is On-device processing?

On-device processing handles data locally on the device. SnapAction stores resource cards locally with SwiftData, though AI analysis requires backend processing.

Why does On-device processing matter?

On-device processing matters because sensitive inputs can be analyzed locally, which can reduce latency and avoid unnecessary server upload.

Next step

Turn iPhone screenshots into action-ready resource cards with AI.

View on GitHub