Why network calls fetch remote data in Android Kotlin - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a network call using Kotlin coroutines.

Android Kotlin

GlobalScope.launch {
    val response = [1]("https://example.com/data.json")
}

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

AfetchData

BfetchFromNetwork

CfetchRemoteData

Dfetch

Attempts:

3 left

💡 Hint

Common Mistakes

Using a function name that does not exist or is not standard.

Trying to call a network function without coroutine scope.

The fetch function is used here to represent a network call that fetches remote data asynchronously.

2fill in blank

medium

Complete the code to convert the network response to a string.

Android Kotlin

val data = response.[1]()

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

AreadText

BtoString

CtoJson

DtoByteArray

Attempts:

3 left

💡 Hint

Common Mistakes

Using toString() which does not read the content but returns object info.

Using toJson() which is not a standard function.

The readText() function reads the response body as a string, which is common after fetching remote data.

3fill in blank

hard

Fix the error in the code to make the network call on the main thread safe.

Android Kotlin

runBlocking {
    val result = withContext([1]) {
        fetch("https://example.com")
    }
}

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

ADispatchers.Main

BDispatchers.IO

CDispatchers.Default

DDispatchers.Unconfined

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.Main which blocks the UI.

Using Dispatchers.Default which is for CPU-intensive tasks.

Network calls should run on Dispatchers.IO to avoid blocking the main thread and keep the app responsive.

4fill in blank

hard

Fill both blanks to create a simple function that fetches remote data and returns it as a string.

Android Kotlin

suspend fun getData(url: String): String {
    return withContext([1]) {
        val response = fetch(url)
        response.[2]()
    }
}

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

ADispatchers.IO

BDispatchers.Main

CreadText

DtoString

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.Main which blocks UI.

Using toString() which does not read response content.

The function uses Dispatchers.IO to run the network call safely and readText() to get the response as a string.

5fill in blank

hard

Fill all three blanks to create a coroutine that fetches data and updates the UI safely.

Android Kotlin

GlobalScope.launch {
    val data = withContext([1]) {
        fetch("https://api.example.com")
            .[2]()
    }
    withContext([3]) {
        textView.text = data
    }
}

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

ADispatchers.IO

BreadText

CDispatchers.Main

DtoString

Attempts:

3 left

💡 Hint

Common Mistakes

Updating UI on IO dispatcher causing crashes.

Not reading response content properly.

The network call runs on Dispatchers.IO, the response is read as text with readText(), and the UI update runs on Dispatchers.Main to keep the app responsive.