On Wed, May 9, 2012 at 2:48 PM, Kostya Vasilyev <[email protected]> wrote:
> Regarding this being an anti-pattern, I'm not sure I fully agree with the > widespread opinion on higher battery consumption. > The bigger issue is RAM use. There just isn't a lot of RAM available on many of these devices, and they can't afford to have tons of apps sitting around consuming it all of the time. We don't use paging so even if they are sitting there not doing anything their dirty pages can't be paged out. > But it's the user's perception that matters here, and it's very much > against long running services, to the point where I'm sometimes asked why > there are three (!!!!!) services in my app, and wouldn't it be better to > use one to reduce memory usage by a factor of three, obviously (the answer > is no... since the services are sharing the same process). Wow... well hopefully that is from people seeing the older Running Services UI that made the separate services much more up-front, rather than the current one which is much more process-oriented. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
