I agree; this is an unnecessary limitation in the api IMO. It is fair enough to require user input to start any code *the very first time they install*, but what about during upgrades? With the way things work now, it's possible for an app to stop working after an upgrade due to the user not starting the app after installation.
On Feb 13, 12:36 pm, Peter Jeffe <pje...@gmail.com> wrote: > On Feb 12, 1:54 pm, Dianne Hackborn <hack...@android.com> wrote: > > > No, you should let the user decide to run you when they want. > > We certainly let the user decide when they want to run our activity > and interact with it, but we also have a service that we want to run > after we are installed and at boot time. In any system there are > applications that have a service/daemon character, or a component of > them that do, and mobile devices are no different. Android provides > the BOOT_COMPLETED broadcast to allow this behavior at boot time, just > like Unix's init or Window's service manager, so I don't see why it > would be a problem to have us invoked in the same manner after > installation? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
