Modifier basics (padding, size, clickable) in Android Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add padding of 16.dp to the Text composable.

Android Kotlin

Text("Hello", modifier = Modifier.[1](16.dp))

Drag options to blanks, or click blank then click option'

Apadding

Bsize

Cclickable

Dbackground

Attempts:

3 left

💡 Hint

Common Mistakes

Using size instead of padding will change the composable size, not add space inside.

Using clickable won't add space, it makes the composable respond to taps.

The padding modifier adds space around the composable content.

2fill in blank

medium

Complete the code to set the size of the Button to 100.dp width and 50.dp height.

Android Kotlin

Button(onClick = {}, modifier = Modifier.[1](100.dp, 50.dp)) { Text("Click") }

Drag options to blanks, or click blank then click option'

AfillMaxWidth

Bsize

Cclickable

Dpadding

Attempts:

3 left

💡 Hint

Common Mistakes

Using padding instead of size will add space but not change the composable size.

Using clickable does not affect size.

The size modifier sets the width and height of the composable.

3fill in blank

hard

Fix the error in the code to make the Text respond to clicks.

Android Kotlin

Text("Tap me", modifier = Modifier.[1] { println("Clicked") })

Drag options to blanks, or click blank then click option'

Aclickable

Bpadding

Csize

Dbackground

Attempts:

3 left

💡 Hint

Common Mistakes

Using padding or size does not make the composable clickable.

Using background only changes color, not click behavior.

The clickable modifier makes the composable respond to tap events.

4fill in blank

hard

Fill both blanks to add padding of 8.dp and make the Box clickable.

Android Kotlin

Box(modifier = Modifier.[1](8.dp).[2] { println("Box clicked") }) { }

Drag options to blanks, or click blank then click option'

Apadding

Bsize

Cclickable

Dbackground

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the order of modifiers can cause unexpected behavior.

Using size instead of padding will change size, not add space.

First add padding, then make the Box clickable with the clickable modifier.

5fill in blank

hard

Fill all three blanks to create a Text with 12.dp padding, size 120.dp by 40.dp, and clickable behavior.

Android Kotlin

Text("Press me", modifier = Modifier.[1](12.dp).[2](120.dp, 40.dp).[3] { println("Pressed") })

Drag options to blanks, or click blank then click option'

Apadding

Bsize

Cclickable

Dbackground

Attempts:

3 left

💡 Hint

Common Mistakes

Changing the order of modifiers can affect the final look and behavior.

Using background instead of clickable will not respond to taps.

Use padding to add space, size to set dimensions, and clickable to handle taps.

Practice

1. What does the padding modifier do in Jetpack Compose?

easy

A. Changes the background color of a UI element

B. Makes a UI element respond to clicks

C. Adds space around the content inside a UI element

D. Sets the width and height of a UI element

Solution

1. Step 1: Understand the role of padding

   Padding adds empty space inside the element boundary but outside its content.

2. Step 2: Compare with other modifiers

   Size sets dimensions, clickable adds tap response, background changes color, so padding is about spacing.

3. Final Answer:

   Adds space around the content inside a UI element -> Option C

4. Quick Check:

   Padding = space around content [OK]

Hint: Padding always adds space inside element edges [OK]

Common Mistakes:

• Confusing padding with margin (margin is outside element)
• Thinking padding changes size directly
• Mixing padding with clickable behavior

2. Which of the following is the correct syntax to add 16.dp padding to a Text composable?

easy

A. Text("Hello", Modifier.padding(16.dp))

B. Text("Hello", Modifier.padding(16))

C. Text("Hello", Modifier.padding(16.px))

D. Text("Hello", Modifier.padding(16.dp, 16.dp, 16.dp))

Solution

1. Step 1: Recognize correct unit usage

   In Jetpack Compose, padding requires a Dp value, so 16.dp is correct.

2. Step 2: Check syntax correctness

   Text("Hello", Modifier.padding(16)) misses the .dp unit, C uses .px which is invalid, D tries to pass three parameters which is not the standard padding call.

3. Final Answer:

   Text("Hello", Modifier.padding(16.dp)) -> Option A

4. Quick Check:

   Use .dp for dimension units [OK]

Hint: Use .dp suffix for padding values in Compose [OK]

Common Mistakes:

• Omitting .dp unit causing type errors
• Using .px which is not valid in Compose
• Passing multiple parameters incorrectly

3. What will happen when this code runs?

Box(
  Modifier.size(100.dp).padding(20.dp).clickable { /* do something */ }
) {
  Text("Click me")
}

medium

A. Box is 100x100 dp with 20 dp padding inside and responds to clicks

B. Box is 140x140 dp because padding adds outside size

C. Box is 100x100 dp but padding disables clickable

D. Box ignores padding and clickable modifiers

Solution

1. Step 1: Understand modifier order and effects

   Size sets the Box to 100x100 dp. Padding adds space inside the Box boundary, reducing content area but not increasing Box size.

2. Step 2: Check clickable behavior

   Clickable modifier makes the Box respond to taps; it is not disabled by padding.

3. Final Answer:

   Box is 100x100 dp with 20 dp padding inside and responds to clicks -> Option A

4. Quick Check:

   Size fixes size, padding adds inner space, clickable enables taps [OK]

Hint: Padding adds space inside size, clickable always works [OK]

Common Mistakes:

• Thinking padding increases total size
• Assuming padding disables clickable
• Ignoring modifier order effects

4. Identify the error in this code snippet:

Text(
  "Tap me",
  Modifier.clickable { println("Clicked") }.padding(10.dp)
)

medium

A. Text composable cannot have clickable modifier

B. Clickable modifier must be last to work properly

C. Missing .dp unit in padding

D. Padding should come before clickable to make padding area clickable

Solution

1. Step 1: Understand modifier order impact

   Clickable only applies to the area defined by previous modifiers. Padding after clickable means padding area is not clickable.

2. Step 2: Correct modifier order

   Placing padding before clickable makes the entire padded area respond to clicks.

3. Final Answer:

   Padding should come before clickable to make padding area clickable -> Option D

4. Quick Check:

   Modifier order affects clickable area [OK]

Hint: Put padding before clickable to include padding in tap area [OK]

Common Mistakes:

• Assuming clickable works regardless of modifier order
• Thinking clickable must be last always
• Confusing padding units

5. You want a Button with a fixed size of 150x50 dp, 12 dp padding inside, and it should respond to clicks on the entire visible area including padding. Which modifier chain is correct?

hard

A. Modifier.padding(12.dp).size(150.dp, 50.dp).clickable { /* action */ }

B. Modifier.size(150.dp, 50.dp).padding(12.dp).clickable { /* action */ }

C. Modifier.clickable { /* action */ }.size(150.dp, 50.dp).padding(12.dp)

D. Modifier.clickable { /* action */ }.padding(12.dp).size(150.dp, 50.dp)

Solution

1. Step 1: Ensure size sets total dimensions

   Size should come before padding to fix the total size, with padding inside that size.

2. Step 2: Place clickable last to cover entire area

   Clickable should be last so it applies to the full size including padding.

3. Step 3: Analyze options

   Modifier.size(150.dp, 50.dp).padding(12.dp).clickable { /* action */ } sets size first, then padding inside that size, then clickable covers all.

4. Final Answer:

   Modifier.size(150.dp, 50.dp).padding(12.dp).clickable { /* action */ } -> Option B

5. Quick Check:

   Size before padding, clickable last for full tap area [OK]

Hint: Put size before padding, clickable last for full clickable area [OK]

Common Mistakes:

• Putting size after padding causing size to include padding and grow
• Clickable before padding excludes padding from tap area
• Confusing order of modifiers