There are a number of scenarios. The basic one is from the home page, but an app can also "run" when the device boots, wakes up, an alarm fires, or when another application sends an intent. The crux is the manifest which tells the Android OS what interactions the app is expecting and able to respond to.
Note that an app doesn't really run. Its code gets loaded into a Dalvic VM and then the Andorid OS calls various lifecycle methods in the app's code. A lot of newbie developers stumble over this, thinking that an Android app runs just like a desktop application (even they are really subject to an event loop as well). If you can think of IOC (inversion of control) you'll have a better grip on how this works. -- 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
