Why runtime permissions protect user privacy in Android Kotlin - Quick Recap

Recall & Review

beginner

What are runtime permissions in Android?

Runtime permissions are permissions that an app requests from the user while the app is running, not just at install time. This lets users decide if they want to allow access to sensitive data or features.

beginner

Why do runtime permissions improve user privacy?

They let users control when and how apps access sensitive information, like location or contacts, preventing apps from accessing data without user consent.

beginner

When does an Android app request runtime permissions?

An app requests runtime permissions only when it needs to use a feature that requires permission, such as accessing the camera or microphone, making the request relevant and timely.

beginner

What happens if a user denies a runtime permission?

The app cannot use the feature that requires that permission. The user can later change this decision in the device settings if they want to allow it.

intermediate

How do runtime permissions differ from install-time permissions?

Install-time permissions are granted when the app is installed, without asking again. Runtime permissions ask the user during app use, giving more control and transparency.

What is the main purpose of runtime permissions in Android?

A To let users control app access to sensitive data during app use

B To speed up app installation

C To allow apps to access all device features automatically

D To prevent apps from running in the background

Runtime permissions let users decide when apps can access sensitive features, protecting privacy.

When does an app request a runtime permission?

A Only when the app is installed

B When the app needs to use a feature requiring permission

C Every time the device is restarted

D Only when the user opens device settings

Apps ask for runtime permissions only when they need to use a feature that requires it.

What can a user do if they deny a runtime permission?

A Change the permission later in device settings

B Nothing, the decision is permanent

C Uninstall the app automatically

D Force the app to close

Users can always change permission decisions later in the device settings.

Which of these is NOT a benefit of runtime permissions?

A Improved user privacy

B User control over sensitive data

C Apps get all permissions by default

D Transparency about app access

Runtime permissions prevent apps from getting all permissions by default.

How do runtime permissions protect user privacy?

A By hiding app data from the user

B By automatically granting all permissions

C By blocking all app features

D By asking user consent before accessing sensitive features

Runtime permissions ask users for consent, protecting their privacy.

Explain how runtime permissions help protect user privacy in Android apps.

Think about when and why the app asks for permissions.

Describe the difference between install-time permissions and runtime permissions.

Consider when the user is asked to grant permissions.

Practice

1. Why do Android apps request runtime permissions instead of asking for all permissions at install time?

easy

A. To protect user privacy by asking only when the permission is needed

B. To make the app install faster

C. To reduce the app size

D. To avoid asking the user any questions

Solution

1. Step 1: Understand runtime permissions purpose

   Runtime permissions ask users only when a feature needs access, protecting privacy.

2. Step 2: Compare with install-time permissions

   Install-time permissions ask all at once, which can overwhelm users and reduce control.

3. Final Answer:

   To protect user privacy by asking only when the permission is needed -> Option A

4. Quick Check:

   Runtime permissions = protect privacy [OK]

Hint: Runtime permissions ask only when needed, protecting privacy [OK]

Common Mistakes:

• Thinking runtime permissions speed up installation
• Believing runtime permissions reduce app size
• Assuming runtime permissions avoid user prompts

2. Which Kotlin code snippet correctly checks if the app has permission to access the camera before requesting it?

easy

A. if (checkPermission(Manifest.permission.CAMERA)) { /* permission granted */ }

B. if (hasPermission(Manifest.permission.CAMERA)) { /* permission granted */ }

C. if (ContextCompat.checkSelfPermission(this, Manifest.permission.CAMERA) == PackageManager.PERMISSION_GRANTED) { /* permission granted */ }

D. if (requestPermission(Manifest.permission.CAMERA)) { /* permission granted */ }

Solution

1. Step 1: Identify correct permission check method

   ContextCompat.checkSelfPermission returns permission status in Android Kotlin.

2. Step 2: Verify correct comparison

   Compare result to PackageManager.PERMISSION_GRANTED to confirm permission granted.

3. Final Answer:

   if (ContextCompat.checkSelfPermission(this, Manifest.permission.CAMERA) == PackageManager.PERMISSION_GRANTED) { /* permission granted */ } -> Option C

4. Quick Check:

   Use ContextCompat.checkSelfPermission == PERMISSION_GRANTED [OK]

Hint: Use ContextCompat.checkSelfPermission with PERMISSION_GRANTED check [OK]

Common Mistakes:

• Using non-existent methods like checkPermission or hasPermission
• Calling requestPermission instead of checking permission
• Not comparing to PERMISSION_GRANTED constant

3. Given this Kotlin code snippet, what will be the output if the user denies the permission request?

if (ContextCompat.checkSelfPermission(this, Manifest.permission.LOCATION) != PackageManager.PERMISSION_GRANTED) {
  ActivityCompat.requestPermissions(this, arrayOf(Manifest.permission.LOCATION), 100)
} else {
  println("Permission already granted")
}

medium

A. Nothing printed immediately; permission request dialog shown

B. Permission already granted

C. App crashes due to missing permission

D. Permission denied message printed

Solution

1. Step 1: Analyze permission check condition

   Permission is not granted, so requestPermissions is called to ask user.

2. Step 2: Understand immediate output

   requestPermissions shows dialog asynchronously; no immediate print happens.

3. Final Answer:

   Nothing printed immediately; permission request dialog shown -> Option A

4. Quick Check:

   Permission request dialog shows, no immediate print [OK]

Hint: requestPermissions shows dialog, no immediate output printed [OK]

Common Mistakes:

• Assuming println runs before user responds
• Expecting crash without handling permission denial
• Thinking denial message prints automatically

4. What is wrong with this Kotlin code snippet for requesting permission?

ActivityCompat.requestPermissions(this, arrayOf(Manifest.permission.READ_CONTACTS), 1)
if (ContextCompat.checkSelfPermission(this, Manifest.permission.READ_CONTACTS) == PackageManager.PERMISSION_GRANTED) {
  println("Permission granted")
}

medium

A. println statement should be outside the if block

B. Permission check is done immediately after request, before user responds

C. Manifest.permission.READ_CONTACTS is not a valid permission

D. requestPermissions method is called with wrong parameters

Solution

1. Step 1: Understand requestPermissions behavior

   requestPermissions shows dialog asynchronously; user response is not immediate.

2. Step 2: Identify timing of permission check

   Checking permission immediately after request will not reflect user's choice yet.

3. Final Answer:

   Permission check is done immediately after request, before user responds -> Option B

4. Quick Check:

   Check permission after user response, not immediately [OK]

Hint: Check permission after user responds, not right after request [OK]

Common Mistakes:

• Checking permission immediately after requestPermissions call
• Assuming requestPermissions blocks until user answers
• Misusing permission constants

5. An app needs to access the user's location only when showing nearby stores. How should it use runtime permissions to protect user privacy best?

hard

A. Request all permissions including location at install time

B. Request location permission immediately when the app starts

C. Never request location permission and guess location from IP

D. Request location permission only when the user tries to view nearby stores

Solution

1. Step 1: Identify when location is needed

   Location is needed only when user views nearby stores, not before.

2. Step 2: Apply runtime permission best practice

   Request permission only at the moment feature is used to respect privacy and reduce prompts.

3. Final Answer:

   Request location permission only when the user tries to view nearby stores -> Option D

4. Quick Check:

   Request permission when feature used, protect privacy [OK]

Hint: Ask permission only when feature needs it, not before [OK]

Common Mistakes:

• Requesting permission too early at app start
• Requesting all permissions upfront at install
• Avoiding permission request and guessing location