Background Sync on Mobile: Keeping Data Fresh Without Draining the Battery
Short answer: Phones limit background work on purpose, to protect battery life, so an app cannot count on refreshing itself at exact intervals. Instead, decide what each screen truly needs to be current, then match that need to the tool the platform offers: a push message when the data changes, a scheduled refresh the system may delay, or a manual refresh the user triggers. Write a freshness target for each screen, test it on a real phone with the battery saver switched on, and keep the sync small. Most battery complaints come from frequent full downloads, not from the sync itself.
Why the phone decides when you run
Both iOS and Android decide when background work happens. The operating system looks at battery level, how often the user opens the app, whether the phone is charging and whether the network is available. An app that asks to run every five minutes may get a few runs a day, and a rarely opened app may get almost none. The platform is protecting the user, and your plan should accept that.
This is why a field-staff app that depends on exact timing will disappoint. Design around what the platform reliably offers.
What each platform allows
The details change between operating system versions, so check the current developer documentation. In general terms:
- iOS offers background refresh for apps that the user has allowed to refresh, with the system choosing the timing. Background tasks are scheduled, not guaranteed, and the system may skip them when resources are low. Push notifications can also wake an app briefly to fetch content, within limits.
- Android offers scheduled background work with minimum intervals and constraints, such as needing a network or a charging phone. Battery optimisation settings can restrict apps further, and users sometimes turn those settings on without knowing what they affect.
Neither platform promises a precise schedule, so treat background sync as a way to improve freshness, not a clock.
The three sync options
Most apps combine three approaches:
| Approach | How it works | Best for | Main limit |
|---|---|---|---|
| Push-triggered | Server sends a message when data changes, the app fetches the change | Job assignments, order status | Needs a reliable push setup and a server event |
| Scheduled | System runs a refresh at intervals it chooses | Background pre-loading, daily summaries | Timing is approximate and may be skipped |
| Manual | User pulls to refresh or taps a button | Any screen where the user is already looking | Relies on the user, so data may be stale until they act |
The right mix depends on the screen. A dispatch screen for a plumbing crew needs push-triggered updates. A weekly report for an owner can use a scheduled refresh. A parts catalogue can rely on manual refresh, plus a sync on opening the app.
A freshness specification
Write a short specification that states how fresh each screen must be. This turns a vague wish into a testable rule. Use a table like this:
| Screen | Data | Freshness target | Sync method | Acceptable delay |
|---|---|---|---|---|
| Today's jobs | Assigned jobs and times | Within 1 minute of change | Push, plus fetch on open | 5 minutes if push fails |
| Customer notes | Notes added by office | On open | Fetch on open | Not critical |
| Stock levels | Parts on hand | Within 30 minutes | Scheduled, plus manual refresh | 1 hour |
| Weekly summary | Totals for last week | Once daily | Scheduled | 24 hours |
Notice how the table prevents over-engineering. Only one screen needs near-instant data, so only one screen needs push. The rest can be satisfied with cheaper methods.
Why sync drains batteries
Battery drain usually comes from work done in the wrong place or at the wrong time:
- Full downloads. Fetching the whole dataset each time uses far more power than fetching only the changes.
- Frequent wake-ups. Many small requests spread across the day keep the radio busy.
- Location polling. Checking location constantly is one of the biggest drains of all.
- Retry loops. An app that retries a failed request every few seconds can burn a battery overnight.
Fix these before you reduce the sync frequency. Use changed-data fetches with a timestamp or a version number. Batch requests. Back off after failures, waiting longer each time. Request location only when a feature needs it, and stop it when the task ends.
A worked example: a cleaning crew's app
A small cleaning business has crews working across the city. The office assigns jobs during the morning. The crew needs their list to update when the office changes it, but they do not need to see every stock or report update.
The team sets up push for the job list, so a change reaches the crew's phones within a few seconds when the server is reachable. The app also refreshes the job list when a crew member opens it. The stock screen uses a manual refresh button plus a background refresh every hour, and the weekly summary uses one scheduled refresh each morning. The result is a fresh job list with modest battery use, and no complaints about the phone running hot.
Testing on real devices
Test with the realistic settings your crews will use:
- Turn on the phone's low power or battery saver mode, and check whether syncs still happen.
- Run a full day on a single charge, noting battery use per hour in the app's settings screen.
- Test with the network dropping and returning, to confirm the app recovers without retry storms.
- Check the data after a long period in the background, such as overnight.
- Confirm that the app shows the last-updated time, so users know how fresh the data is.
Communicating freshness to users
Show the last-updated time on screens where freshness matters. A line such as "Updated 3 minutes ago" tells people what to expect. A pull-to-refresh control and a clear empty state help people recover when the data is old. Users forgive a delay they can see, but they lose trust in an app that shows stale data without saying so.
FAQ
Can I make the app sync every minute in the background?
Not reliably. The platform decides the timing. Use push for time-critical data and accept that scheduled refresh is approximate.
Will users notice if I turn background refresh off?
They may. Explain the benefit in the app, and let the user choose. An app that ignores the setting and drains the battery will get worse reviews than one that asks politely.
Does syncing cost data plans?
It can. Keep downloads small, avoid large images in background syncs, and let users decide whether to sync over mobile data for heavy content.
Who should write the freshness specification?
The person who owns the screen's workflow, with the developer. The owner knows how stale data can be before it causes a mistake, and the developer knows what the platform will allow.
If you want help setting freshness targets and a sync plan for your field app, tell us which screens your staff use most and what goes wrong when the data is out of date, and we will work through it with you: get in touch.