Lifecycle awareness in Android Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of lifecycle awareness in Android apps?

Lifecycle awareness helps an app respond correctly to changes in its state, like when it starts, stops, or is destroyed. This keeps the app efficient and prevents crashes.

beginner

Name the main lifecycle states of an Android Activity.

The main states are: onCreate (start), onStart (visible), onResume (active), onPause (partially visible), onStop (hidden), and onDestroy (cleanup).

intermediate

What is a LifecycleObserver in Android?

A LifecycleObserver is a class that watches lifecycle events of components like Activities or Fragments and reacts to them, helping organize code and manage resources.

intermediate

Why should you avoid heavy work in onResume() and prefer lifecycle-aware components?

Heavy work in onResume() can slow the app and cause a bad user experience. Lifecycle-aware components help run tasks only when needed and stop them when not visible.

intermediate

How does ViewModel help with lifecycle awareness?

ViewModel holds UI data and survives configuration changes like screen rotations, so data is not lost and the UI stays consistent without restarting tasks.

Which lifecycle method is called when an Activity becomes visible but not yet interactive?

A onCreate()

B onStart()

C onResume()

D onPause()

onStart() is called when the Activity becomes visible to the user but is not yet in the foreground for interaction.

What interface do you implement to create a lifecycle-aware observer in Android?

A LifecycleOwner

B ViewModel

C ActivityLifecycleCallbacks

D LifecycleObserver

LifecycleObserver is the interface used to create classes that observe lifecycle events.

Which lifecycle method is best for releasing resources when an Activity is no longer visible?

A onStop()

B onPause()

C onDestroy()

D onResume()

onStop() is called when the Activity is no longer visible, making it a good place to release resources.

What happens to a ViewModel when the Activity is destroyed due to a configuration change?

A It is destroyed immediately

B It is recreated with the Activity

C It survives and retains data

D It causes a memory leak

ViewModel survives configuration changes and keeps UI data intact.

Why is lifecycle awareness important for background tasks?

A All of the above

B To prevent tasks from running when the app is stopped

C To save battery and resources

D To run tasks only when the app is visible

Lifecycle awareness helps manage background tasks efficiently, saving battery and resources by running tasks only when appropriate.

Explain the main lifecycle states of an Android Activity and what happens in each.

Think about when the Activity is created, visible, interactive, partially visible, hidden, and destroyed.

Describe how lifecycle-aware components improve app performance and user experience.

Consider how apps behave when users switch apps or rotate screens.

Practice

1. What is the main purpose of lifecycle awareness in an Android app?

easy

A. To add animations to UI components

B. To change the app's theme colors dynamically

C. To increase the app's download speed

D. To respond to app state changes like start and stop

Solution

1. Step 1: Understand lifecycle awareness concept

   Lifecycle awareness means the app knows when it starts, stops, or pauses.

2. Step 2: Identify the main goal

   The goal is to respond properly to these state changes to save resources and improve user experience.

3. Final Answer:

   To respond to app state changes like start and stop -> Option D

4. Quick Check:

   Lifecycle awareness = respond to state changes [OK]

Hint: Lifecycle awareness means reacting to app start/stop events [OK]

Common Mistakes:

• Confusing lifecycle with UI styling
• Thinking it controls app download speed
• Assuming it only adds animations

2. Which annotation is used to mark a method that listens to lifecycle events in Android Kotlin?

easy

A. @OnClick

B. @OnLifecycleEvent

C. @Override

D. @Subscribe

Solution

1. Step 1: Recall lifecycle event annotations

   In Android Kotlin, @OnLifecycleEvent marks methods that respond to lifecycle changes.

2. Step 2: Compare options

   @OnClick is for button clicks, @Override is for overriding methods, @Subscribe is for event bus patterns.

3. Final Answer:

   @OnLifecycleEvent -> Option B

4. Quick Check:

   Lifecycle event listener annotation = @OnLifecycleEvent [OK]

Hint: Use @OnLifecycleEvent to handle lifecycle changes [OK]

Common Mistakes:

• Using @OnClick for lifecycle events
• Confusing @Override with lifecycle annotations
• Thinking @Subscribe is for lifecycle

3. Given this code snippet, what lifecycle event will trigger the onStartEvent() method?

class MyObserver : LifecycleObserver {
  @OnLifecycleEvent(Lifecycle.Event.ON_START)
  fun onStartEvent() {
    println("Started")
  }
}

medium

A. When the app starts or comes to foreground

B. When the app is paused

C. When the app is stopped

D. When the app is destroyed

Solution

1. Step 1: Identify the lifecycle event annotation

   The method is annotated with @OnLifecycleEvent(Lifecycle.Event.ON_START), which means it triggers on start.

2. Step 2: Understand ON_START meaning

   ON_START happens when the app moves to the foreground or becomes visible.

3. Final Answer:

   When the app starts or comes to foreground -> Option A

4. Quick Check:

   ON_START event triggers on app foreground [OK]

Hint: ON_START means app is visible or foregrounded [OK]

Common Mistakes:

• Confusing ON_START with ON_PAUSE or ON_STOP
• Thinking ON_START means app destroyed
• Assuming it triggers on app pause

4. What is wrong with this observer class?

class MyObserver : LifecycleObserver {
  fun onResumeEvent() {
    println("Resumed")
  }
}

medium

A. Missing @OnLifecycleEvent annotation on the method

B. Class should extend Activity instead of LifecycleObserver

C. Method name must be onStartEvent instead of onResumeEvent

D. println cannot be used inside lifecycle methods

Solution

1. Step 1: Check method annotation

   The method onResumeEvent lacks the @OnLifecycleEvent annotation, so it won't be called on lifecycle changes.

2. Step 2: Verify class and method correctness

   The class correctly implements LifecycleObserver, method name can be any valid name, and println is allowed.

3. Final Answer:

   Missing @OnLifecycleEvent annotation on the method -> Option A

4. Quick Check:

   Lifecycle methods need @OnLifecycleEvent annotation [OK]

Hint: Always add @OnLifecycleEvent to lifecycle methods [OK]

Common Mistakes:

• Forgetting the annotation
• Thinking method name must be fixed
• Assuming println is disallowed

5. You want to save battery by stopping a sensor when the app is not visible. Which lifecycle event should you observe to stop the sensor properly?

hard

A. Lifecycle.Event.ON_CREATE

B. Lifecycle.Event.ON_RESUME

C. Lifecycle.Event.ON_PAUSE

D. Lifecycle.Event.ON_DESTROY

Solution

1. Step 1: Understand when to stop sensors

   Sensors should stop when the app is no longer visible to save battery, which happens at ON_PAUSE.

2. Step 2: Match lifecycle event to stopping action

   ON_PAUSE is called when the app loses focus but is not yet destroyed, ideal for stopping sensors.

3. Final Answer:

   Lifecycle.Event.ON_PAUSE -> Option C

4. Quick Check:

   Stop sensors on ON_PAUSE to save battery [OK]

Hint: Stop sensors on ON_PAUSE to save battery [OK]

Common Mistakes:

• Stopping sensors too late at ON_DESTROY
• Stopping sensors too early at ON_CREATE
• Confusing ON_RESUME with stopping event