Why runtime permissions protect user privacy in Android Kotlin - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do Android apps request permissions at runtime?

Which reason best explains why Android apps ask for permissions while the app is running instead of only at install time?

A To let users decide when to allow access to sensitive data or features, improving privacy control.

B To make the app load faster by delaying permission checks until needed.

C To reduce the app size by downloading permissions separately.

D Because Android does not support permissions declared in the app manifest anymore.

💡 Hint

Think about how users can control what data apps can access.

Runtime permissions let users approve or deny access to sensitive features like camera or location only when the app needs them, giving users more control and protecting their privacy.

❓ ui_behavior

intermediate

What happens if a user denies a runtime permission?

When an Android app requests a runtime permission and the user denies it, what is the typical app behavior?

A The app automatically requests the permission again until the user accepts.

B The app crashes immediately because it cannot access the denied feature.

C The app continues without the feature that needs the permission, possibly showing a message explaining the limitation.

D The app disables all functionality and closes.

💡 Hint

Consider how apps handle missing permissions gracefully.

Apps should handle denied permissions by disabling or hiding features that require them and informing the user, instead of crashing or forcing permission acceptance.

❓ lifecycle

advanced

When should an app request runtime permissions?

At which point in the app lifecycle is it best practice to request a runtime permission?

A Immediately when the app starts, before showing any UI.

B Right before the app needs to use the feature that requires the permission.

C Only after the user has used the app for more than 5 minutes.

D After the app has crashed once due to missing permission.

💡 Hint

Think about when the user expects to grant access.

Requesting permissions just before using the related feature helps users understand why the permission is needed and improves trust.

🔧 Debug

advanced

Identify the cause of a permission denial crash

This Kotlin code snippet crashes when accessing the camera. What is the cause?

Android Kotlin

if (checkSelfPermission(Manifest.permission.CAMERA) == PackageManager.PERMISSION_GRANTED) {
  startCamera()
} else {
  startCamera()
}

A The app calls startCamera() even when permission is not granted, causing a crash.

B The permission check uses the wrong constant for CAMERA permission.

C The app should request permission inside the else block before starting the camera.

D The app needs to check permission in onCreate(), not here.

💡 Hint

Look at what happens when permission is denied.

The code calls startCamera() regardless of permission status, so if permission is denied, the app tries to access the camera and crashes.

❓ navigation

expert

How to handle permission denial with 'Don't ask again' selected?

If a user denies a runtime permission and selects 'Don't ask again', what is the best way for the app to let the user enable the permission later?

A Keep requesting the permission every time the app starts until the user accepts.

B Disable the app permanently without informing the user.

C Restart the app automatically to reset permission requests.

D Show a dialog explaining the permission is needed and provide a button to open the app settings screen.

💡 Hint

Think about how users can manually change permissions after blocking requests.

When 'Don't ask again' is selected, the app cannot request permission again programmatically. The user must go to app settings to enable it.