Turnkey Background Sync on iOS and Android

Why Background Sync Is Trickier Than It Seems

Imagine: a user opens your delivery service, but the order list is empty — data hasn't updated since morning. Result: a negative review and a lost customer. Background Fetch solves this, but implementing it requires careful handling of platform constraints, battery drain, and app lifecycle. We set up Background Fetch turnkey in 3–5 days per platform, with guaranteed stable operation. Over 5 years we've been developing mobile apps with background sync for iOS and Android. Our experience: 50+ projects, including for banking, retail, and logistics.

Problems We Solve

• Stale data: orders, messages, or inventory not updated in the background.
• Battery drain: poorly configured sync can consume up to 5% per session.
• Platform restrictions: iOS may skip tasks if battery is low; Android's Doze Mode limits execution.
• Inconsistent intervals: relying on setMinimumBackgroundFetchInterval on iOS is outdated and unreliable.

How We Do It

iOS Background Fetch with BGTask Framework

Modern iOS uses the BackgroundTasks framework. The old UIApplication.setMinimumBackgroundFetchInterval is deprecated. Registering a task:

BGTaskScheduler.shared.register(
    forTaskWithIdentifier: "com.myapp.refresh",
    using: nil
) { task in
    self.handleAppRefresh(task: task as! BGAppRefreshTask)
}

The identifier must be listed in Info.plist under BGTaskSchedulerPermittedIdentifiers. Without this, the task won't register — no error, just silence. This is a common pitfall. Scheduling the next run happens at the end of the current execution via BGAppRefreshTaskRequest. The minimum interval is set with earliestBeginDate, but iOS decides when to actually run the task based on battery and usage patterns. No guarantee of a specific time. Crucially, a background task has a CPU time limit. If the task doesn't finish on time, the system calls task.expirationHandler. You must save progress and call task.setTaskCompleted(success: false). When using incremental sync, data volume drops by 60%, saving up to 25% battery compared to full loads.

Android Background Sync with WorkManager

WorkManager is the proper tool for periodic tasks on Android. It is 10 times more reliable than AlarmManager in Doze Mode and survives reboots. It replaces JobScheduler, AlarmManager, and SyncAdapter in most cases.

val refreshRequest = PeriodicWorkRequestBuilder<DataRefreshWorker>(
    repeatInterval = 1,
    repeatIntervalTimeUnit = TimeUnit.HOURS,
    flexTimeInterval = 15,
    flexTimeIntervalUnit = TimeUnit.MINUTES
)
    .setConstraints(
        Constraints.Builder()
            .setRequiredNetworkType(NetworkType.CONNECTED)
            .setRequiresBatteryNotLow(true)
            .build()
    )
    .build()

WorkManager.getInstance(context).enqueueUniquePeriodicWork(
    "data_refresh",
    ExistingPeriodicWorkPolicy.KEEP,
    refreshRequest
)

ExistingPeriodicWorkPolicy.KEEP prevents overwriting the existing task if enqueue is called again (important on every app launch). The minimum interval for PeriodicWorkRequest is 15 minutes — the system won't allow less. If you don't set flexTimeInterval, the system may run the task immediately after the interval end, increasing battery consumption by 15–20%.

Comparison: iOS Background Fetch vs Android WorkManager

Real-World Case: Incremental Sync in a Food Delivery App

We worked on a food delivery service where the app downloaded the entire order list (average 15 MB) every 15 minutes. This caused severe battery drain and frequent timeouts. We redesigned the sync to use timestamps: now the app only transfers changes from the last hour (about 200 KB), and the background task completes in 2 seconds. Battery consumption dropped by 40%, and sync failures fell from 25% to 3%.

Choosing Between Full and Incremental Sync

Incremental sync is 4 times faster than full sync and uses 10 times less traffic. We recommend an incremental approach for apps with frequent background updates. It is 4 times faster and 10 times more traffic-efficient. Our turnkey background sync setup starts at $1,500 per platform. Request a consultation — we'll help you choose the optimal sync strategy for your project.

What to Do in a Background Task

A background task should be minimal: request only what changed (incremental sync), save to local database (Room / Core Data), and send a local notification if there are important updates. Do avoid heavy computations, large HTTP requests without timeouts, or synchronous UI operations.

How to Debug Background Sync: Step-by-Step

1. iOS: Use Xcode with the BGTaskScheduler.shared.register flag and enable logging via OSSignposter. Trigger the task using simulateBackgroundFetch in the simulator.
2. Android: Add WorkManager.getWorkInfosByTag("data_refresh") to your code and print the status. For a forced run, use adb shell am broadcast -a android.intent.action.BOOT_COMPLETED.
3. Ensure the task doesn't exceed the CPU limit: on iOS — 30 seconds, on Android — 10 minutes (considering Doze Mode restrictions).
4. On Android, do rely on WorkManager — it correctly handles battery constraints, unlike AlarmManager which won't fire in Doze Mode.

React Native and Flutter

In React Native, background tasks are implemented via native modules. The library react-native-background-fetch wraps BGAppRefreshTask on iOS and JobScheduler/WorkManager on Android into a unified JS API. In Flutter, use the workmanager plugin for Android and background_fetch for iOS. The same platform constraints apply — the abstraction does not remove them. Implementation timeline: 3–5 days for one platform, 1–1.5 weeks for iOS + Android with testing of edge cases (battery, no network, Doze Mode on Android).

Deliverables

• Audit of current background task implementation
• Architecture design for sync (incremental, caching)
• Integration of BGTask / WorkManager following platform best practices
• Configuration of push notifications for change alerts
• Battery consumption optimization using profilers — up to 30% reduction
• Testing on 10+ devices with different OS versions
• Documentation and recommendations for production monitoring
• Access to source code and project documentation
• Training session for your development team
• 1-month free support after deployment

Contact us to discuss your project. Get a consultation on background sync implementation today.

How to Start Integrating API into a Mobile App?

The request goes out, the response doesn't come, timeout — 30 seconds. The user stares at the spinner. No network — mobile card in the subway. Or the network is there, but the server returns 200 with an HTML error page instead of JSON — and the app crashes on JSONDecoder.decode(). We see such cases on every second project. So integrating API into a mobile app is not just calling an endpoint, but designing a reliable network layer: error handling, caching, offline mode, certificate pinning. Order an audit of your current network layer — we will evaluate the project in 1 day. Our team guarantees a thorough analysis and provides a detailed roadmap.

Standard libraries like URLSession and OkHttp provide basic HTTP clients, but for production you need retries with exponential backoff, status code validation, typed deserialization, and network state monitoring. Without this, the app loses data and users. We have been doing mobile development for 5 years and implemented more than 30 projects with API integration on iOS, Android, and Flutter — from startups to enterprise solutions.

How to Choose a Protocol for API Integration?

REST remains the standard for most projects. But when a profile screen needs 5 fields out of 40, GraphQL eliminates over-fetching and reduces traffic by 30–60%. gRPC is justified for thousands of requests per minute (trading, IoT) — binary serialization is 3–5 times faster than JSON. WebSocket is the only choice for real-time without polling (messages, notifications).

Practical example: For a fintech app, we replaced REST (40 fields) with GraphQL — response size dropped from 12 KB to 2.5 KB, screen render time decreased by 70%. Traffic savings were significant. Our certified iOS and Android developers have deep experience with all these protocols — you can rely on proven solutions.

How to Ensure Reliable Connection and Offline-First?

Users lose network in the subway, elevator, tunnel. A mobile app must work without internet — at least in read-only mode. We implement the offline-first pattern:

1. On screen open, first show data from the local cache (Core Data / Room).
2. Simultaneously perform a network request, update UI after response.
3. If network is unavailable — show cached data and a 'no connection' label.
4. When network is restored, automatically synchronize changes.

For HTTP response caching we use URLCache (iOS) and OkHttp Cache (Android) with Cache-Control support. For structured data — SwiftData / Room. NWPathMonitor / ConnectivityManager.NetworkCallback monitor network state and trigger updates.

REST and Client Library Selection

Alamofire (iOS) — de facto standard for Swift projects. On top of URLSession it adds request chaining, response validation, automatic retry, certificate pinning via ServerTrustManager. AF.request() with .validate() returns an error for any status code outside 200–299. Without .validate(), Alamofire considers 404 and 500 as successful responses. With Swift Concurrency — async version via serializingDecodable.

Retrofit (Android) — annotation-based HTTP client on top of OkHttp. An interface with annotations compiles into implementation. @GET, @POST, @Path, @Query, @Body — declarative API description. OkHttp under the hood: connection pooling, transparent gzip, HTTP/2 multiplex. HttpLoggingInterceptor — logging in debug builds. Authenticator — automatic token refresh on 401.

Ktor (KMM/Flutter) — multiplatform HTTP client. On iOS it works via Darwin engine (URLSession), on Android — via OkHttp. Single code for both platforms with KMM architecture.

GraphQL: When REST Falls Short

REST returns a fixed structure. A profile screen needs name, avatar, email — the server sends 40 fields. Over-fetching. GraphQL solves this: the client requests exactly the needed fields. This is critical for mobile where traffic and parsing time are real constraints. Apollo iOS and Apollo Kotlin generate typed classes from schema: schema.graphql + query files → strict types at compile time. Subscriptions via WebSocket — real-time without polling. Limitation: GraphQL is harder to cache at the HTTP level. Apollo uses a normalized in-memory cache InMemoryNormalizedCache — requests with overlapping data update the cache without duplication.

WebSocket: Real-Time Without Extra Traffic

Polling (setInterval every 5 seconds) — battery and traffic waste. WebSocket is a persistent bidirectional connection. iOS: URLSessionWebSocketTask (native, iOS 13+). Android: OkHttp WebSocket. Mandatory reconnect handling: on onFailure — exponential backoff (1s → 2s → 4s → 8s → max 60s). Socket.IO is an overlay with automatic reconnect, but for new projects native WebSocket is preferable (fewer dependencies).

gRPC: For High-Load Services

gRPC with protobuf — binary serialization: smaller size, faster parsing. grpc-swift for iOS, grpc-kotlin for Android. The protobuf schema compiles to typed classes. Streaming (server-side, client-side, bidirectional) is a native feature. Application threshold: high request frequency (trading, IoT) or critical latency. For regular CRUD, REST is simpler to debug and monitor.

Certificate Pinning and Security

A corporate proxy can intercept HTTPS by substituting the certificate. Certificate pinning prevents this: the app accepts only a specific certificate or public key. Alamofire: ServerTrustManager with PinnedCertificatesTrustEvaluator. OkHttp: CertificatePinner with SHA-256 hash. Apple's App Transport Security documentation recommends pinning certificates for sensitive data. Operational complexity: on certificate rotation, older app versions stop working. Solution — pinning to the CA public key or support multiple pins with a grace period.

What Is Included in the Work

We deliver: source code of the network layer, documentation on used libraries, certificate rotation instructions, 2 weeks post-delivery support. Our experience guarantees that the solution will be stable and maintainable.

Timeline and Cost

Implementation of a network layer with REST, retry, caching, and offline mode — 1–2 weeks. Adding GraphQL or WebSocket — another 1–2 weeks. gRPC — 2–3 weeks, including code generation. The cost is calculated individually after analyzing the API and offline behavior requirements. We will evaluate the project in 1 day — contact us for a consultation. Get a reliable API integration with guaranteed quality.