Google may debut an à la carte app permission system for Android, similar to App Ops in Android 4.3, at Google I/O
Android could finally be getting back à la carte app permissions — As it stand right now, app permission control in Android is frustratingly monolithic.
Context & Ripple Effects
In 2015, Android's permission model was all-or-nothing: users accepted an app's full permission list at install or skipped it entirely, a frustration the article calls 'monolithic.' Google had briefly exposed finer control through App Ops-style toggles in Android 4.3 before pulling them, so this I/O report reads as a second attempt to ship what was quietly removed.
The report lands days before Google I/O alongside other Play Store changes, such as letting developers A/B test listing pages and price points, signaling a platform-controls refresh across both sides of the store.
First-order effects
- Users would gain per-permission toggles over installed apps instead of accept-all-or-reject decisions, directly changing how they evaluate apps that request broad access.
- Developers shipping on Play would need their apps to degrade gracefully when users deny individual permissions, since installs could no longer be gated on the full list.
Second-order effects
- Apple's iOS already ran a more granular runtime-permission model — the same dynamic that later pushed Google to adopt iOS-style 'Allow Once' temporary permissions in Android 11 — so parity pressure on Google comes from cross-platform expectations rather than a rival OS feature alone.
- Apps whose value depends on always-on access (background data, location) would see opt-in rates fall once permissions become optional, forcing redesigns around explicit consent.
Third-order effects
- The pattern holds across the corpus: granular controls kept expanding until Google added automatic resets of permissions for apps left unused, meaning the end state is not just user choice but permissions that expire by default without user action.
- If install-time bundles keep giving way to runtime, revocable, self-expiring grants, the permission system becomes an ongoing policy layer Google enforces across every Android version — a governance role rather than a one-time dialog.
The trend: Android's permission model has spent the decade moving from install-time all-or-nothing grants toward granular, temporary, and automatically revoked access, with each step narrowing what apps can assume by default.