What's the best approach for running background API calls similar to Gmail?

Other Questions Gmail
1

I’m trying to figure out how to make API calls in the background and show notifications based on the data received. Right now I’ve set up a service for handling these calls but I’m not sure if it’s the best way to go about it.

Here’s a simplified version of what I’ve done:

class BackgroundApiService : Service() {
    private var isRunning = false

    override fun onStartCommand(intent: Intent?, flags: Int, startId: Int): Int {
        if (!isRunning) {
            isRunning = true
            startApiCalls()
        }
        return START_STICKY
    }

    private fun startApiCalls() {
        // Use coroutines to make API calls every 10 minutes
        GlobalScope.launch(Dispatchers.IO) {
            while (isRunning) {
                fetchDataFromApi()
                delay(10 * 60 * 1000)
            }
        }
    }

    private fun fetchDataFromApi() {
        // Make API call and show notification if needed
    }
}

I’ve added the necessary information to the manifest and I start the service from an activity. The issue I’m facing is that this approach creates a persistent notification that cannot be dismissed. Could there be a better method to perform background API calls without running into this persistent notification problem? Perhaps using WorkManager or another solution could improve this?

2

After exploring several methods for managing background API calls, I found that offloading these tasks to the cloud can significantly reduce device workload. In my experience, integrating Firebase Cloud Functions with Firebase Cloud Messaging offers a robust solution since the Cloud Functions handle the periodic API calls while FCM is used to alert the app of any new data. This approach avoids the pitfalls of a persistent service on the device and provides a scalable, maintenance-friendly alternative.

Considering local processing, WorkManager can also be an effective solution if cloud integration is not ideal.

3

I’ve had a similar challenge in one of my projects, and I found that using WorkManager was indeed a more elegant solution. It offers better battery optimization and handles device restarts gracefully.

Here’s what worked for me:

I created a Worker class that handles the API calls. Then, I set up a periodic work request with a 10-minute interval. WorkManager takes care of running these tasks in the background without the need for a persistent service.

One thing to keep in mind is that WorkManager might not run exactly every 10 minutes due to battery optimization. If you need precise timing, you might want to combine it with Firebase Cloud Messaging for immediate notifications.

Also, don’t forget to handle potential network issues and implement proper error handling in your Worker. It’ll make your app more robust and user-friendly in the long run.

Hope this helps! Let me know if you need any more details on implementation.

4

hey mate, workmanager’s pretty sweet for this kinda thing. it handles background tasks nicely without messin with battery life. you can set it up to run your api calls every 10 mins or so. no need for a persistent service or annoying notifications. just make sure to handle network hiccups and you’re golden. give it a shot!