Repository pattern in depth in Android Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a repository interface in Kotlin.

Android Kotlin

interface UserRepository {
    fun getUserById(id: Int): [1]
}

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

AInt

BString

CUser

DBoolean

Attempts:

3 left

💡 Hint

Common Mistakes

Returning a primitive type like Int or String instead of a User object.

Forgetting to specify the return type.

The repository interface defines a method that returns a User object by its ID.

2fill in blank

medium

Complete the code to implement the repository class that fetches data from a local data source.

Android Kotlin

class UserRepositoryImpl(private val localDataSource: LocalDataSource) : UserRepository {
    override fun getUserById(id: Int): User {
        return [1].getUser(id)
    }
}

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

AremoteDataSource

BuserService

CuserDao

DlocalDataSource

Attempts:

3 left

💡 Hint

Common Mistakes

Using remoteDataSource instead of localDataSource.

Using undefined variables like userDao or userService.

The repository implementation uses the localDataSource to get the user data.

3fill in blank

hard

Fix the error in the repository method to return a nullable User when not found.

Android Kotlin

override fun getUserById(id: Int): [1] {
    return localDataSource.getUser(id)
}

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

ABoolean

BUser?

CList<User>

DUser

Attempts:

3 left

💡 Hint

Common Mistakes

Returning a non-nullable User type which causes errors if user is missing.

Returning a list or Boolean which does not match the method purpose.

The method should return User? to indicate the user might not be found (nullable).

4fill in blank

hard

Fill both blanks to create a repository method that saves a user and returns success status.

Android Kotlin

fun saveUser(user: User): [1] {
    val result = localDataSource.[2](user)
    return result > 0
}

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

ABoolean

BInt

CsaveUser

DinsertUser

Attempts:

3 left

💡 Hint

Common Mistakes

Returning Int instead of Boolean.

Calling a method named saveUser which does not exist in data source.

The method returns a Boolean indicating success. It calls insertUser on the local data source.

5fill in blank

hard

Fill all three blanks to define a repository method that fetches users filtered by age greater than a value.

Android Kotlin

fun getUsersOlderThan(age: Int): List<User> {
    return localDataSource.getUsers().filter { user -> user.[1] [2] [3] }
}

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

Aage

B>

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong property like name instead of age.

Using wrong comparison operators.

The filter checks if the user's age is greater than the given age parameter.

Practice

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

easy

A. To separate data access logic from UI components

B. To handle user interface animations

C. To manage app navigation between screens

D. To define the app's theme and styles

Solution

1. Step 1: Understand the role of Repository

   The Repository pattern abstracts data sources and provides a clean API for data access.

2. Step 2: Identify separation of concerns

   This pattern separates data handling from UI code, improving maintainability and testability.

3. Final Answer:

   To separate data access logic from UI components -> Option A

4. Quick Check:

   Repository pattern = separation of data and UI [OK]

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

Common Mistakes:

• Confusing Repository with UI or navigation components
• Thinking Repository manages UI animations
• Assuming Repository handles app styling

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

easy

A. object UserRepository { val user = User() }

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

C. fun UserRepository() { return User }

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

Solution

1. Step 1: Identify interface syntax in Kotlin

   Interfaces use the interface keyword and declare functions without bodies.

2. Step 2: Check each option

   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 interface. fun UserRepository() { return User } is invalid syntax. object UserRepository { val user = User() } is an object, not an interface.

3. Final Answer:

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

4. Quick Check:

   Kotlin interface syntax = interface UserRepository { fun getUser(id: Int): User } [OK]

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

Common Mistakes:

• Using class instead of interface for Repository declaration
• Writing invalid function syntax inside interface
• Confusing object declaration with interface

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

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

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

medium

A. 1\n2

B. Unknown\nAlice

C. Alice\nUnknown

D. Alice\nAlice

Solution

1. Step 1: Analyze getUserName function

   If the id is 1, it returns "Alice", otherwise "Unknown".

2. Step 2: Trace main function calls

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

3. Final Answer:

   Alice\nUnknown -> Option C

4. Quick Check:

   id=1 returns Alice, else Unknown [OK]

Hint: Check if condition for id equals 1 [OK]

Common Mistakes:

• Mixing up return values for different ids
• Assuming numeric output instead of strings
• Confusing order of print statements

4. Identify the error in this Kotlin Repository implementation:

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

class User(val name: String)

fun main() {
  val repo = UserRepository()
  val user = repo.getUser(1)
  println(user.name)
}

medium

A. getUser function should return String, not User

B. User() requires a name parameter but none provided

C. UserRepository class must be an interface

D. println cannot print user.name

Solution

1. Step 1: Check User class constructor

   User class requires a name parameter in its constructor.

2. Step 2: Check UserRepository getUser return

   getUser returns User() without passing name, causing a compile error.

3. Final Answer:

   User() requires a name parameter but none provided -> Option B

4. Quick Check:

   Missing constructor argument causes error [OK]

Hint: Check constructor parameters when creating objects [OK]

Common Mistakes:

• Ignoring required constructor parameters
• Thinking class must be interface for Repository
• Assuming println can't print properties

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. Create a Repository that combines local and remote data sources and exposes a unified API

B. Call the local database directly from UI and ignore remote API

C. Make UI components call remote API and local database separately

D. Use only remote API and discard local data storage

Solution

1. Step 1: Understand Repository role with multiple data sources

   The Repository should abstract and combine data from local and remote sources.

2. Step 2: Evaluate options for separation and abstraction

   Create a Repository that combines local and remote data sources and exposes a unified API correctly combines data sources and exposes a clean API. The other options break separation or ignore data sources.

3. Final Answer:

   Create a Repository that combines local and remote data sources and exposes a unified API -> Option A

4. Quick Check:

   Repository unifies data sources for UI [OK]

Hint: Repository unifies multiple data sources behind one API [OK]

Common Mistakes:

• Accessing data sources directly from UI
• Ignoring one data source completely
• Mixing data calls in UI instead of Repository