Kotlin for Android Basics

# CHAPTER 24

Kotlin for Android Basics #

1. Chapter Introduction #

2. Learning Objectives #

• Understand the role of Android Studio.

• Explain the MVC architecture in Android (XML + Kotlin).

• Understand what an Activity is.

• Bind an XML UI button to Kotlin logic.

• Use an Intent to navigate between screens.

3. Android Studio vs IntelliJ IDEA #

• Android Emulator (Virtual Phone).

• SDK Manager (To download different Android versions).

• Visual Layout Editor (To drag and drop UI elements).

4. The Architecture (XML + Kotlin) #

• XML Files (res/layout/activity_main.xml): Dictates how the screen looks (Buttons, Text colors, Margins).

• Kotlin Files (MainActivity.kt): Dictates how the screen behaves (What happens when a button is clicked).

*(Note: Google is currently transitioning to "Jetpack Compose", which allows you to build UIs purely in Kotlin without XML, but understanding the XML system is still mandatory for maintaining millions of existing apps).*

5. What is an Activity? #

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

// MainActivity inherits from AppCompatActivity
class MainActivity : AppCompatActivity() {

    // onCreate is the entry point for this screen (like fun main)
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        // Connects this Kotlin code to the XML visual layout!
        setContentView(R.layout.activity_main) 
    }
}

6. Binding UI to Kotlin #

import android.widget.Button
import android.widget.Toast

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)
        
        // 1. Find the button from the XML
        val submitButton = findViewById<Button>(R.id.btnSubmit)
        
        // 2. Attach a Click Listener using a trailing lambda!
        submitButton.setOnClickListener {
            // 3. Show a pop-up message (Toast)
            Toast.makeText(this, "Button Clicked!", Toast.LENGTH_SHORT).show()
        }
    }
}

7. Navigating Between Screens (Intents) #

import android.content.Intent

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)
        
        val nextButton = findViewById<Button>(R.id.btnNext)
        
        nextButton.setOnClickListener {
            // Create an Intent stating we want to go to DetailsActivity
            // Note the use of ::class.java to interoperate with Android's Java core
            val intent = Intent(this, DetailsActivity::class.java)
            
            // Execute the navigation
            startActivity(intent)
        }
    }
}

8. Common Mistakes #

• Forgetting to declare Activities in the Manifest: Every single Activity must be registered in the AndroidManifest.xml file. If you create a new Activity but don't add it to the manifest, the app will instantly crash when you try to navigate to it.

• Null UI Elements: Calling findViewById *before* calling setContentView(). The app will crash because the XML hasn't been loaded into memory yet!

9. Best Practices #

• Use ViewBinding: findViewById is considered legacy and is prone to null crashes. Learn and enable "ViewBinding" in your build.gradle file, which automatically generates safe Kotlin properties for every ID in your XML.

10. Exercises #

1. 1. Describe the relationship between activity_main.xml and MainActivity.kt.

1. 2. Write the syntax to create an Intent navigating from Login to Home.

11. MCQs with Answers #

12. Interview Questions #

• Q: Explain the purpose of an Intent in Android.

• Q: What is the difference between an Activity and an XML Layout?

13. Summary #

14. Next Chapter Recommendation #