Why architecture scales codebases in Android Kotlin - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use architecture in Android apps?

Which of the following best explains why using architecture patterns helps scale Android codebases?

A Architecture separates concerns, making code easier to maintain and extend as the app grows.

B Architecture forces all code into one file, reducing complexity.

C Architecture removes the need for testing by making code perfect.

D Architecture makes the app run faster by skipping UI updates.

💡 Hint

Think about how organizing code helps when many developers work on the same app.

Good architecture splits code into parts with clear roles. This makes it easier to add features and fix bugs without breaking other parts.

❓ ui_behavior

intermediate

Effect of architecture on UI updates

In an Android app using MVVM architecture, what happens when LiveData changes in the ViewModel?

A The UI automatically updates because it observes LiveData changes.

B The UI must be manually refreshed by calling invalidate() every time.

C The app crashes because LiveData cannot be observed.

D Nothing happens because ViewModel does not communicate with UI.

💡 Hint

Think about how LiveData helps keep UI and data in sync.

LiveData is observable data holder. When data changes, UI components observing it update automatically, reducing boilerplate and bugs.

❓ lifecycle

advanced

ViewModel lifecycle advantage

What is a key advantage of using ViewModel in Android architecture regarding lifecycle?

A ViewModel replaces Activities and Fragments completely.

B ViewModel is destroyed immediately when the app goes to background.

C ViewModel automatically restarts the app after crashes.

D ViewModel survives configuration changes like screen rotations, preserving UI data.

💡 Hint

Consider what happens to UI data when you rotate the device.

ViewModel objects are tied to UI controller lifecycle but survive configuration changes, so data is not lost and UI state is preserved.

❓ navigation

advanced

Navigation component role in scaling apps

How does using Android Navigation Component help scale large apps?

A It automatically generates UI layouts without coding.

B It forces all screens to be in one Activity, reducing modularity.

C It centralizes navigation logic, making it easier to manage complex screen flows.

D It disables back button to prevent navigation errors.

💡 Hint

Think about how managing many screens can get complicated without a system.

Navigation Component provides a single place to define all app navigation paths, reducing bugs and making it easier to add or change screens.

🔧 Debug

expert

Identifying architecture-related bug

Given this Kotlin code snippet in an Android app using MVVM: val data = MutableLiveData() fun loadData() { data.value = fetchDataFromNetwork() } fun fetchDataFromNetwork(): String { Thread.sleep(5000) // simulate network delay return "Hello" } What problem will this code cause when loadData() is called from the UI thread?

A The LiveData will never update because fetchDataFromNetwork returns empty string.

B The UI will freeze for 5 seconds because network call blocks the main thread.

C The app will run smoothly because Thread.sleep is asynchronous.

D The app will crash with NullPointerException because data is null.

💡 Hint

Consider what happens when you block the main thread in Android.

Calling Thread.sleep on the main thread freezes UI, causing poor user experience. Network calls must run on background threads.