Reliable Background Data Upload in Mobile Apps

We often encounter the task of background data upload in mobile apps. Imagine: a user selects 20 photos, minimizes the app, and waits for a notification. A naive implementation—upload is interrupted, data is lost, the user gets no result. Proper architecture allows the upload to continue even after the app is killed by the system. The user receives a "Upload complete" notification 10 minutes after minimizing. Below, we break down how to implement a reliable mechanism on iOS and Android using URLSession background configuration, WorkManager, and Foreground Service.

Why is background upload harder than it seems?

Many developers use regular network requests for background upload. But the system can kill the app at any moment, and data is lost. In 95% of cases, this leads to data loss and user dissatisfaction. The main issues: iOS supports only URLSession background, and you need to restore the session. On Android, WorkManager struggles with long tasks without Foreground Service.

How does background upload work on iOS?

According to Apple Developer Documentation, URLSession background configuration is the only way for background upload on iOS. Only such a session continues working after the app goes to background or is terminated.

let config = URLSessionConfiguration.background(
    withIdentifier: "com.myapp.upload.\(UUID().uuidString)"
)
config.isDiscretionary = false  // upload immediately, not deferred
config.sessionSendsLaunchEvents = true  // wake app on completion

let session = URLSession(
    configuration: config,
    delegate: self,
    delegateQueue: nil
)

For background upload, use only uploadTask(with:fromFile:). Save the data to a file beforehand. uploadTask(with:from:) with Data does not work in the background—data is lost on restart.

Note: when upload completes or the app is killed, iOS calls application(_:handleEventsForBackgroundURLSession:completionHandler:) in AppDelegate. You need to restore the session with the same identifier and call the completionHandler after processing events. Mistake: creating a new session with a new identifier on each launch—events will be lost.

Tracking progress and notifications on iOS

Upload progress is obtained via the delegate urlSession(_:task:didSendBodyData:totalBytesSent:totalBytesExpectedToSend:). In the background, you cannot update the UI, so show progress via UNMutableNotificationContent with progress. On completion, send a local notification:

let content = UNMutableNotificationContent()
content.title = "Upload complete"
content.body = "20 photos uploaded successfully"
let request = UNNotificationRequest(
    identifier: UUID().uuidString,
    content: content,
    trigger: nil
)
UNUserNotificationCenter.current().add(request)

How does background upload work on Android?

On Android, we use WorkManager with CoroutineWorker. For large files, we implement chunking: the file is split into parts, each uploaded with a separate request containing the Content-Range header. If the upload is interrupted, we resume from the last successful chunk.

class UploadWorker(context: Context, params: WorkerParameters)
    : CoroutineWorker(context, params) {

    override suspend fun doWork(): Result {
        val filePath = inputData.getString("file_path") ?: return Result.failure()
        return try {
            uploadFile(File(filePath))
            Result.success()
        } catch (e: Exception) {
            if (runAttemptCount < 3) Result.retry()
            else Result.failure()
        }
    }
}

runAttemptCount + Result.retry() — automatic retries on failure with backoff strategy. Set the maximum number of attempts: optimally 3-5.

Why is Foreground Service needed for large files?

For uploading large files (videos, archives) on Android, ForegroundService is mandatory—the system will not kill the process while the service shows a notification. WorkManager can delegate the task to Foreground via setForeground(). On Android 14+, ForegroundService type dataSync requires an explicit permission in the manifest. This increases upload success rate to 99% even with unstable connections.

Comparison of iOS and Android approaches

Step-by-step: configuring retries in WorkManager

1. Set the maximum number of attempts in configuration: setBackoffCriteria(BackoffPolicy.EXPONENTIAL, Duration.ofSeconds(10)).
2. Use runAttemptCount in doWork(): if attempts are below the threshold, return Result.retry(), otherwise Result.failure().
3. Configure backoff strategy: linear for frequent small uploads, exponential for rare large ones.

What is included in background upload implementation?

Our experience and guarantees

Our team has over 10 years of experience in mobile development and has implemented over 50 projects with background upload. For a social media app with 20 MB average uploads, we implemented iOS background URLSession and Android WorkManager with Foreground Service. Result: 99.8% upload completion rate even with frequent app backgrounding. We guarantee that your app will handle background upload correctly even with unstable connections. Native implementation via URLSession background configuration is 10 times more reliable than using standard URLSession in the background, and guarantees upload completion even if the app is killed.

Timelines: basic background upload—from 1 week. Complete solution with chunking, retry logic, and notifications—from 2 to 3 weeks. Contact us to evaluate your project—we will prepare a proposal within 1-2 days. Order a turnkey background upload implementation.

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.