Google has now put a date on the point at which an unregistered Android app stops installing. It is September 30, 2026, and in this first phase it applies to users in Brazil, Indonesia, Singapore and Thailand, on certified devices running Android 7 or higher, installing from seven participating stores — Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps. A global rollout to all certified Android devices is scheduled for 2027.
That is a real change in how software reaches Android phones, and it deserves to be read accurately rather than dramatically. Two things are worth separating: what the deadline actually covers, and what the resulting "verified" status actually certifies.
What the deadline covers, precisely
A lot of the commentary has compressed this into "every Android developer must now send Google a government ID." The primary documentation says something narrower.
- The September date is store-scoped. Google's FAQ states that enforcement starting September 30 "is limited only to the specific stores mentioned," and that if users sideload an app directly, or install it from a store outside that list, "these new verification requirements won't apply to your app yet."
- There is a free tier that takes no ID. Limited distribution accounts opened to everyone in August for hobbyists, students and teachers. They cost nothing, they allow sharing with up to 20 devices that end users have explicitly authorized, and the guide says it plainly: "you don't need to provide a government ID." The $25 fee belongs to a Full Distribution account and is waived for this one.
- ADB is untouched. Installing over Android Debug Bridge needs no verification, and the advanced flow's waiting period does not apply to it.
- Most Play apps are already done. Google states that Play automatically registers 99% of apps, and that apps using Play App Signing are claimed automatically.
None of that makes the 2027 global phase a small thing, and the developers raising objections to it are not raising imaginary ones. But someone reading only headlines might conclude that the hobby project on their bench dies in eleven days, and that is not what the documents say.
What "verified" certifies — and what it does not
Here is the part worth sitting with. It is not a gotcha, because Google states it clearly itself, in the FAQ, while answering a question about NDAs:
"Verification is narrowly focused on the developer's identity to establish accountability. Android Developer Verification does not collect information about the app content or functionality."
Read that against the programme's stated purpose, which is equally explicit: identity verification "establishes accountability," making it harder for whoever shipped malware to turn around and ship the same thing again under a fresh anonymous identity. That is a genuine problem, and this is a reasonable lever against it.
But accountability is a claim about who. It is not a claim about what. Verification binds a legal identity to a signing key; it does not examine what the software does once it is running. Both of these remain entirely possible after September 30:
- A fully verified developer — ID submitted, fee paid, key registered — ships an app that uploads everything it records to a server you know nothing about.
- An unverified hobbyist ships an app that never opens a socket in its life.
The risk here is not that verification is bad. The risk is the heuristic users may quietly learn from it. Install friction is about to become visible: an unverified app shows a warning, and reaching one at all takes a deliberate one-time setup involving developer mode, a restart, and a one-day wait. It is very natural to start reading smooth as safe and friction as suspicious. As a privacy heuristic that is unreliable in both directions, because privacy is a question about behaviour and the badge is an answer about identity.
For camera apps, the gap is widest
A camera app is the case where the distance between those two questions matters most. You are handing an application a live view of a room in your home, plus storage, plus — usually — the network. Who wrote it is worth knowing. It is not the thing that determines whether tonight's recording stays on the device.
The useful part is that the behaviour question is testable by the person asking it, without trusting anybody's badge or anybody's marketing copy, ours included:
- Cut the network and see what survives. Put the phone in airplane mode, or take it off Wi-Fi, and try to record. Something storing locally keeps working. Something whose pipeline runs through a server will tell you, quickly.
- Read the permissions against the feature list. A recorder needs camera, storage, and network if it serves a stream on your LAN. Anything past that is a question you are entitled to ask out loud.
- Check whether it insists on an account. An account is the mechanism by which footage becomes associated with a person on somebody else's system. An app that never asks for one cannot do that by that route.
- Watch it at rest. Leave it recording nothing in particular for a day, then look at its data usage.
Those four tests work on any camera app on your phone. They are not a pitch. They are precisely the questions the verification programme says it does not answer.
Where we sit
Background Camera RemoteStream is distributed on Google Play, which puts it in the 99% that Google registers automatically. Nothing about September 30 changes how anyone installs it. That is worth stating plainly rather than leaving implied — and it is worth saying in the same breath that it proves nothing whatsoever about our privacy claims. It proves Google knows who we are.
What we would rather you do is run test one. The app is built to record to local storage on the device, and to work without an account; airplane mode is the fastest way to find out whether that description survives contact with your own phone. We would rather be checked than believed, and the four tests above are the ones we would want someone to run on us.
Verification answers a question Android genuinely needed answered: when something harmful ships, who shipped it. That work is real and it is happening on a published schedule. It is simply a different question from the one most people are actually asking when they ask whether an app is private — and only one of those two questions has a deadline attached.
Background Camera RemoteStream is free on Google Play. More at superfunicular.com.
Sources, all first-party:
Top comments (0)