Launching Activities and Subactivities

Abstract

The theory behind the Android UI architecture is that developers should decompose their application into distinct activities. For example, a calendar application could have activities for viewing the calendar, viewing a single event, editing an event (including adding a new one), viewing and editing events on the same screen for larger displays, and so forth. This implies that one of your activities has the means to start up another activity. For example, if a user selects an event from the view-calendar activity, you might want to show the view-event activity for that event. This means that you need to be able to cause the view-event activity to launch and show a specific event (the one the user chose).