Composable functions in Android Kotlin

Introduction

Composable functions help you build your app's user interface by combining small pieces together. They make UI code simple and easy to understand.

When you want to create a button, text, or image on the screen.

When you want to build a screen by putting smaller UI parts together.

When you want to update the UI quickly when data changes.

When you want to reuse UI parts in different places.

When you want your app to look good on different screen sizes.

Syntax

Android Kotlin

@Composable
fun Greeting(name: String) {
    Text(text = "Hello, $name!")
}

Use the @Composable annotation to mark a function as composable.

Composable functions describe what the UI should look like.

Examples

This function shows a simple text greeting with the given name.

Android Kotlin

@Composable
fun Greeting(name: String) {
    Text(text = "Hello, $name!")
}

This function uses two Greeting composables inside a column to show two greetings stacked vertically.

Android Kotlin

@Composable
fun WelcomeScreen() {
    Column {
        Greeting("Alice")
        Greeting("Bob")
    }
}

This shows a button with text inside. When clicked, it can run code.

Android Kotlin

@Composable
fun ButtonExample() {
    Button(onClick = { /* do something */ }) {
        Text("Click me")
    }
}

Sample App

This app shows three greetings stacked vertically: Hello, Alice! Hello, Bob! and Hello, Charlie!.

Android Kotlin

import androidx.compose.material3.*
import androidx.compose.runtime.Composable
import androidx.compose.ui.tooling.preview.Preview
import androidx.compose.foundation.layout.Column

@Composable
fun Greeting(name: String) {
    Text(text = "Hello, $name!")
}

@Composable
fun GreetingList() {
    Column {
        Greeting("Alice")
        Greeting("Bob")
        Greeting("Charlie")
    }
}

@Preview
@Composable
fun PreviewGreetingList() {
    GreetingList()
}

Important Notes

Composable functions can call other composable functions to build complex UIs.

Use @Preview to see your composable UI in Android Studio without running the app.

Composable functions should be short and focused on one UI part for easy reuse.

Summary

Composable functions build UI by combining small pieces.

Mark them with @Composable annotation.

They help create reusable and easy-to-read UI code.

Practice

1. What is the main purpose of a @Composable function in Android Kotlin?

easy

A. To manage database operations

B. To handle network requests

C. To define app navigation routes

D. To build and display UI components

Solution

1. Step 1: Understand the role of @Composable

   The @Composable annotation marks functions that create UI elements in Jetpack Compose.

2. Step 2: Identify the correct purpose

   These functions are used to build and display UI components, not for networking or database tasks.

3. Final Answer:

   To build and display UI components -> Option D

4. Quick Check:

   @Composable = UI builder [OK]

Hint: Remember: @Composable means UI code [OK]

Common Mistakes:

• Thinking @Composable handles logic like networking
• Confusing @Composable with lifecycle methods
• Assuming it manages navigation or data storage

2. Which of the following is the correct way to declare a composable function in Kotlin?

easy

A. @Composable fun MyComponent() { /* UI code */ }

B. fun MyComponent() { /* UI code */ }

C. @Composable MyComponent() { /* UI code */ }

D. fun @Composable MyComponent() { /* UI code */ }

Solution

1. Step 1: Recall the syntax for composable functions

   Composable functions must be annotated with @Composable before the function keyword.

2. Step 2: Check each option

   @Composable fun MyComponent() { /* UI code */ } correctly places @Composable before fun. The other options either lack the annotation entirely or place it incorrectly (after fun or without fun).

3. Final Answer:

   @Composable fun MyComponent() { /* UI code */ } -> Option A

4. Quick Check:

   Annotation before fun = correct syntax [OK]

Hint: Always put @Composable before fun [OK]

Common Mistakes:

• Omitting the @Composable annotation
• Placing @Composable after the function name
• Using incorrect syntax like missing fun

3. What will be displayed when this composable function is called?

  @Composable
  fun Greeting() {
    Text(text = "Hello, Compose!")
  }

medium

A. A text label showing 'Hello, Compose!'

B. A compile-time error due to missing imports

C. An empty screen with no text

D. A button labeled 'Hello, Compose!'

Solution

1. Step 1: Understand the Text composable

   The Text composable displays a text label on the screen with the given string.

2. Step 2: Analyze the function output

   The function shows the text "Hello, Compose!" as a label, not a button or empty screen.

3. Final Answer:

   A text label showing 'Hello, Compose!' -> Option A

4. Quick Check:

   Text shows text label [OK]

Hint: Text composable always displays text on screen [OK]

Common Mistakes:

• Confusing Text with Button composable
• Assuming missing imports cause runtime error
• Expecting no output from a valid composable

4. Identify the error in this composable function:

  @Composable
  fun Welcome() {
    Text(text = Hello World)
  }

medium

A. Missing @Composable annotation

B. Missing quotes around the string in Text

C. Function name should be lowercase

D. Text composable cannot be used inside functions

Solution

1. Step 1: Check the Text parameter

   The string passed to Text must be in quotes. Here, "Hello World" is missing quotes.

2. Step 2: Verify other parts

   The function has the @Composable annotation, function name casing is allowed, and Text is valid inside composables.

3. Final Answer:

   Missing quotes around the string in Text -> Option B

4. Quick Check:

   Strings need quotes in Kotlin [OK]

Hint: Strings must be in quotes inside Text composable [OK]

Common Mistakes:

• Forgetting quotes around string literals
• Thinking function names must be lowercase
• Assuming @Composable is missing when it is present

5. How can you create a reusable composable that shows a greeting with a dynamic name?
Choose the correct function declaration:

  ?

hard

A. @Composable fun Greeting() {
Text(text = "Hello, name!")
}

B. fun Greeting(name: String) {
Text(text = "Hello, ${name}!")
}

C. @Composable fun Greeting(name: String) {
Text(text = "Hello, ${name}!")
}

D. @Composable fun Greeting(name) {
Text(text = "Hello, ${name}!")
}

Solution

1. Step 1: Check for @Composable annotation and parameter

   The function must be annotated with @Composable and accept a String parameter for the name.

2. Step 2: Verify string interpolation and parameter syntax

   @Composable fun Greeting(name: String) { Text(text = "Hello, ${name}!") } correctly uses @Composable, declares name: String, and interpolates it inside the text. The version without @Composable misses the annotation, the one without a parameter hardcodes the name, and the one missing the parameter type is invalid.

3. Final Answer:

   @Composable fun Greeting(name: String) { Text(text = "Hello, ${name}!") } -> Option C

4. Quick Check:

   Composable + typed parameter + string interpolation = correct [OK]

Hint: Composable needs annotation and typed parameters [OK]

Common Mistakes:

• Omitting @Composable annotation
• Not declaring parameter type
• Hardcoding text instead of using parameter