How to Handle Large File Uploads in Android Using WorkManager & Foreground Services

What is WorkManager: WorkManager is the recommended solution for persistent work. It doesn’t magically prevent the OS from killing your app. Instead, it guarantees Reliable Execution. Even if your app is killed or the device reboots, WorkManager remembers your task (saved in its local SQLite DB) and executes it when the required constraints are met.

Usecase: App uploads a large movie file (50MB) (※ Assume we already implemented a resumable upload mechanism)

1. User taps the upload button.
2. App creates a WorkRequest with specific Constraints (e.g., NetworkType.CONNECTED) and enqueues it to WorkManager.
3. Once the constraints are met, the WorkManager spawns a background thread and starts the Worker.
4. [Crucial Step] Inside the Worker, we call setForegroundAsync() to bind the task to a Foreground Service. This displays a sticky notification to the user.
5. The user puts the app into the background.
6. Because of the Foreground Service, the OS recognizes this as a high-priority active task and heavily reduces the chance of killing the process.
7. The upload process safely continues in the background.
8. The user brings the app back to the foreground.
9. The UI observes the WorkInfo (via LiveData or Flow) and seamlessly updates the progress bar based on the Worker's state.

Key Takeaways (Points):

1. The 10-Minute Limit: Standard background Workers are subject to OS restrictions and can be killed after roughly 10 minutes. By explicitly using a Foreground Service (Long-running workers), we bypass this limit for large file uploads.
2. Deferrable Execution: For standard tasks, the OS (via JobScheduler under the hood) intelligently decides the exact timing to execute the work to optimize battery life.
3. Powerful Constraints: You can set preconditions like setRequiresCharging(true) or setRequiredNetworkType(NetworkType.UNMETERED) so the upload only happens on Wi-Fi, saving user data.
4. Built-in Resiliency: WorkManager handles failures gracefully. It has a built-in Exponential Backoff mechanism (setBackoffCriteria), eliminating the need to write complex retry loops manually.