Why architecture scales codebases in Android Kotlin - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a ViewModel class in Kotlin.

Android Kotlin

class MainViewModel : [1]() {
    // ViewModel logic here
}

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

AViewModel

BFragment

CActivity

DService

Attempts:

3 left

💡 Hint

Common Mistakes

Using Activity or Fragment instead of ViewModel.

Confusing Service with ViewModel.

The ViewModel class helps keep UI data separate from UI controllers, which is key for scalable architecture.

2fill in blank

medium

Complete the code to observe LiveData in an Activity.

Android Kotlin

viewModel.data.observe([1]) { value ->
    // update UI with value
}

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

Athis

BlifecycleOwner

CviewLifecycleOwner

Dcontext

Attempts:

3 left

💡 Hint

Common Mistakes

Using viewLifecycleOwner which is for Fragments.

Passing lifecycleOwner without context.

In an Activity, you pass 'this' as the LifecycleOwner to observe LiveData.

3fill in blank

hard

Fix the error in the repository pattern code by completing the interface declaration.

Android Kotlin

interface [1] {
    fun getUser(id: String): User
}

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

AUserDataSource

BUserViewModel

CUserService

DUserRepository

Attempts:

3 left

💡 Hint

Common Mistakes

Naming it UserViewModel which is for UI logic.

Using UserService which is more network related.

The repository interface is commonly named UserRepository to abstract data operations.

4fill in blank

hard

Fill both blanks to complete the ViewModel factory code for dependency injection.

Android Kotlin

class [1](private val repository: [2]) : ViewModel() {
    // ViewModel code
}

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

AMainViewModel

BUserRepository

CUserService

DMainActivity

Attempts:

3 left

💡 Hint

Common Mistakes

Using MainActivity as class name instead of ViewModel.

Injecting UserService directly instead of repository.

The ViewModel class is named MainViewModel and it takes UserRepository as a dependency.

5fill in blank

hard

Fill all three blanks to complete the Kotlin code for a simple MVVM data flow.

Android Kotlin

class [1](private val [2]: [3]) : ViewModel() {
    val data = MutableLiveData<String>()
}

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

AUserViewModel

Brepository

CUserRepository

DMainActivity

Attempts:

3 left

💡 Hint

Common Mistakes

Using MainActivity as class name.

Naming the repository parameter incorrectly.

The ViewModel is UserViewModel, it has a repository property of type UserRepository injected.

Practice

1. Why is using an architecture pattern important when building Android apps?

easy

A. It automatically writes code for you.

B. It makes the app run faster on all devices.

C. It organizes code into clear parts making it easier to manage.

D. It removes the need for testing the app.

Solution

1. Step 1: Understand the role of architecture

   Architecture divides the app into parts like UI, data, and logic to keep code organized.

2. Step 2: Recognize benefits of organization

   Organized code is easier to grow, fix, and share among team members.

3. Final Answer:

   It organizes code into clear parts making it easier to manage. -> Option C

4. Quick Check:

   Architecture = Organized code [OK]

Hint: Architecture means clear code parts for easier work [OK]

Common Mistakes:

• Thinking architecture speeds up app performance directly
• Believing architecture writes code automatically
• Assuming architecture removes testing needs

2. Which Kotlin syntax correctly defines a simple interface for a repository in an architecture pattern?

easy

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

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

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

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

Solution

1. Step 1: Identify correct interface syntax

   Kotlin interfaces use the keyword 'interface' followed by function signatures with 'fun'.

2. Step 2: Check function declaration format

   Functions inside interfaces must have 'fun' and proper return type with parentheses.

3. Final Answer:

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

4. Quick Check:

   Interface + fun + return type = interface UserRepository { fun getUser(id: Int): User } [OK]

Hint: Interfaces need 'fun' before functions in Kotlin [OK]

Common Mistakes:

• Omitting 'fun' keyword inside interface
• Using class instead of interface
• Missing parentheses in function declaration

3. Given this simplified code snippet in an MVVM architecture, what will be printed?

class UserViewModel(private val repo: UserRepository) {
  fun loadUser(id: Int) = repo.getUser(id)
}

class FakeRepo : UserRepository {
  override fun getUser(id: Int) = "User$id"
}

fun main() {
  val vm = UserViewModel(FakeRepo())
  println(vm.loadUser(5))
}

medium

A. Error: getUser not implemented

B. User5

C. 5

D. User

Solution

1. Step 1: Trace the method calls

   Main creates UserViewModel with FakeRepo, then calls loadUser(5), which calls repo.getUser(5).

2. Step 2: Check FakeRepo implementation

   FakeRepo's getUser returns "User" + id, so getUser(5) returns "User5".

3. Final Answer:

   User5 -> Option B

4. Quick Check:

   FakeRepo returns "User" + id = User5 [OK]

Hint: Follow method calls and return values step-by-step [OK]

Common Mistakes:

• Ignoring the parameter passed to getUser
• Assuming getUser returns only id
• Thinking getUser is not implemented

4. What is the main problem in this code snippet that breaks the architecture pattern?

class UserViewModel {
  fun getUser(id: Int) = UserRepository().getUser(id)
}

class UserRepository {
  fun getUser(id: Int) = "User$id"
}

medium

A. UserViewModel creates UserRepository directly, causing tight coupling.

B. UserRepository does not implement an interface.

C. getUser function is missing return type.

D. UserViewModel should not have any functions.

Solution

1. Step 1: Identify dependency creation

   UserViewModel creates UserRepository inside its method, which tightly couples them.

2. Step 2: Understand architecture principle

   Architecture encourages passing dependencies from outside (dependency injection) to keep parts independent.

3. Final Answer:

   UserViewModel creates UserRepository directly, causing tight coupling. -> Option A

4. Quick Check:

   Direct creation = tight coupling = UserViewModel creates UserRepository directly, causing tight coupling. [OK]

Hint: Avoid creating dependencies inside classes; use injection [OK]

Common Mistakes:

• Thinking missing interface is the main issue
• Ignoring tight coupling caused by direct creation
• Believing functions are not allowed in ViewModel

5. You want to scale your Android app with many developers working on UI, data, and logic separately. Which architecture approach best supports this and why?

hard

A. Use a single Activity with all code inside to keep it simple.

B. Use no architecture and let each developer write code anywhere.

C. Write all code in one ViewModel to avoid confusion.

D. Use MVVM because it separates UI, business logic, and data layers clearly.

Solution

1. Step 1: Identify architecture benefits for teams

   MVVM separates UI (View), logic (ViewModel), and data (Model), allowing parallel work.

2. Step 2: Compare with other options

   Single Activity or no architecture mixes code, causing confusion and hard maintenance.

3. Final Answer:

   Use MVVM because it separates UI, business logic, and data layers clearly. -> Option D

4. Quick Check:

   Clear separation helps teams scale = Use MVVM because it separates UI, business logic, and data layers clearly. [OK]

Hint: Choose architecture that splits work clearly for teams [OK]

Common Mistakes:

• Thinking one big class is easier for teams
• Ignoring benefits of separation in architecture
• Believing no architecture scales better