Runtime Permissions Basics

Relax. We'll talk through this in plain words — no textbook voice.

What you'll walk away with

Understand Runtime Permissions Basics without the intimidation
Get comfortable running Android Studio/Compose code yourself
Apply this concept in a real project right away

Let's think about it this way for a second

Just declaring a permission in AndroidManifest.xml isn't enough — for sensitive permissions (Camera, Location, Notification), you also have to show a dialog and ask the user directly at app runtime (Android 6.0+). The user can pick 'Allow' or 'Deny' — if they pick 'Deny', you need to handle the feature gracefully (so the app doesn't crash).

Let's connect this to a real scenario

For an app with a camera feature, add `<uses-permission android:name="android.permission.CAMERA" />` to `AndroidManifest.xml`, then use `rememberLauncherForActivityResult` in Compose to trigger the runtime permission dialog — you can only enable the camera feature once the user taps 'Allow'; if they pick 'Deny', show an explanation message and keep the feature disabled.

Declaring a permission in AndroidManifest.xml isn't enough — sensitive permissions need a runtime request
The user can pick 'Allow'/'Deny' — handle 'Deny' gracefully
rememberLauncherForActivityResult = triggers the permission dialog in Compose

Let's walk through it together

kotlin

@Composable
fun CameraScreen() {
    var hasPermission by remember { mutableStateOf(false) }
    val launcher = rememberLauncherForActivityResult(
        ActivityResultContracts.RequestPermission()
    ) { granted -> hasPermission = granted }

    Button(onClick = { launcher.launch(Manifest.permission.CAMERA) }) {
        Text("Request Camera Permission")
    }

    if (hasPermission) {
        Text("Camera ready!")
    } else {
        Text("Camera permission not granted")
    }
}

You should see

Clicking the button should bring up the system permission dialog, and picking 'Allow' should show 'Camera ready!'

5-minute try-it

Run `CameraScreen` and click the permission button — try both 'Allow' and 'Deny' and see how the UI changes each time.

A quick word of caution

If the user keeps picking 'Deny' (or taps 'Don't ask again'), Android stops showing the permission dialog altogether — since they'd have to go into Settings manually at that point, your app should handle this scenario too.

Easy traps

Calling a feature (like the camera API) directly without checking whether the permission was granted or denied — this can crash with a SecurityException
Silently disabling the feature with no explanation when the user picks 'Deny' — this can leave the user confused

Now try it yourself

Run `CameraScreen` and click the permission button — try both 'Allow' and 'Deny' and see how the UI changes each time.

You'll know it worked when: Clicking the button should bring up the system permission dialog, and picking 'Allow' should show 'Camera ready!'