Modularization in Android Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is modularization in Android development?

Modularization means splitting an app into smaller, independent parts called modules. Each module handles a specific feature or function, making the app easier to build and maintain.

beginner

Name two benefits of modularization in Android apps.

1. Faster build times because only changed modules need rebuilding.
2. Easier teamwork since developers can work on separate modules without conflicts.

intermediate

What is a feature module in Android modularization?

A feature module is a self-contained part of the app that implements a specific feature, like login or profile. It can be developed and tested independently.

intermediate

How does modularization improve app scalability?

By dividing the app into modules, you can add or update features without affecting the whole app. This makes it easier to grow and change the app over time.

intermediate

What is the role of Gradle in Android modularization?

Gradle manages modules by defining dependencies and build rules. It helps build each module separately and combine them into the final app.

What does modularization help improve in Android apps?

A Build speed and code organization

B Only UI design

C Battery usage

D Screen resolution

Modularization improves build speed by building only changed modules and helps organize code better.

Which of these is a typical module in Android modularization?

A Feature module

B Color module

C Battery module

D Screen size module

Feature modules contain specific app features like login or settings.

How does modularization help teamwork?

A It slows down development

B Everyone edits the same file

C Developers work on separate modules without conflicts

D It removes the need for version control

Separate modules let developers work independently, reducing conflicts.

What tool manages module dependencies in Android projects?

A Git

B Firebase

C Android Studio Layout Editor

D Gradle

Gradle handles building modules and their dependencies.

Which is NOT a benefit of modularization?

A Faster build times

B More app crashes

C Better code reuse

D Easier testing

Modularization reduces crashes by isolating code, not increasing them.

Explain what modularization is and why it is useful in Android app development.

Think about how breaking a big task into smaller parts helps.

Describe how Gradle supports modularization in Android projects.

Gradle is like the app's builder and organizer.

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