Modularization in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use modularization in Android apps?

Which of the following is the main benefit of modularizing an Android app into multiple modules?

A It improves build times and allows independent development of features.

B It automatically increases the app's runtime speed without code changes.

C It forces all code to be in one file for easier debugging.

D It disables the use of external libraries to reduce app size.

💡 Hint

Think about how dividing code helps teams and build processes.

Modularization breaks the app into smaller parts, which can be built and tested independently, improving build speed and team collaboration.

❓ ui_behavior

intermediate

Module dependency effect on UI

If a feature module depends on a core module that provides UI components, what happens if the core module is removed from the project?

A The app will run normally without any UI changes.

B The feature module will automatically recreate the core UI components.

C The feature module will convert to a library module automatically.

D The feature module's UI components will fail to compile or run.

💡 Hint

Consider what happens when a required module is missing.

If a module depends on another for UI components, removing the core module breaks those dependencies, causing compile or runtime errors.

❓ lifecycle

advanced

Impact of modularization on app lifecycle

How does modularization affect the Android app lifecycle when modules are loaded dynamically at runtime?

A Modules can be loaded or unloaded without restarting the entire app, affecting lifecycle callbacks.

B All modules must be loaded at app start, so lifecycle is unchanged.

C Modules replace the main activity lifecycle with their own independent lifecycles.

D Modularization disables lifecycle callbacks in feature modules.

💡 Hint

Think about dynamic feature modules and their loading behavior.

Dynamic modules can be loaded or unloaded during app runtime, so lifecycle events may be triggered when modules initialize or are removed.

❓ navigation

advanced

Navigation between modules

In a modularized Android app, what is the recommended way to navigate from a screen in one module to a screen in another module?

A Copy the target screen's code into the current module.

B Directly import the target module's classes and call them.

C Use a shared navigation interface or deep links to decouple modules.

D Use static variables to share navigation state between modules.

💡 Hint

Consider how to keep modules independent while allowing navigation.

Using interfaces or deep links allows modules to communicate without tight coupling, preserving modularity.

🔧 Debug

expert

Debugging module dependency errors

You get a runtime error: "ClassNotFoundException" for a class in a feature module. What is the most likely cause in a modularized Android app?

A The class name is misspelled in the feature module source code.

B The feature module was not included or loaded properly at runtime.

C The app's main module has too many dependencies declared.

D The AndroidManifest.xml is missing the INTERNET permission.

💡 Hint

Think about how modules are packaged and loaded in the app.

If a module is not included or loaded, classes inside it won't be found at runtime, causing ClassNotFoundException.