LazyGrid in Android Kotlin

Introduction

LazyGrid helps you show many items in a grid without slowing down your app. It only creates items you see on the screen, saving memory and making scrolling smooth.

Showing a photo gallery with many pictures.

Displaying a list of products in a shopping app in a grid layout.

Creating a grid of buttons or icons that users can tap.

Making a dashboard with multiple cards arranged in rows and columns.

Syntax

Android Kotlin

LazyVerticalGrid(
    columns = GridCells.Fixed(2),
    content = {
        items(yourList) { item ->
            // Your item UI here
        }
    }
)

LazyVerticalGrid creates a vertical scrolling grid.

GridCells.Fixed(2) means 2 columns in the grid.

Examples

This creates a grid with 3 columns and 10 text items labeled from Item #0 to Item #9.

Android Kotlin

LazyVerticalGrid(
    columns = GridCells.Fixed(3),
    content = {
        items(10) { index ->
            Text("Item #$index")
        }
    }
)

This grid adapts the number of columns based on minimum size 100dp for each item, showing letters A, B, and C.

Android Kotlin

LazyVerticalGrid(
    columns = GridCells.Adaptive(minSize = 100.dp),
    content = {
        items(listOf("A", "B", "C")) { letter ->
            Text(letter)
        }
    }
)

Sample App

This example shows a simple grid with 2 columns displaying fruit names. Each fruit name has padding around it for spacing.

Android Kotlin

import androidx.compose.foundation.layout.padding
import androidx.compose.foundation.lazy.grid.GridCells
import androidx.compose.foundation.lazy.grid.LazyVerticalGrid
import androidx.compose.foundation.lazy.grid.items
import androidx.compose.material3.MaterialTheme
import androidx.compose.material3.Surface
import androidx.compose.material3.Text
import androidx.compose.runtime.Composable
import androidx.compose.ui.Modifier
import androidx.compose.ui.unit.dp

@Composable
fun SimpleLazyGrid() {
    val fruits = listOf("Apple", "Banana", "Cherry", "Date", "Elderberry", "Fig")
    LazyVerticalGrid(
        columns = GridCells.Fixed(2),
        modifier = Modifier.padding(16.dp)
    ) {
        items(fruits) { fruit ->
            Text(
                text = fruit,
                modifier = Modifier.padding(8.dp),
                style = MaterialTheme.typography.bodyLarge
            )
        }
    }
}

Important Notes

LazyGrid only creates items visible on screen, so it works well with large lists.

You can choose fixed columns or adaptive columns that change based on screen size.

Use padding and spacing modifiers to make your grid look neat and readable.

Summary

LazyGrid shows items in a grid efficiently by creating only visible items.

You can set fixed or adaptive columns to control grid layout.

It is great for photo galleries, product lists, or any grid-based UI.

Practice

1. What is the main purpose of using LazyVerticalGrid in Android Compose?

easy

A. To efficiently display a scrollable grid of items by creating only visible items

B. To create a fixed number of buttons in a row

C. To display a list of items vertically without any grid layout

D. To load all items at once for faster access

Solution

1. Step 1: Understand LazyVerticalGrid behavior

   LazyVerticalGrid creates only the visible grid items to save memory and improve performance.

2. Step 2: Compare with other options

   Options A and B describe different layouts, and D is inefficient because it loads all items at once.

3. Final Answer:

   To efficiently display a scrollable grid of items by creating only visible items -> Option A

4. Quick Check:

   LazyGrid creates visible items only = C [OK]

Hint: LazyGrid creates only visible items for efficiency [OK]

Common Mistakes:

• Thinking LazyGrid loads all items at once
• Confusing LazyGrid with a simple vertical list
• Assuming LazyGrid fixes number of buttons only

2. Which of the following is the correct way to define a fixed number of columns in a LazyVerticalGrid?

easy

A. LazyVerticalGrid(columns = GridCells.Fixed("3")) { /* items */ }

B. LazyVerticalGrid(columns = GridCells.Fixed(3)) { /* items */ }

C. LazyVerticalGrid(columns = 3) { /* items */ }

D. LazyVerticalGrid(columns = GridCells.Adaptive(100.dp)) { /* items */ }

Solution

1. Step 1: Recall syntax for fixed columns

   The correct syntax uses GridCells.Fixed with an integer number of columns.

2. Step 2: Analyze each option

   LazyVerticalGrid(columns = GridCells.Fixed(3)) { /* items */ } uses GridCells.Fixed(3) correctly. LazyVerticalGrid(columns = GridCells.Adaptive(100.dp)) { /* items */ } uses adaptive columns, not fixed. LazyVerticalGrid(columns = 3) { /* items */ } passes an integer directly, which is invalid. LazyVerticalGrid(columns = GridCells.Fixed("3")) { /* items */ } passes a string instead of an integer.

3. Final Answer:

   LazyVerticalGrid(columns = GridCells.Fixed(3)) { /* items */ } -> Option B

4. Quick Check:

   Fixed columns use GridCells.Fixed(number) = D [OK]

Hint: Use GridCells.Fixed(number) for fixed columns [OK]

Common Mistakes:

• Passing integer directly instead of GridCells.Fixed
• Using string instead of integer for column count
• Confusing fixed with adaptive columns

3. Given the code snippet:

LazyVerticalGrid(columns = GridCells.Fixed(2)) {
  items(4) { index ->
    Text(text = "Item $index")
  }
}

How many columns and rows will be visible if the grid shows all items?

medium

A. 2 columns and 2 rows

B. 4 columns and 1 row

C. 1 column and 4 rows

D. 2 columns and 4 rows

Solution

1. Step 1: Understand columns and items

   The grid has 2 fixed columns and 4 items total.

2. Step 2: Calculate rows needed

   With 2 columns, 4 items fill 2 rows (2 items per row).

3. Final Answer:

   2 columns and 2 rows -> Option A

4. Quick Check:

   4 items / 2 columns = 2 rows [OK]

Hint: Rows = total items ÷ columns (round up) [OK]

Common Mistakes:

• Assuming columns equal number of items
• Confusing rows and columns count
• Ignoring fixed columns setting

4. Identify the error in this LazyVerticalGrid code:

LazyVerticalGrid(columns = GridCells.Fixed(3)) {
  items(5) { index ->
    Text(text = "Item $index")
  }
  item {
    Text(text = "Footer")
  }
}

medium

A. Using both items and item inside LazyVerticalGrid is invalid

B. The item block should be inside items block

C. No error; code is correct

D. GridCells.Fixed cannot be used with 3 columns

Solution

1. Step 1: Check usage of items and item

   LazyVerticalGrid supports both items (multiple) and item (single) blocks for content.

2. Step 2: Verify GridCells.Fixed usage

   GridCells.Fixed(3) is valid to set 3 columns.

3. Final Answer:

   No error; code is correct -> Option C

4. Quick Check:

   items and item can coexist = B [OK]

Hint: items and item blocks can be mixed in LazyGrid [OK]

Common Mistakes:

• Thinking item block must be inside items
• Assuming GridCells.Fixed(3) is invalid
• Believing multiple content blocks cause error

5. You want to create a photo gallery with images that adapt to screen width, showing as many columns as fit with a minimum size of 120.dp per item. Which LazyVerticalGrid setup is correct?

hard

A. LazyVerticalGrid(columns = GridCells.Fixed(3)) { /* images */ }

B. LazyVerticalGrid(columns = GridCells.Fixed(120)) { /* images */ }

C. LazyVerticalGrid(columns = GridCells.Adaptive(3)) { /* images */ }

D. LazyVerticalGrid(columns = GridCells.Adaptive(120.dp)) { /* images */ }

Solution

1. Step 1: Understand adaptive columns

   GridCells.Adaptive sets columns based on minimum item size, adapting to screen width.

2. Step 2: Match requirement to code

   LazyVerticalGrid(columns = GridCells.Adaptive(120.dp)) { /* images */ } uses GridCells.Adaptive(120.dp), which fits the requirement of minimum 120.dp per item and adapts columns.

3. Final Answer:

   LazyVerticalGrid(columns = GridCells.Adaptive(120.dp)) { /* images */ } -> Option D

4. Quick Check:

   Adaptive columns use minimum size = A [OK]

Hint: Use GridCells.Adaptive(minSize) for responsive columns [OK]

Common Mistakes:

• Using Fixed with pixel count instead of dp
• Confusing number of columns with minimum size
• Using Adaptive with integer instead of dp