Is it better to use AsyncTask (Or Timer) within single process, or using Service in separate process?
<p>I just read <a href="http://mindtherobot.com/blog/37/android-architecture-tutorial-developing-an-app-with-a-background-service-using-ipc/" rel="nofollow">Android Architecture Tutorial: Developing an App with a Background Service (using IPC)</a>. It is basically</p>

<ol>
<li>Have a service run in separate process.</li>
<li>A repeated timer event will occur in the service.</li>
<li>Within the timer event handler, it will perform networking to retrieve tweet, and inform all the listener attached to it. Listeners are attached to it through IPC.</li>
</ol>

<p>I can see there are 2 major characteristics with this approach.</p>

<ol>
<li>Tweet retrieving action run within separate process.</li>
<li>It always run, even the main activity has quit.</li>
</ol>

<p>However, if "<strong>It always run</strong>" is not my requirement. I want everything to stop when I quit my main Activity. </p>

<ol>
<li>Will it be better, if I use <code>AsyncTask</code> (Or <code>Timer</code>) within my main Activity, to perform tweet retrieving action? Everything will be run within single process. No more using <code>Service</code>.</li>
<li>Using AsyncTask (Or Timer), seems simpler. We no longer need to deal with IPC.</li>
<li>Or, using <code>Service</code> approach might be better? Am I missing some goodies provided by Service?</li>
</ol>
