What Kevin said plus… It’s reasonable to use different approaches for different subsystems in your app. For example: If you’re fetching an audio file to play immediately, a standard session is probably best. Critically, it results in the least latency, which is important because you’re actively playing that audio. And while this requires your app to not suspend, that’s OK because you’re playing audio. If you’re downloading a large file that the user isn’t actively playing, a background session makes sense. If you’re scanning for updates, you could use a background processing task. This typically runs overnight, which is fine because the user isn’t expecting the results immediately. Unless they bring your app to the foreground and tap the refresh button, in which case you might run the same code immediately. And you can then use a continued processing task to complete the refresh. But that’s just one way to slice this. You have lots of options and it’s kinda up to you to decide which
Topic:
App & System Services
SubTopic:
Networking
Tags: