Android Permission Model and Runtime Permissions
You'll learn: How Android controls what apps can access through permissions, and the critical difference between install-time and runtime permission models.
What Are Android Permissions?
Android permissions act like security checkpoints that apps must pass through to access sensitive device features. Think of them as a bouncer at a club—an app can't read your contacts, access your camera, or use your location without explicit permission granted through the Android system.
These permissions protect user privacy and system integrity by enforcing principle of least privilege at the application level.
Install-Time vs Runtime Permissions
Android uses two permission models:
Install-Time (Normal) Permissions are automatically granted when the app installs. These cover low-risk features like internet access or setting an alarm. The system trusts these won't harm users.
Runtime (Dangerous) Permissions require explicit user approval while the app is running. These protect sensitive data and capabilities: camera, microphone, location, contacts, SMS, storage, and phone state. Starting with Android 6.0 (API 23), apps must request these at runtime—not just list them in the manifest.
Permission Groups
Android organizes related permissions into permission groups (e.g., CALENDAR, CAMERA, LOCATION). When an app requests one permission from a group, the user's approval applies to that entire group. However, apps must still request each specific permission in code—grouping only affects the UI presentation.
Example: If you grant READ_CONTACTS, the system may also grant WRITE_CONTACTS without another prompt, since both belong to the CONTACTS group.
Security Implications
This model prevents malicious apps from silently harvesting user data. Even if an app declares permissions in AndroidManifest.xml, runtime checks ensure users maintain control. Apps must handle permission denial gracefully, and users can revoke permissions at any time through system settings.
Key Takeaway: Android's permission model enforces least privilege through a two-tier system—normal permissions granted at install, dangerous permissions requiring explicit runtime user consent, organized into groups for usability while maintaining granular control.