Item keys for performance in Android Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to assign a unique key to each item in a LazyColumn for better performance.

Android Kotlin

LazyColumn {
  items(items = itemList, key = [1]) { item ->
    Text(text = item.name)
  }
}

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

Aitem.id

Bitem.name

CitemList.size

Ditem.hashCode()

Attempts:

3 left

💡 Hint

Common Mistakes

Using itemList.size as key causes all items to have the same key.

Using item.name might not be unique if names repeat.

Using a unique identifier like item.id as the key helps the LazyColumn track items efficiently and improves performance.

2fill in blank

medium

Complete the code to provide a stable key for each item in a RecyclerView adapter.

Android Kotlin

override fun getItemId(position: Int): Long {
  return [1]
}

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

ASystem.currentTimeMillis()

Bposition.toLong()

Citems.hashCode().toLong()

Ditems[position].id.toLong()

Attempts:

3 left

💡 Hint

Common Mistakes

Using position as ID can cause issues when items move.

Using current time causes keys to change every call.

Returning a unique stable ID like items[position].id.toLong() helps RecyclerView optimize item animations and updates.

3fill in blank

hard

Fix the error in the code to correctly set stable IDs in a RecyclerView adapter.

Android Kotlin

init {
  setHasStableIds([1])
}

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

Atrue

Bfalse

Cnull

Ditems.isNotEmpty()

Attempts:

3 left

💡 Hint

Common Mistakes

Passing false disables stable IDs, losing performance benefits.

Passing null causes a compile error.

Calling setHasStableIds(true) tells RecyclerView that each item has a unique stable ID, enabling better performance.

4fill in blank

hard

Fill both blanks to create a LazyRow with items that have unique keys.

Android Kotlin

LazyRow {
  items(items = [1], key = [2]) { item ->
    Text(text = item.title)
  }
}

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

AmyItemList

Bitem.id

Citem.title

Ditems

Attempts:

3 left

💡 Hint

Common Mistakes

Using items instead of the actual list variable.

Using item.title as key may not be unique.

Use the list variable myItemList and the unique item.id as the key for each item in LazyRow.

5fill in blank

hard

Fill all three blanks to create a RecyclerView adapter that uses stable IDs.

Android Kotlin

class MyAdapter(private val data: List<MyData>) : RecyclerView.Adapter<MyViewHolder>() {

  override fun getItemCount() = [1]

  override fun getItemId(position: Int): Long = [2]

  init {
    setHasStableIds([3])
  }

  // other adapter methods...
}

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

Adata.size

Bdata[position].uniqueId.toLong()

Ctrue

Dposition

Attempts:

3 left

💡 Hint

Common Mistakes

Returning position as ID instead of a unique stable ID.

Not enabling stable IDs with setHasStableIds(true).

Returning wrong item count.

The adapter returns the size of data, uses a unique stable ID for each item, and enables stable IDs with setHasStableIds(true).

Practice

1. Why should you use unique keys for list items in Android Kotlin RecyclerView adapters?

easy

A. To make the list items look colorful

B. To help the system identify items for efficient updates and animations

C. To increase the size of the list

D. To slow down the app for testing

Solution

1. Step 1: Understand the role of keys in lists

   Keys uniquely identify each item so the system can track changes efficiently.

2. Step 2: Connect keys to performance benefits

   Using unique keys helps RecyclerView animate changes smoothly and update only changed items.

3. Final Answer:

   To help the system identify items for efficient updates and animations -> Option B

4. Quick Check:

   Unique keys improve performance [OK]

Hint: Keys uniquely identify items for smooth updates [OK]

Common Mistakes:

• Using item position as key
• Not using keys at all
• Using non-unique keys

2. Which of the following is the correct way to provide a stable key in a RecyclerView adapter in Kotlin?

easy

A. override fun getItemId(position: Int) = position.toLong()

B. override fun getItemId(position: Int) = 0L

C. override fun getItemId(position: Int) = items[position].id

D. override fun getItemId(position: Int) = items.size.toLong()

Solution

1. Step 1: Identify stable unique ID source

   Using a unique ID from the item data ensures stable keys.

2. Step 2: Compare options

   override fun getItemId(position: Int) = items[position].id uses the item's unique id, while others use position or constants which are unstable or incorrect.

3. Final Answer:

   override fun getItemId(position: Int) = items[position].id -> Option C

4. Quick Check:

   Use unique item IDs for stable keys [OK]

Hint: Use unique item IDs, not positions, for keys [OK]

Common Mistakes:

• Using position as key which can change
• Returning constant key for all items
• Using list size as key

3. Given the following code snippet in a RecyclerView adapter, what will happen if keys are not unique?

override fun getItemId(position: Int) = position.toLong()

medium

A. RecyclerView will crash immediately

B. RecyclerView will duplicate items automatically

C. RecyclerView will ignore the keys and work fine

D. RecyclerView may incorrectly animate or update items causing glitches

Solution

1. Step 1: Understand position as key problem

   Using position as key is unstable because item positions can change when list updates.

2. Step 2: Effect on RecyclerView behavior

   RecyclerView may confuse items during animations or updates, causing visual glitches but not crashes.

3. Final Answer:

   RecyclerView may incorrectly animate or update items causing glitches -> Option D

4. Quick Check:

   Non-unique keys cause update glitches [OK]

Hint: Non-unique keys cause animation glitches [OK]

Common Mistakes:

• Thinking RecyclerView crashes on key issues
• Assuming keys don't affect animations
• Believing keys duplicate items

4. You notice your RecyclerView animations are glitchy after adding new items. Which of these fixes the problem?

medium

A. Use unique stable IDs in getItemId() and call setHasStableIds(true)

B. Remove all keys and rely on default behavior

C. Use item position as key in getItemId()

D. Disable animations completely

Solution

1. Step 1: Identify cause of glitches

   Glitches often happen when keys are unstable or missing.

2. Step 2: Apply correct fix

   Providing unique stable IDs and enabling stable IDs fixes animation glitches.

3. Final Answer:

   Use unique stable IDs in getItemId() and call setHasStableIds(true) -> Option A

4. Quick Check:

   Stable IDs fix animation glitches [OK]

Hint: Enable stable IDs with unique keys [OK]

Common Mistakes:

• Ignoring setHasStableIds(true)
• Using positions as keys
• Disabling animations instead of fixing keys

5. You have a list of users with possible duplicate names but unique IDs. Which key strategy ensures best RecyclerView performance and correct animations?

hard

A. Use user IDs as keys in getItemId() and enable stable IDs

B. Use user names as keys since they are visible

C. Use list position as key because it is simple

D. Use a random number as key for each item

Solution

1. Step 1: Analyze uniqueness of keys

   User IDs are unique, names may duplicate, positions change, random numbers are unstable.

2. Step 2: Choose best key strategy

   Using unique user IDs with stable IDs enabled ensures correct item tracking and smooth animations.

3. Final Answer:

   Use user IDs as keys in getItemId() and enable stable IDs -> Option A

4. Quick Check:

   Unique stable IDs ensure best performance [OK]

Hint: Always prefer unique stable IDs over visible or position keys [OK]

Common Mistakes:

• Using visible but non-unique fields as keys
• Using position which changes on updates
• Using random keys causing instability