On 24 February 2011 11:11, Dudero <[email protected]> wrote: > I have heard that an Activity must not contain UI - so is in some > cases an Activity a better solution than a Service?
That's quite misunderstanding of basics. Is wheel better than bucket? > Can anybody give me an example for a useful case of an Activity > without UI? In general if you do not need UI you may not need to extend Activity but instead create "pure" class for your job. However it may be that extending Activity gives you access to certain resources/methods you need. But this still does not mean you have to create or show UI. Depending on evaluation you may do your job in onCreate and i.e. invoke other activity -- Regards, Marcin -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
