For example, having a foreground services shows some sort of intent that users want the app to be running continuously. If the user force kills an app with a foreground service, that just seems dumb, since they should have just stopped it using the facilities of that app anyway :-/, but I guess none of that use case makes sense anyway.
kris On Thu, Oct 17, 2013 at 9:07 AM, Kristopher Micinski <[email protected] > wrote: > On Thu, Oct 17, 2013 at 2:57 AM, Piren <[email protected]> wrote: > >> A foreground service is sort of the way you build apps that live >>> indefinitely. >>> >> I wouldn't say that, foreground services die like everything else... they >> are persistent little buggers, but it doesn't take much to get rid of them. >> Especially for the app-killer-click-happy users that think it helps their >> device go faster. >> > > So I should say that they are "morally" how you build services that last > indefinitely. Since indefinite services don't really exist, they are as > close as you can realistically get.. > > kris > > -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
