Lifecycle awareness in Android Kotlin

Introduction

Lifecycle awareness helps your app know when to start, pause, or stop tasks. This keeps your app smooth and saves battery.

When you want to pause a video when the user switches apps.

When you need to save user data before the app closes.

When you want to stop background tasks to save battery.

When you want to refresh data when the app becomes active again.

Syntax

Android Kotlin

class MyActivity : AppCompatActivity(), LifecycleObserver {
  @OnLifecycleEvent(Lifecycle.Event.ON_START)
  fun onStartEvent() {
    // Code to run when activity starts
  }

  @OnLifecycleEvent(Lifecycle.Event.ON_STOP)
  fun onStopEvent() {
    // Code to run when activity stops
  }
}

Use @OnLifecycleEvent to mark methods that respond to lifecycle changes.

Register your observer with lifecycle.addObserver(this) in your activity or fragment.

Examples

This observer prints a message when the app resumes.

Android Kotlin

class MyObserver : LifecycleObserver {
  @OnLifecycleEvent(Lifecycle.Event.ON_RESUME)
  fun onResume() {
    println("App resumed")
  }
}

Here, the activity adds the observer to listen for lifecycle events.

Android Kotlin

class MyActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    lifecycle.addObserver(MyObserver())
  }
}

Sample App

This app prints messages to the console when the activity starts and stops. It shows how lifecycle awareness helps react to app state changes.

Android Kotlin

import android.os.Bundle
import androidx.appcompat.app.AppCompatActivity
import androidx.lifecycle.Lifecycle
import androidx.lifecycle.LifecycleObserver
import androidx.lifecycle.OnLifecycleEvent

class MainActivity : AppCompatActivity(), LifecycleObserver {

  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(android.R.layout.simple_list_item_1)
    lifecycle.addObserver(this)
  }

  @OnLifecycleEvent(Lifecycle.Event.ON_START)
  fun onStartEvent() {
    println("Activity started")
  }

  @OnLifecycleEvent(Lifecycle.Event.ON_STOP)
  fun onStopEvent() {
    println("Activity stopped")
  }
}

Important Notes

Lifecycle events help manage resources efficiently.

Always remove observers if you add them manually to avoid leaks.

Use lifecycle-aware components to simplify your code.

Summary

Lifecycle awareness lets your app respond to start, stop, and other state changes.

Use LifecycleObserver and @OnLifecycleEvent to handle events.

This helps save battery and keep your app smooth.

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