title: android.app.Application vs android.app.Service
body: <p>I am writing an android application that uses location.LocationManager and LocationListener to receive GPS location updates. The application updates the location on a MapActivity and sends the co-ordiantes to a restful web service.  The web service needs to receive location updates even when the MapActivity is not visible to the user. </p>
  
  <p>At the moment i am doing everything (apart from UI) within app.Application as it stays active even when the MapActivity is not visible. However, all the documentation i have read suggests that app.Application is used to store state rather than carrying out more demaning tasks. I have tried using app.Service, but it seems to be over complicated (life-cycle, binding, unbinding)  and has many memory leak problems. I haven't been able to find any articles or documentation that explicitly forbids carrying out these kind of tasks from app.Application, so i was wondering if there is anything wrong with this approach?     </p>
  
  <p>Edit: Thanks for the replies, looks like i am going to have to spend a bit more time figuring out app.Service </p>