Activity concept in Android Kotlin

Introduction

An Activity is like a single screen in an app. It shows the user what to see and lets them interact with the app.

When you want to show a new screen to the user.

When you need to handle user actions on a screen.

When you want to switch between different parts of your app.

When you want to display a form or information page.

When you want to manage the app's lifecycle for a screen.

Syntax

Android Kotlin

class MainActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_main)
  }
}

onCreate() is where you set up the screen.

setContentView() links the screen to a layout file.

Examples

This creates a second screen with its own layout.

Android Kotlin

class SecondActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_second)
  }
}

onStart() runs when the screen is about to be shown.

Android Kotlin

override fun onStart() {
  super.onStart()
  // Code to run when activity becomes visible
}

Sample App

This simple Activity shows a text message on the screen.

Android Kotlin

import android.os.Bundle
import androidx.appcompat.app.AppCompatActivity
import android.widget.TextView

class MainActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    val textView = TextView(this)
    textView.text = "Hello from Activity!"
    setContentView(textView)
  }
}

Important Notes

Every screen in Android is an Activity or uses one.

Activities have a lifecycle: onCreate, onStart, onResume, onPause, onStop, onDestroy.

Use the AndroidManifest.xml to declare your Activity.

Summary

An Activity is a screen in your app.

Use onCreate() to set up the screen.

Activities manage user interaction and app flow.

Practice

1. What is the main role of an Activity in an Android app?

easy

A. It stores app data permanently.

B. It handles network requests only.

C. It manages background tasks without UI.

D. It represents a single screen with a user interface.

Solution

1. Step 1: Understand Activity purpose

   An Activity is designed to show a screen where users interact.

2. Step 2: Compare options

   Only It represents a single screen with a user interface. correctly describes an Activity as a UI screen.

3. Final Answer:

   It represents a single screen with a user interface. -> Option D

4. Quick Check:

   Activity = Screen UI [OK]

Hint: Remember: Activity = one screen in app [OK]

Common Mistakes:

• Confusing Activity with data storage
• Thinking Activity runs without UI
• Mixing Activity with background services

2. Which method is used to set up the UI when an Activity starts?

easy

A. onResume()

B. onStart()

C. onCreate()

D. onPause()

Solution

1. Step 1: Identify lifecycle methods

   onCreate() is called when the Activity is first created to set up UI.

2. Step 2: Eliminate other methods

   onStart() and onResume() happen later; onPause() is for pausing.

3. Final Answer:

   onCreate() -> Option C

4. Quick Check:

   UI setup = onCreate() [OK]

Hint: UI setup always starts in onCreate() [OK]

Common Mistakes:

• Choosing onStart() or onResume() for UI setup
• Confusing onPause() as setup method
• Not knowing Activity lifecycle order

3. What will happen when this Activity code runs?

class MainActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_main)
  }
}

medium

A. The screen shows the layout defined in activity_main.xml.

B. The app shows a blank screen.

C. Nothing happens because onCreate is empty.

D. The app crashes due to missing layout.

Solution

1. Step 1: Analyze onCreate method

   It calls super.onCreate and sets content view to activity_main layout.

2. Step 2: Understand setContentView effect

   This loads and displays the UI from activity_main.xml on screen.

3. Final Answer:

   The screen shows the layout defined in activity_main.xml. -> Option A

4. Quick Check:

   setContentView loads layout = screen shows layout [OK]

Hint: setContentView shows UI layout on screen [OK]

Common Mistakes:

• Assuming onCreate does nothing
• Thinking app crashes without error
• Confusing blank screen with missing layout

4. Identify the error in this Activity code:

class MainActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    setContentView(R.layout.activity_main)
    super.onCreate(savedInstanceState)
  }
}

medium

A. setContentView called before super.onCreate()

B. No error, code is correct

C. Missing call to super.onCreate()

D. onCreate method should not be overridden

Solution

1. Step 1: Check order of calls in onCreate

   super.onCreate() must be called before setContentView to initialize Activity properly.

2. Step 2: Identify mistake

   Here, setContentView is called first, which is incorrect and can cause issues.

3. Final Answer:

   setContentView called before super.onCreate() -> Option A

4. Quick Check:

   super.onCreate() first, then setContentView [OK]

Hint: Always call super.onCreate() before setContentView [OK]

Common Mistakes:

• Calling setContentView before super.onCreate()
• Forgetting to override onCreate
• Not calling super.onCreate() at all

5. You want to start a new Activity called DetailActivity from MainActivity. Which code snippet correctly starts the new Activity?

hard

A. startActivity(DetailActivity::class.java)

B. val intent = Intent(this, DetailActivity::class.java)
startActivity(intent)

C. Intent intent = new Intent(DetailActivity)
startActivity(intent)

D. val intent = Intent(DetailActivity)
startActivity()

Solution

1. Step 1: Understand Intent creation

   Intent requires context (this) and target Activity class (DetailActivity::class.java).

2. Step 2: Check startActivity usage

   startActivity(intent) correctly starts the new Activity with the Intent.

3. Final Answer:

   val intent = Intent(this, DetailActivity::class.java) startActivity(intent) -> Option B

4. Quick Check:

   Intent(this, TargetClass) + startActivity(intent) [OK]

Hint: Use Intent(this, TargetActivity::class.java) to start Activity [OK]

Common Mistakes:

• Omitting context in Intent constructor
• Calling startActivity without Intent
• Using wrong syntax for Intent creation