Modularization in Android Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Kotlin function inside a module.

Android Kotlin

fun greet() : String {
    return [1]
}

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

A"Hello from module!"

Bprintln("Hello from module!")

CHello from module!

Dreturn "Hello from module!"

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the string

Using println instead of returning a string

The function must return a String literal, so the text must be in quotes.

2fill in blank

medium

Complete the code to import a function from another module.

Android Kotlin

import com.example.moduleA.[1]

fun main() {
    println(greet())
}

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

AMainActivity

Bgreet

CModuleA

Dgreeting

Attempts:

3 left

💡 Hint

Common Mistakes

Importing the module name instead of the function

Using wrong function names

You import the function name exactly to use it in your code.

3fill in blank

hard

Fix the error in the module dependency declaration in build.gradle.kts.

Android Kotlin

dependencies {
    implementation(project([1]))
}

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

A":moduleB"

B"moduleB"

CmoduleB

D"\":moduleB\""

Attempts:

3 left

💡 Hint

Common Mistakes

Adding extra quotes inside the string

Omitting the colon prefix

Using just the module name without quotes

The project path must be a string with colon prefix and no extra quotes inside.

4fill in blank

hard

Fill both blanks to create a Kotlin interface and implement it in a class.

Android Kotlin

interface [1] {
    fun sayHello(): String
}

class Greeter : [2] {
    override fun sayHello() = "Hi from Greeter"
}

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

AGreeting

BGreeter

Attempts:

3 left

💡 Hint

Common Mistakes

Using the class name as interface

Mismatching names between interface and implementation

The interface is named Greeting and the class implements it by name.

5fill in blank

hard

Fill all three blanks to define a module-level constant and use it in a function.

Android Kotlin

const val [1] = [2]

fun printVersion() {
    println("App version: $[3]")
}

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

AAPP_VERSION

B"1.0.0"

DVERSION

Attempts:

3 left

💡 Hint

Common Mistakes

Not using quotes for the string value

Using different names for constant and usage

Define APP_VERSION as a constant string and use it inside the function.

Practice

1. What is the main purpose of modularization in Android Kotlin projects?

easy

A. To avoid using dependencies

B. To write all code in a single file

C. To split the app into smaller, manageable parts

D. To increase app size unnecessarily

Solution

1. Step 1: Understand modularization concept

   Modularization means dividing the app into smaller parts called modules.

2. Step 2: Identify the purpose

   This helps manage code better and makes development easier.

3. Final Answer:

   To split the app into smaller, manageable parts -> Option C

4. Quick Check:

   Modularization = split app into parts [OK]

Hint: Modularization means breaking app into smaller parts [OK]

Common Mistakes:

• Thinking modularization means writing all code in one file
• Believing modularization avoids dependencies
• Assuming modularization increases app size

2. Which of the following is the correct way to add a module dependency in a Kotlin Android project build file?

easy

A. import module ":mylibrary"

B. add dependency ":mylibrary"

C. include module ":mylibrary"

D. implementation project(":mylibrary")

Solution

1. Step 1: Recall Gradle syntax for module dependencies

   In build.gradle.kts, dependencies use implementation(project(":moduleName")) syntax.

2. Step 2: Match correct syntax

   implementation project(":mylibrary") matches this syntax exactly.

3. Final Answer:

   implementation project(":mylibrary") -> Option D

4. Quick Check:

   Module dependency syntax = implementation project(":module") [OK]

Hint: Use implementation project(":moduleName") to add module dependency [OK]

Common Mistakes:

• Using import or include keywords incorrectly
• Forgetting to wrap module name in project()
• Using add dependency which is not Gradle syntax

3. Given two modules: app and utils. If app depends on utils, what happens when you call a function defined in utils from app?

medium

A. The function runs correctly if dependency is set

B. The app crashes at runtime

C. The function is ignored during build

D. The app fails to compile

Solution

1. Step 1: Understand module dependency effect

   If app depends on utils, app can use utils code.

2. Step 2: Predict behavior when calling function

   Calling a function from utils works if dependency is correctly set, so function runs fine.

3. Final Answer:

   The function runs correctly if dependency is set -> Option A

4. Quick Check:

   Dependency set = function runs [OK]

Hint: Module dependency allows code sharing and function calls [OK]

Common Mistakes:

• Assuming app crashes without error
• Thinking function is ignored during build
• Believing app fails to compile without error

4. You added a module dependency in app on library, but the app fails to compile with "Unresolved reference" errors for library classes. What is the most likely cause?

medium

A. The project was not synced after adding dependency

B. The library module has no Kotlin files

C. The app module is missing AndroidManifest.xml

D. The dependency was added in the wrong build.gradle file

Solution

1. Step 1: Identify cause of unresolved references

   Unresolved references after adding dependency usually mean changes haven't taken effect in the IDE.

2. Step 2: Check sync status

   The project must be synced after modifying build.gradle for dependencies to resolve.

3. Final Answer:

   The project was not synced after adding dependency -> Option A

4. Quick Check:

   No sync = unresolved references [OK]

Hint: Sync project after adding dependencies [OK]

Common Mistakes:

• Adding dependency in wrong build.gradle file
• Library module has no Kotlin files
• App module missing AndroidManifest.xml

5. You want to create a modularized Android app with three modules: app, network, and database. The app module should use both network and database, but network should not depend on database. How should you set dependencies?

hard

A. network depends on database; app depends on network

B. app depends on network and database; network has no dependencies

C. database depends on network; app depends on database

D. app depends only on network; network depends on database

Solution

1. Step 1: Analyze dependency requirements

   App needs both network and database modules. Network must not depend on database.

2. Step 2: Set dependencies accordingly

   App depends on both network and database. Network has no dependencies to database.

3. Final Answer:

   app depends on network and database; network has no dependencies -> Option B

4. Quick Check:

   App uses both; network independent [OK]

Hint: Only app depends on both; network stays independent [OK]

Common Mistakes:

• Making network depend on database incorrectly
• Setting app to depend only on network
• Confusing dependency directions