Repository pattern in depth in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Repository Role

What is the main purpose of the Repository pattern in Android app development?

A To abstract data sources and provide a clean API for data access

B To manage network requests directly in the UI layer

C To handle UI rendering and user interactions

D To store UI state and lifecycle events

💡 Hint

Think about separating data logic from UI logic.

The Repository pattern abstracts the data sources (like databases, network, cache) and provides a clean API for the rest of the app to access data without knowing where it comes from.

❓ ui_behavior

intermediate

Repository and LiveData Interaction

Given a Repository that returns LiveData from a Room database, what happens in the UI when the database data changes?

A The UI automatically updates because LiveData notifies observers of changes

B The UI crashes because LiveData cannot be observed

C The UI must manually refresh data by calling the Repository again

D The UI shows stale data until the app restarts

💡 Hint

LiveData is lifecycle-aware and updates observers automatically.

LiveData observes the database and notifies the UI when data changes, so the UI updates automatically without manual refresh.

❓ lifecycle

advanced

Repository and ViewModel Lifecycle

Which statement best describes the lifecycle relationship between a Repository and a ViewModel in Android?

A The Repository is destroyed before the ViewModel to free resources

B The Repository typically outlives the ViewModel and can be shared across multiple ViewModels

C The ViewModel and Repository have the same lifecycle and are always created and destroyed together

D The Repository is recreated every time the ViewModel is accessed

💡 Hint

Consider how many ViewModels might use the same data source.

Repositories are often singleton or scoped to the application, so they can be shared and outlive ViewModels, which are tied to UI lifecycle.

❓ navigation

advanced

Repository Impact on Navigation Flow

How does using a Repository pattern affect navigation between screens that share data in an Android app?

A It prevents data sharing and requires passing data via intents only

B It forces each screen to reload data independently, causing delays

C It allows screens to share data easily by accessing the same Repository instance

D It causes navigation to fail if the Repository is not passed explicitly

💡 Hint

Think about centralized data access and sharing.

A shared Repository instance provides a single source of truth, enabling multiple screens to access and update data consistently without redundant reloads.

🔧 Debug

expert

Debugging Repository Data Inconsistency

You notice your UI shows outdated data even though the Repository fetches fresh data from the network. Which is the most likely cause?

Android Kotlin

class UserRepository(private val api: ApiService, private val dao: UserDao) {
  val users = dao.getUsersLiveData()

  suspend fun refreshUsers() {
    val response = api.fetchUsers()
    if (response.isSuccessful) {
      dao.insertUsers(response.body() ?: emptyList())
    }
  }
}

A The dao.insertUsers method does not insert data into the database

B The LiveData from dao.getUsersLiveData() does not notify observers on database changes

C The API fetchUsers method returns cached data instead of fresh data

D The refreshUsers function is not called or awaited properly, so data is not updated in the database

💡 Hint

Check if the network refresh is triggered and completed before UI update.

If refreshUsers is not called or awaited, the database is not updated, so LiveData emits old data causing UI to show outdated info.