Android: AsyncTask recommendations: private class or public class?
I'm currently developing some Android Apps in a team and we've used 2 different approaches during the last months (one that i personally prefere, and the other that the other developer prefers).


Although so far the results are the same, this got me wondering...should we: 

 - use AsyncTasks as private classes inside the Activities that use them. 
 - or use AsyncTasks as separate public classes that receive the context of the activity


Are any of the approachs recommended by Google? 

What does your experience say about this (advantages, disadvantages, problems)?
Android: AsyncTask recommendations: private class or public class?
===

I'm currently developing some Android Apps in a team and we've used 2 different approaches during the last months (one that i personally prefere, and the other that the other developer prefers).


Although so far the results are the same, this got me wondering...should we: 

 - use AsyncTasks as private classes inside the Activities that use them. 
 - or use AsyncTasks as separate public classes that receive the context of the activity


Are any of the approachs recommended by Google? 

What does your experience say about this (advantages, disadvantages, problems)?