Android 17 beta 3, released to the developer channel on Tuesday, converts INTERNET from a normal permission into a runtime permission. Since Android 1.0, an app that declared internet access in its manifest received it at install time with no user involvement, which is why a flashlight app could phone home and nobody would know. Beta 3 prompts on first network use, offers allow, allow while using the app, and deny, and surfaces per-app data destinations in Settings. Google frames it as the last major gap in the runtime permission model that started in Android 6.0. Developers, particularly ad-supported ones, are describing it in less measured terms.
How the prompt behaves
The permission triggers on the first outbound socket, not at launch, so an app that works offline never prompts. Denying it does not crash a well-written app, since the platform returns the same errors an offline device produces, though Google's compatibility testing found roughly 18 percent of the top 500 apps crash or hang when network calls fail immediately. Those apps will need work, which is the entire purpose of a beta program and also the source of most of the developer anger.
Google carved out exceptions that matter. Play Services, system components, and any app the user has set as a default handler for calls, messaging, or browsing get network access without a prompt. Apps installed by an enterprise mobility manager can have the permission pre-granted by policy. And critically, the permission does not apply to apps targeting an API level below 37, which means the ecosystem converts gradually as Play Store target requirements ratchet forward, likely completing in 2028.
The advertising industry's problem
Mobile advertising depends on ad requests reaching an exchange from the device. If a meaningful share of users deny network access to a free game, that game's revenue drops to zero while its costs continue. The Interactive Advertising Bureau's technology lab published a statement within hours calling the change disproportionate and asking Google to exempt advertising traffic, which is not a request any privacy regulator would look at kindly.
Apple's App Tracking Transparency provides the base rate everyone is extrapolating from. Roughly 75 percent of iOS users declined tracking when prompted, and mobile ad revenue on iOS fell sharply before recovering through modeling and first-party data. A network permission is broader and more consequential, since declining it breaks the app rather than merely reducing targeting. Analysts at Sensor Tower estimate deny rates will be far lower for that reason, perhaps 15 to 25 percent, concentrated in apps users perceive as not needing connectivity.
The story is rarely the launch. It is what breaks, what ships, and who owns the mess at 2 a.m.
What users see in Settings
Beyond the prompt, Android 17 adds a network activity page per app listing the domains contacted over the past seven days with byte counts. This is the feature that will generate screenshots. A calculator app contacting eleven analytics domains is a story that writes itself, and consumer technology press will run those stories for months. Google built the collection at the DNS and connection layer, so it works regardless of what the app does internally, and it cannot be evaded by using raw IP addresses since those appear too.
There are limits. Traffic through a VPN or through Play Services shows as a single entry, which conceals the most common data pipeline in the ecosystem. Google's own apps appear in the list, and the beta's rendering of Gmail and YouTube domain counts is not flattering, though the company has not asked for an exemption. Privacy researchers at the Electronic Frontier Foundation called the feature genuinely useful and noted the Play Services aggregation as the obvious gap to close in a future release.
The regulatory context
The timing is not accidental. The European Data Protection Board has an open inquiry into mobile operating system data flows, and the German Federal Cartel Office has been pressing Google on Android data practices since 2023. Shipping a user-facing control that limits app data collection is a useful thing to point at in those conversations, particularly one that constrains third-party developers more than it constrains Google.
That asymmetry is exactly what competition authorities watch for. Play Services being exempt from a permission that binds every competitor's SDK is the kind of structural advantage the Digital Markets Act was written to address. Two European developer associations have already indicated they will raise it with the Commission. Google's defense will be that Play Services is a system component rather than an app, an argument the company has made before with mixed success.
What developers should do now
Test with the permission denied. That is the entire short-term action item, and it will surface bugs that have been latent since your app was written, because almost nobody handles a network stack that fails instantly and consistently. The failure should be a clear message explaining what the app cannot do rather than a spinner that never resolves, which is what most apps currently produce.
The medium-term work is reducing the number of things that require network at launch. Apps that fetch configuration, check for updates, and initialize four analytics SDKs before rendering a first screen will prompt immediately and look greedy. Apps that render local content first and reach the network only when the user does something that obviously needs it will prompt at a moment the user understands. That distinction will separate the apps that keep their permission grants from the apps that do not.
Skarvonix will keep following this beat with reporting grounded in how systems behave outside the launch keynote.
- Privacy
