Pagination basics in Android Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is pagination in mobile app development?

Pagination is a technique to load and display data in small chunks or pages instead of all at once. It helps apps run faster and use less memory.

beginner

Why do we use pagination in Android apps?

We use pagination to avoid loading too much data at once, which can slow down the app or cause crashes. It improves user experience by loading data as needed.

beginner

Name two common ways to trigger loading the next page in a list.

1. User scrolls to the bottom of the list (infinite scroll). 2. User taps a "Load More" button.

beginner

What Android component helps to display a scrollable list that supports pagination?

RecyclerView is commonly used to display scrollable lists. It works well with pagination by loading more items as the user scrolls.

intermediate

What is a simple way to detect when to load the next page in a RecyclerView?

You can add a scroll listener to RecyclerView that checks if the user has scrolled near the bottom, then trigger loading the next page.

What is the main benefit of using pagination in mobile apps?

A Load all data at once for faster access

B Prevent user from scrolling

C Make the app use more battery

D Reduce app memory use and improve performance

Pagination reduces memory use and improves performance by loading data in small chunks.

Which Android view is best suited for showing a paginated list?

A TextView

B ImageView

C RecyclerView

D Button

RecyclerView efficiently displays scrollable lists and supports pagination.

How can an app know when to load the next page in a list?

A When user taps the screen

B When user scrolls near the bottom

C When app starts

D When user closes the app

Loading the next page usually happens when the user scrolls near the bottom of the list.

What is NOT a common way to implement pagination?

A Loading all data at once

B Load More button

C Infinite scroll

D Loading data page by page

Loading all data at once is not pagination; it can cause performance issues.

Which of these is a good practice when implementing pagination?

A Load next page only after user scrolls

B Load all pages at app start

C Ignore user scrolling

D Show no feedback when loading

Loading next page after user scrolls improves performance and user experience.

Explain how pagination improves app performance and user experience.

Think about what happens if you load all data at once.

Describe how you would detect when to load the next page in a RecyclerView.

Consider what happens when user scrolls near the bottom.

Practice

1. What is the main purpose of pagination in mobile apps?

easy

A. To split data into smaller pages for faster loading and less memory use

B. To combine all data into one big list

C. To delete old data permanently

D. To change the app's theme colors

Solution

1. Step 1: Understand pagination concept

   Pagination divides large data into smaller parts called pages.

2. Step 2: Identify benefits of pagination

   This helps apps load data faster and use less memory by not loading everything at once.

3. Final Answer:

   To split data into smaller pages for faster loading and less memory use -> Option A

4. Quick Check:

   Pagination = split data for speed and memory [OK]

Hint: Pagination means loading data in small parts, not all at once [OK]

Common Mistakes:

• Thinking pagination deletes data
• Believing pagination merges all data
• Confusing pagination with UI themes

2. Which Kotlin code snippet correctly represents fetching page 2 with page size 10?

easy

A. val page = 2
val size = 10
val start = size - page

B. val page = 2
val size = 10
val start = page * size

C. val page = 2
val size = 10
val start = (page - 1) * size

D. val page = 2
val size = 10
val start = page + size

Solution

1. Step 1: Calculate start index for page 2

   Start index = (page number - 1) * page size, so (2 - 1) * 10 = 10.

2. Step 2: Check code snippets

   val page = 2 val size = 10 val start = (page - 1) * size uses correct formula; others use wrong math.

3. Final Answer:

   val start = (page - 1) * size -> Option C

4. Quick Check:

   Start index formula = (page - 1) * size [OK]

Hint: Start index = (page - 1) times page size [OK]

Common Mistakes:

• Using page * size instead of (page - 1) * size
• Subtracting page from size incorrectly
• Adding page and size instead of multiplying

3. Given this Kotlin code snippet, what will be printed?

val page = 3
val size = 5
val start = (page - 1) * size
println("Loading items from index $start to ${start + size - 1}")

medium

A. Loading items from index 10 to 14

B. Loading items from index 15 to 19

C. Loading items from index 5 to 9

D. Loading items from index 0 to 4

Solution

1. Step 1: Calculate start index

   start = (3 - 1) * 5 = 2 * 5 = 10.

2. Step 2: Calculate end index

   end = start + size - 1 = 10 + 5 - 1 = 14.

3. Final Answer:

   Loading items from index 10 to 14 -> Option A

4. Quick Check:

   Start=10, End=14 [OK]

Hint: End index = start + size - 1 for page ranges [OK]

Common Mistakes:

• Calculating start as page * size
• Forgetting to subtract 1 for end index
• Mixing up start and end indexes

4. What is wrong with this Kotlin pagination code?

val page = 1
val size = 10
val start = page * size
println("Loading items from index $start to ${start + size - 1}")

medium

A. Page size should be multiplied by 2

B. Start index calculation is off by one page

C. Page number should start from 0

D. No error, code is correct

Solution

1. Step 1: Check start index formula

   Correct formula is (page - 1) * size, but code uses page * size.

2. Step 2: Understand impact

   For page 1, start should be 0, but code gives 10, skipping first 10 items.

3. Final Answer:

   Start index calculation is off by one page -> Option B

4. Quick Check:

   Start index must be (page - 1) * size [OK]

Hint: Page 1 start index is zero, so subtract 1 in formula [OK]

Common Mistakes:

• Using page * size instead of (page - 1) * size
• Starting page count at 0 incorrectly
• Assuming no off-by-one errors

5. You want to load pages of data in your app. If the total data size is 47 items and page size is 10, how many pages do you need to load all items?

hard

A. 4

B. 7

C. 6

D. 5

Solution

1. Step 1: Calculate full pages

   47 items divided by 10 per page gives 4 full pages (4 * 10 = 40 items).

2. Step 2: Account for leftover items

   Remaining 7 items need an extra page, so total pages = 4 + 1 = 5.

3. Step 3: Re-check calculation

   Wait, 4 full pages cover 40 items, leftover 7 items need 1 page, total 5 pages.

4. Final Answer:

   5 -> Option D

5. Quick Check:

   Pages = ceil(47/10) = 5 [OK]

Hint: Divide total items by page size and round up [OK]

Common Mistakes:

• Using integer division without rounding up
• Counting only full pages
• Miscounting leftover items