text: Q:
  
  What to use: service or threads
  
  I am developing an android app which fetches/uploads data from/to the web service every n minutes. This upload/download is only done when the app is running. But this might change in future.
  I dont update the UI when the new data is downloaded. The UI is only updated if the user is on the current screen(app have multiple activities) 
  My question is what is the best approach to this problem.
  I dont think service is the right approach as it sounds like an overkill(in the present scenario). AlarmManager could be an option.
  Running threads inside a service be an option ..something like this .
  Any pointers/suggestions would be great.
  Thanks
  
  A:
  
  I am using AsyncTask in my activity to ask .net web service some information and it works and easy to use.
  
  AsyncTask enables proper and easy use of the UI thread. This class allows to perform background operations and publish results on the UI thread without having to manipulate threads and/or handlers.
  
  