The architectural decision behind an app's speed, your privacy, and the subscription price you end up paying.
When you press "remove background" in a photo app, one of two things happens: the image is processed inside your phone, or it's uploaded to a remote server and the result comes back. The difference between those two paths reaches into speed, privacy, cost, and what happens when the connection drops.
On-device processing
Everything happens locally: the computation, the storage and the result.
Advantages:
- Privacy: what is never sent can't leak from a server or be used to train a model.
- Speed: no upload or download time. On small tasks the difference is decisive.
- Always works: on a plane, on a train, on a weak connection.
- No recurring cost: which is why local tools are often a one-time payment while their cloud equivalents are subscriptions.
Limits: bounded by your device's processor and memory. Very heavy tasks become slow or impossible on mid-range hardware. Embedded models inflate the app's size. And there's no automatic sync between your devices and no backup if the device is lost.
Cloud processing
Data is sent to a server that does the work and returns the result.
Advantages:
- Practically unlimited capacity: large models that could never run on a phone.
- Identical results on every device, however modest.
- Sync and backup across devices automatically.
- Instant improvement: the provider improves the model and you benefit without updating the app.
Limits: your data leaves your device, you need a stable connection, you usually pay a subscription because servers cost the provider every month, and you become dependent on the service continuing: if it shuts down, the app stops.
Comparison
| Criterion | On-device | Cloud |
|---|---|---|
| Privacy | Highest | Depends on the provider |
| Works offline | Yes | No |
| Heavy task capability | Limited by hardware | High |
| Cross-device sync | Manual | Automatic |
| Typical pricing | One-time payment | Subscription |
| Longevity | Guaranteed while installed | Tied to the service surviving |
How to tell which one you're using
- Turn on airplane mode and try the feature. If it works, it's local.
- Watch the latency: a consistent delay on every operation suggests a round trip to a server.
- Read the data safety section on the store listing; cloud apps usually declare collecting files or photos.
- A mandatory account is a strong hint of cloud processing or storage.
The practical rule
Choose local processing for sensitive data: personal photos, documents, invoices, medical or financial notes. Choose the cloud when computing power is the point itself, or when you need sync across several devices.
Many good apps combine the two: process locally by default, and offer a cloud option for cases that exceed the device's capability — as long as that's an explicit choice you make, not something happening in the background without telling you.
Written for the Store of Apps blog. Corrections and feedback: contact@storeofapps.com.