Understanding Android Activity: Functions, Lifecycle, and Process States

Activity is a fundamental interaction component in Android that connects an app with its users; testers and developers must understand its purpose and behavior.

Functions of Activity

1. User interaction – Activity loads layout XML via setContentView() , displays UI, updates it with backend results, and receives user commands for processing.

2. Obtaining a Context object – Activity provides an application context, essential for many system components, libraries, and resources, similar to Application and Service.

3. Saving state – Activity can record transient data so that when the user returns, the previous state can be restored, preventing loss when the app is killed.

4. Handling configuration changes – When device configuration (e.g., orientation) changes, Android recreates the Activity, reloading resources and using the saved state.

5. Switching between Activity and Service – Activities launch other Activities or Services via Intents, passing small amounts of data; the Activity stack manages navigation and back‑button behavior.

Activity Lifecycle

The lifecycle consists of a complete cycle (onCreate → onDestroy), a visible cycle (onStart → onStop), and a foreground cycle (onResume → onPause). The visible state does not guarantee user input; an Activity can be visible but not interactable if partially covered.

Process States

Android prioritizes processes based on Activity state: foreground processes (active user interaction), visible processes (user can see but not interact), background processes (no visible UI), and empty processes (cached after app exit). Higher‑priority processes are less likely to be killed.

Other Notes

Additional topics such as Activity stack management and Intent relationships are mentioned as future material, and developers must register each Activity in AndroidManifest.xml before use.