title: UWP Performance: Task.Run() vs Background Service
body: <p>I'm working on a UWP app that is showing videos, images &amp; XAML animations. The content displayed is being updated from time to time by pushing updates from the server to the app through grpc.</p>
  
  <p>When updates happen the app will need to download new assets like potentially big video files. While this happens it is important that the UI does not get any negative impact and the fps remain stable.</p>
  
  <p>From what I've read so far it can help to wrap the download operation inside a Task.Run() instead simply awaiting the HttpClient call to not affect the UI thread.</p>
  
  <p>Would there be any additional performance improvements if I'd move the download operation to a background service altogether? Or would this be unnecessary overhead?
  (I don't need downloads to work while the app is not running.)</p>