Compose with existing Views (interop) in Android Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a traditional Android Button inside a Compose UI using AndroidView.

Android Kotlin

AndroidView(factory = { context ->
    val button = Button(context)
    button.text = "Click me"
    button.setOnClickListener { /* handle click */ }
    [1]
})

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

Abutton

Bcontext

Cthis

Dview

Attempts:

3 left

💡 Hint

Common Mistakes

Returning context or this instead of the button.

Not returning anything from the factory lambda.

The AndroidView factory must return the Android View to be displayed. Here, returning button shows the Button inside Compose.

2fill in blank

medium

Complete the code to update the Android TextView's text inside AndroidView's update block.

Android Kotlin

AndroidView(factory = { context ->
    TextView(context).apply { text = "Hello" }
}, update = { textView ->
    textView.[1] = "Updated Text"
})

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

Atext

BsetText()

CcontentDescription

Dhint

Attempts:

3 left

💡 Hint

Common Mistakes

Using setText() as a property instead of a method.

Trying to set contentDescription instead of text.

The text property of TextView sets the displayed text. Using textView.text = "Updated Text" updates the text inside Compose.

3fill in blank

hard

Fix the error in the code to correctly add a SeekBar inside Compose using AndroidView.

Android Kotlin

AndroidView(factory = { context ->
    val seekBar = SeekBar(context)
    seekBar.max = 100
    seekBar.progress = 50
    [1]
})

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

Areturn seekBar

BseekBar

Creturn@factory seekBar

DseekBar.toString()

Attempts:

3 left

💡 Hint

Common Mistakes

Just writing 'seekBar' without return keyword.

Using 'return seekBar' without label causes error in lambdas.

Returning a string instead of the View.

In Kotlin lambdas with labels, return@factory seekBar explicitly returns the SeekBar from the factory lambda, which is required here.

4fill in blank

hard

Fill both blanks to create an Android EditText with a hint and update its text inside Compose.

Android Kotlin

AndroidView(factory = { context ->
    EditText(context).apply {
        [1] = "Enter name"
    }
}, update = { editText ->
    editText.[2] = "John Doe"
})

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

Ahint

Btext

CsetText()

DcontentDescription

Attempts:

3 left

💡 Hint

Common Mistakes

Using setText() instead of text for the update block.

Using contentDescription instead of hint.

The hint property sets the placeholder text in EditText. To update the text, use the text property inside the update block.

5fill in blank

hard

Fill all three blanks to create an Android CheckBox with a label, set its checked state, and update it inside Compose.

Android Kotlin

AndroidView(factory = { context ->
    CheckBox(context).apply {
        text = [1]
        isChecked = [2]
    }
}, update = { checkBox ->
    checkBox.isChecked = [3]
})

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

A"Accept Terms"

BTrue

CFalse

D"Check me"

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes incorrectly around the label text.

Mixing true and false values for initial and updated checked state.

The CheckBox label is set with the text property. The initial checked state is set with isChecked. Inside update, you can change isChecked to update the UI.

Practice

1. What is the main purpose of using AndroidView in Jetpack Compose?

easy

A. To create animations in Compose

B. To convert Compose UI elements into XML layouts

C. To replace all Views with Compose components automatically

D. To embed traditional Android Views inside a Compose UI

Solution

1. Step 1: Understand AndroidView role

   AndroidView allows embedding existing Android Views inside Compose UI, enabling reuse of legacy UI parts.

2. Step 2: Compare options

   Creating animations, converting Compose UI elements into XML layouts, and automatically replacing all Views with Compose components do not describe embedding Views inside Compose. Only embedding traditional Android Views inside a Compose UI correctly states the purpose.

3. Final Answer:

   To embed traditional Android Views inside a Compose UI -> Option D

4. Quick Check:

   AndroidView = Embed Views in Compose [OK]

Hint: AndroidView puts Views inside Compose UI [OK]

Common Mistakes:

• Confusing AndroidView with ComposeView
• Thinking AndroidView converts Compose to XML
• Assuming AndroidView replaces Views automatically

2. Which of the following is the correct way to add a Compose UI inside an existing Android View hierarchy?

easy

A. Use AndroidView inside the View XML layout

B. Use ComposeView inside the View hierarchy

C. Replace the View with a Compose function directly

D. Use setContentView with Compose functions

Solution

1. Step 1: Identify ComposeView usage

   ComposeView is a View that hosts Compose UI inside a traditional View hierarchy.

2. Step 2: Eliminate wrong options

   Use AndroidView inside the View XML layout is wrong because AndroidView is for Compose to View embedding, not View XML. Replace the View with a Compose function directly is invalid as Views cannot be replaced directly by Compose functions. Use setContentView with Compose functions is for setting Compose as the whole content, not embedding.

3. Final Answer:

   Use ComposeView inside the View hierarchy -> Option B

4. Quick Check:

   ComposeView = Compose inside Views [OK]

Hint: ComposeView hosts Compose inside Views [OK]

Common Mistakes:

• Using AndroidView to embed Compose in Views
• Trying to replace Views with Compose functions directly
• Confusing setContentView with embedding Compose

3. What will be displayed when the following Compose code runs?

AndroidView(factory = { context ->
    Button(context).apply {
        text = "Click Me"
    }
})

medium

A. An empty space because Button is not a Compose component

B. A Compose Button with text "Click Me"

C. A traditional Android Button with text "Click Me" inside Compose

D. A runtime error because Button cannot be used inside AndroidView

Solution

1. Step 1: Analyze AndroidView factory

   The factory creates a traditional Android Button with text "Click Me" inside Compose UI.

2. Step 2: Understand output

   AndroidView embeds the View, so the Button is shown as a View inside Compose, not a Compose Button.

3. Final Answer:

   A traditional Android Button with text "Click Me" inside Compose -> Option C

4. Quick Check:

   AndroidView shows Views inside Compose [OK]

Hint: AndroidView shows Views, not Compose components [OK]

Common Mistakes:

• Thinking AndroidView creates Compose components
• Expecting runtime error for Button usage
• Confusing Android Button with Compose Button

4. Identify the error in this Compose code embedding a View:

AndroidView(factory = { context ->
    TextView(context).apply {
        setText("Hello")
    }
}) {
    text = "World"
}

medium

A. Cannot set text inside the trailing lambda; it should be inside factory

B. TextView does not exist in Android Views

C. Missing import for AndroidView

D. Factory lambda must return null

Solution

1. Step 1: Check AndroidView usage

   The trailing lambda is for updating the View, but text is not a Compose property; it should be set on the View inside the factory or update block.

2. Step 2: Identify correct usage

   Setting text outside the factory like this causes error because text is not recognized in that scope.

3. Final Answer:

   Cannot set text inside the trailing lambda; it should be inside factory -> Option A

4. Quick Check:

   Set View properties inside factory or update lambda [OK]

Hint: Set View properties inside factory or update lambda [OK]

Common Mistakes:

• Trying to set View properties directly in trailing lambda
• Assuming trailing lambda is Compose scope
• Ignoring factory return value requirements

5. You want to gradually migrate an app from Views to Compose. Which approach correctly mixes Compose and Views for a smooth transition?

hard

A. Use ComposeView to add Compose UI inside existing View layouts and AndroidView to add Views inside Compose screens

B. Rewrite all Views to Compose before running the app

C. Use only AndroidView everywhere to avoid Compose

D. Replace setContentView with Compose functions and remove all Views immediately

Solution

1. Step 1: Understand gradual migration

   Gradual migration means mixing Compose and Views without rewriting everything at once.

2. Step 2: Identify correct interop usage

   ComposeView embeds Compose inside Views; AndroidView embeds Views inside Compose. Using both allows smooth transition.

3. Step 3: Eliminate wrong options

   Rewriting all Views to Compose before running the app, using only AndroidView everywhere to avoid Compose, and replacing setContentView with Compose functions and removing all Views immediately are extreme or incorrect approaches that do not support gradual migration.

4. Final Answer:

   Use ComposeView to add Compose UI inside existing View layouts and AndroidView to add Views inside Compose screens -> Option A

5. Quick Check:

   ComposeView + AndroidView = smooth migration [OK]

Hint: Use ComposeView and AndroidView together for migration [OK]

Common Mistakes:

• Trying to rewrite entire app at once
• Using only AndroidView or only ComposeView
• Removing Views before Compose is ready