I've been trying to understand the key concepts that make up the Android programming model. I'm impressed as well as intrigued by 'tasks' that stack up activities. I do not really appreciate why and how one assigns a particular launch mode to an activity. For instance, I'd like to define a few necessary conditions for marking an activity the root of a new task. I'm focusing particularly on the 'singleTask' launch mode. I'd like to know, for example, whether security, user experience, and such factors decide the launch modes...
Can someone educate me about the rationale behind Android tasks? I'm also curious to know the thought process behind their design when they were originally conceived? thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
