Why Activity concept in Android Kotlin? - Purpose & Use Cases

The Big Idea

What if managing each screen in your app was as easy as flipping a page in a book?

The Scenario

Imagine you want to build a mobile app with multiple screens, like a login page, a home page, and a settings page. Without a clear way to manage these screens, you might try to put all the code and layouts in one place.

This quickly becomes confusing and hard to control, like trying to read a book where all chapters are jumbled together.

The Problem

Trying to handle multiple screens manually means writing lots of complicated code to switch views, manage user input, and keep track of what screen is showing.

This is slow to build, easy to break, and hard to fix or improve later.

The Solution

The Activity concept in Android gives you a simple, organized way to create and manage each screen separately.

Each Activity acts like a single page in your app, handling its own layout and user interactions.

Android helps you switch between Activities smoothly, so your app feels natural and easy to use.

Before vs After

✗ Before

fun showScreen(name: String) {
  if (name == "login") {
    // show login layout
  } else if (name == "home") {
    // show home layout
  }
}

✓ After

startActivity(Intent(this, HomeActivity::class.java))

What It Enables

With Activities, you can build apps with many screens that work well together, making your app organized and user-friendly.

Real Life Example

Think of a shopping app: one Activity shows the product list, another shows product details, and another handles the checkout process. Activities keep these parts separate but connected.

Key Takeaways

Activities represent individual screens in an Android app.

They help organize code and UI for each screen separately.

Android manages switching between Activities smoothly for you.

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