Repository pattern in Android Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Repository pattern in Android development?

The Repository pattern is a way to organize data access. It acts like a middleman between your app and data sources (like databases or web services). It helps keep your code clean and easy to maintain.

beginner

Why use a Repository in your app?

Using a Repository helps separate data logic from UI logic. It makes your app easier to test and change because data access is all in one place.

intermediate

In the Repository pattern, what kinds of data sources might the Repository manage?

A Repository can manage local databases, remote web APIs, or cached data. It decides where to get data from and when.

intermediate

How does the Repository pattern improve testing in Android apps?

Because the Repository hides data sources, you can replace it with fake data during tests. This makes testing easier and faster without needing real databases or network calls.

beginner

Show a simple Kotlin interface for a UserRepository with a function to get a user by ID.

interface UserRepository { suspend fun getUserById(id: String): User? }

What is the main role of a Repository in Android apps?

A To manage data access and provide a clean API for data

B To handle user interface layout

C To manage app navigation

D To store app settings

The Repository manages data access and provides a clean API for the rest of the app.

Which of these is NOT a typical data source managed by a Repository?

A User interface components

B Remote web API

C Cached data

D Local database

User interface components are not data sources; they are part of the UI layer.

How does the Repository pattern help with testing?

A It automatically writes test cases

B It makes UI testing unnecessary

C It allows replacing real data sources with fake ones

D It slows down tests

Repositories can be replaced with fake versions during tests to avoid real database or network calls.

Which Kotlin keyword is commonly used in Repository functions to handle long-running tasks like network calls?

A var

B val

C fun

D suspend

The 'suspend' keyword marks functions that can be paused and resumed, useful for asynchronous tasks.

What is a benefit of having a Repository interface in your app?

A It makes the app run faster

B It allows different implementations without changing the app code

C It reduces app size

D It handles user input

An interface lets you swap different data sources or mock implementations easily.

Explain the Repository pattern and why it is useful in Android app development.

Think about how your app gets data and how to keep that code organized.

Describe how you would implement a simple Repository interface in Kotlin for fetching user data.

Focus on the function signature and the use of suspend for network or database calls.

Practice

1. What is the main purpose of the Repository pattern in Android Kotlin development?

easy

A. To separate data access logic from UI and business logic

B. To handle user interface animations

C. To manage app navigation between screens

D. To store UI layout XML files

Solution

1. Step 1: Understand the role of Repository

   The Repository pattern is designed to manage data operations and provide a clean API to the rest of the app.

2. Step 2: Identify separation of concerns

   It separates data handling from UI and business logic, making the app easier to maintain and test.

3. Final Answer:

   To separate data access logic from UI and business logic -> Option A

4. Quick Check:

   Repository pattern = separation of data logic [OK]

Hint: Repository separates data logic from UI logic [OK]

Common Mistakes:

• Confusing Repository with UI components
• Thinking Repository manages navigation
• Assuming Repository stores layout files

2. Which of the following is the correct way to declare a Repository interface in Kotlin?

easy

A. interface UserRepository { fun getUser(id: Int): User }

B. class UserRepository { fun getUser(id: Int): User }

C. fun UserRepository() { return User }

D. val UserRepository = object { fun getUser(id: Int): User }

Solution

1. Step 1: Identify interface syntax in Kotlin

   Interfaces in Kotlin are declared with the interface keyword followed by function signatures without bodies.

2. Step 2: Match the correct declaration

   interface UserRepository { fun getUser(id: Int): User } correctly declares an interface with a function signature. class UserRepository { fun getUser(id: Int): User } is a class, not an interface. Options A, B, and C have incorrect syntax.

3. Final Answer:

   interface UserRepository { fun getUser(id: Int): User } -> Option A

4. Quick Check:

   Interface declaration uses interface keyword [OK]

Hint: Interfaces use 'interface' keyword with function signatures [OK]

Common Mistakes:

• Using class instead of interface for Repository
• Incorrect function syntax inside interface
• Trying to instantiate interface directly

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

class UserRepository {
  fun getUserName(id: Int): String = if (id == 1) "Alice" else "Unknown"
}

fun main() {
  val repo = UserRepository()
  println(repo.getUserName(1))
  println(repo.getUserName(2))
}

medium

A. Unknown\nAlice

B. Alice\nUnknown

C. 1\n2

D. Alice\nAlice

Solution

1. Step 1: Analyze getUserName function logic

   The function returns "Alice" if id is 1, otherwise "Unknown".

2. Step 2: Trace the calls in main()

   Calling getUserName(1) returns "Alice". Calling getUserName(2) returns "Unknown".

3. Final Answer:

   Alice\nUnknown -> Option B

4. Quick Check:

   id==1 returns Alice, else Unknown [OK]

Hint: Check condition for id==1 to get 'Alice' [OK]

Common Mistakes:

• Mixing up return values for different ids
• Assuming both calls return 'Alice'
• Confusing id with returned string

4. Identify the error in this Repository implementation:

class UserRepository {
  fun getUser(id: Int): User {
    return User(id, name)
  }
}

Assuming name is not defined anywhere.

medium

A. User class is not imported

B. Missing return type for getUser function

C. Variable 'name' is undefined causing a compilation error

D. Function getUser should be abstract

Solution

1. Step 1: Check variables used in return statement

   The function returns User(id, name), but name is not declared or passed.

2. Step 2: Identify compilation error

   Using an undefined variable causes a compilation error in Kotlin.

3. Final Answer:

   Variable 'name' is undefined causing a compilation error -> Option C

4. Quick Check:

   Undefined variables cause compile errors [OK]

Hint: Check all variables are defined before use [OK]

Common Mistakes:

• Ignoring undefined variables
• Assuming missing imports cause error here
• Thinking function must be abstract

5. You want to create a Repository that fetches user data from both a local database and a remote API. Which approach best follows the Repository pattern principles?

hard

A. Call the local database and remote API directly from the UI layer

B. Store all user data in the UI components for quick access

C. Create separate Repository classes for local and remote and call both from UI

D. Create a Repository class that decides whether to fetch from local or remote and exposes a single method to get user data

Solution

1. Step 1: Understand Repository responsibility

   The Repository should act as a single source of truth and hide data sources from the UI.

2. Step 2: Choose approach that centralizes data logic

   Create a Repository class that decides whether to fetch from local or remote and exposes a single method to get user data centralizes data fetching logic inside the Repository, deciding between local and remote sources.

3. Step 3: Avoid direct data calls in UI

   Options A and C expose data sources to UI, breaking separation of concerns. Store all user data in the UI components for quick access mixes data with UI, which is bad practice.

4. Final Answer:

   Create a Repository class that decides whether to fetch from local or remote and exposes a single method to get user data -> Option D

5. Quick Check:

   Repository centralizes data access [OK]

Hint: Repository hides data sources behind one interface [OK]

Common Mistakes:

• Calling data sources directly from UI
• Splitting data logic across UI and multiple classes
• Storing data inside UI components