The motivation for this was (perhaps erroneously) the idea that sometimes the users would see one process being heavy on battery, want to kill it, and then still be left with the other app, because presumably the app does two disparate things that aren't really logically related. However, that seems obviously contrived to me..
kris On Tue, May 29, 2012 at 7:32 AM, Mark Murphy <[email protected]> wrote: > On Tue, May 29, 2012 at 7:29 AM, Put_tiMe <[email protected]> wrote: >> i.e. I don't want to do IPC. > > Then get rid of your second process, and run your entire app as one > process. Your users will thank you for not wasting their RAM and > battery by having a second process that you do not really need. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > Android Training in NYC: http://marakana.com/training/android/ > > -- > 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 -- 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
