Lifecycle awareness in Android Kotlin - UI Render Trace

Component - Lifecycle awareness

This component demonstrates how an Android activity responds to lifecycle events like creation, start, resume, pause, stop, and destroy. It helps you understand when and how the app reacts to user actions or system changes.

Widget Tree

Activity
├── onCreate()
├── onStart()
├── onResume()
├── onPause()
├── onStop()
└── onDestroy()

The Activity is the main screen container. It goes through lifecycle methods in order: onCreate sets up UI, onStart makes it visible, onResume allows interaction. onPause and onStop happen when the app loses focus or is hidden. onDestroy cleans up before the activity is removed.

Render Trace - 6 Steps

Step 1: Activity

Step 2: Activity

Step 3: Activity

Step 4: Activity

Step 5: Activity

Step 6: Activity

State Change - Re-render

Trigger:User presses home button or switches app

Before

Activity is in onResume state, fully interactive

→

After

Activity moves to onPause then onStop, UI hidden

Re-renders:The entire activity UI becomes inactive and hidden

UI Quiz - 3 Questions

Which lifecycle method is called when the activity becomes visible but not yet interactive?

A onStart

B onCreate

C onResume

D onPause

Key Insight

Understanding the Android activity lifecycle helps you manage app behavior smoothly. You can save data or pause animations at the right time, improving user experience and app performance.