File Download Implementation in Mobile Apps

File Download Implementation

in Mobile Apps

File download is more than just an API call. Distinguish between two fundamentally different scenarios: fast retrieval of small resources (images, documents up to 10 MB) directly in memory, and downloading large files (videos, archives up to 10 GB) with progress indication and resume capability. In 80% of apps, file download functionality is necessary. Mixing these approaches is a common mistake that leads to OOM crashes or a hanging indicator with no feedback. We've implemented this logic in 50+ projects over 10 years on the market—we guarantee stable operation even on low-end devices.

How to Avoid OOM When Downloading Large Files?

The main cause of OOM is attempting to load the entire file into memory. For files >10 MB always use streaming write to disk. On Android—OkHttp with ResponseBody.byteStream() and writing to a file via FileOutputStream in a background coroutine. On iOS—URLSession.downloadTask saves to a temporary file automatically. For Flutter—dio with receiveTimeout option and writing via File. In practice, OOM occurs when downloading files >50 MB without buffering.

Why Progress Bar May Not Work?

The progress bar shows correct percentages only if the server returns the Content-Length header. If missing, the indicator will just spin without numeric value. In such cases you can show an indeterminate progress (activity indicator) or download the file in chunks via Range requests if the server supports resume. Over 30% of servers do not send Content-Length, so test against a real backend.

Mobile File Download by Platform

Compare approaches on three main platforms:

Android. For in-memory download—OkHttp or Retrofit with ResponseBody.byteStream(), write data to file in an IO coroutine. For large files, system DownloadManager with notification in status bar—user sees progress even after leaving the app. DownloadManager is 2x more efficient than a custom download service for large files. Alternative—WorkManager with custom Worker if more control is needed.

Saving to Downloads folder on Android 10+: use MediaStore API for public files, getExternalFilesDir() for private ones. Attempting to write directly to /sdcard/Download/ without MediaStore on modern versions will throw SecurityException.

val request = DownloadManager.Request(Uri.parse(url))
    .setTitle(fileName)
    .setDestinationInExternalPublicDir(Environment.DIRECTORY_DOWNLOADS, fileName)
    .setNotificationVisibility(DownloadManager.Request.VISIBILITY_VISIBLE_NOTIFY_COMPLETED)

val downloadId = downloadManager.enqueue(request)

iOS. URLSession.downloadTask saves to a temporary file, after which you need to move it to FileManager.default.urls(for: .documentDirectory). For background downloads—URLSessionConfiguration.background(withIdentifier:) with delegate URLSessionDownloadDelegate. Without a background session, download stops when the app goes to background.

let config = URLSessionConfiguration.background(withIdentifier: "com.app.download")
let session = URLSession(configuration: config, delegate: self, delegateQueue: nil)
let task = session.downloadTask(with: URL(string: url)!)
task.resume()

Implement urlSession(_:downloadTask:didFinishDownloadingTo:) to move the file and urlSession(_:downloadTask:didWriteData:totalBytesWritten:totalBytesExpectedToWrite:) for progress.

Flutter: package dio with onReceiveProgress, saving via path_provider. For background download—flutter_downloader, which wraps native DownloadManager (Android) and URLSession (iOS).

Details Often Overlooked

A file may download partially due to disconnection. Resumable download via Range header (Range: bytes=1048576-) works only if the server returns Accept-Ranges: bytes and Content-Range. If server does not support it, download starts over. Before implementing resume, test backend behavior—this can save up to 30% download time on unstable connections. On average, 15% of download attempts fail on mobile networks, so proper error handling is critical.

Also important to show real progress, not deterministic. If Content-Length header is missing, progress bar will spin without percentages. In that case, better use an indeterminate indicator.

Work Process

1. Requirements analysis: what files, max size, need resume and background download.
2. Stack selection: DownloadManager or URLSession background with configuration.
3. Design: storage scheme, error handling, progress dialog.
4. Implementation: coding with platform specifics (ProGuard/R8, App Transport Security).
5. Testing: on real devices with varying network speed and interruptions.
6. Deployment: publish to App Store and Google Play with crash log debugging.

Typical Download Errors

• Downloading on main thread—guaranteed ANR on Android.
• Ignoring Content-Type—file may be saved without extension.
• Not cleaning temporary files—Documents & Data grows.
• Not releasing URLSession after background task on iOS—memory leak.

What's Included in the Work

We select the approach for the task (in-memory vs file, foreground vs background), implement progress, saving to the desired directory, network error handling, and temporary file cleanup. We handle download end-to-end with all platform specifics—from App Store Review Guidelines to ProGuard rules.

Timeline: 1–3 days depending on requirements for resume and background behavior. Our basic implementation starts at $500, with complex projects averaging $850. This saves you up to 40% compared to in-house development. Contact us to evaluate your project—write to us, we'll propose an optimal solution considering your stack.

Documentation: URLSession Programming Guide, DownloadManager Reference

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.