An interesting question, although framed a little on the loaded side. On to that first: Based on the expected functionality, it might be necessary to keep app functionality running in the background, there is no "choice" in the first place. As an example, if an app has a function that allows users to set an alarm that shall be triggered when a condition is met at some unknown time in the future, like nearing a particular place, then obviously a Service or other background function needs to be kept running that monitors whether the condition is met. This concept allows users to navigate away from the app and do other stuff, like reading an e-book. Then there might be "evil" functionality in place, like monitoring the device location and the capturing of other analytics. One other driver to use Services data storage that survives an app losing focus. The apparent argument here would be that that's the intention of the user when exiting an app anyway, but there's a wrinkle to it. One of the major design flaws (IMO) in the Android SDK is in the area of how device orientation changes are handled. When the orientation changes from portrait to landscape (and vice-versa), Android completely breaks down an app and restarts it. If an app holds substantial amounts of data, one way of making this data available immediately after restart, without copy-and- forward or store-and-retrieve acrobatics, is to keep the relevant data in a Service and reconnect to the Service after the app has been restarted.
On Nov 7, 3:14 am, appel <johan.appelg...@gmail.com> wrote: > Why is it that there are so many developers out there that chooses not to > stop their services? I'm sure there are valid reasons for never stopping a > Service, but in most cases it seems to be to be just developer laziness. > > Lots of my friends with Android phones have problems with the Launcher app > getting terminated and restarting frequently and other annoying low memory > problems caused by them having too many apps installed that leave their > Services alive. Since processes with running Services are rarely killed by > the system to free memory it seems to effectively reduce the available > memory for regular apps. > > Some apps I've found that does this: > Spotify - Perhaps to emulate a desktop program where you have to explicitly > exit, their support ignores questions about it > Wimp - Perhaps to emulate a desktop program where you have to explicitly > exit, their support ignores questions about it > DoggCatcher - According to developer since it was easier and doesn't cause > any issues if you only have DoggCatcher installed > Flickr - According to support they leave their services running to provide > a unique user experience whatever that means > Foodspotting - Bug/no response from support > Google+ - Bug/no response from support > FlickrFolio - Bug/no response from support -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to android-discuss@googlegroups.com. To unsubscribe from this group, send email to android-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
