Why is Google Forcing Android Developer ID Verification?
As I’m sure you’re all well aware, a new policy from Google will soon require developers to verify their identity before their applications can be installed on Android devices. Google is citing security as the primary motivation for this change, stating that it will help to prevent scams and malware. Despite Google's stated goals, many have speculate there are other reasons for the policy. We're going to dive into the details and see what some of those other reasons are and which ones hold up.
Blocking the ReVanced Apps
One significant concern circulating among users is that Google's new verification policy is a tactic to suppress patched applications, such as YouTube ReVanced, which enable ad blocking and other enhanced features. This theory gains initial traction when considering Google's past efforts to curb ad blockers on YouTube for desktop browsers. However, the argument loses some steam for me when I consider that beyond YouTube Revanced, Google has no other dog in that fight. Why would they care if you mod Instagram or Twitter?
Keep in mind that in the past Google did take action against the original YouTube Vanced, issuing a cease and desist because it involved the direct modification and distribution of Google's proprietary YouTube APK. In contrast, the successor, YouTube ReVanced, has operated without any impedance for years. This is likely because ReVanced operates by allowing users to patch the APK themselves, rather than distributing a pre-modified version. Google's inaction against ReVanced suggests a distinction in their enforcement strategy. They didn’t care that they were modding YouTube. They cared that they were distributing a YouTube app that was modded.
Ask yourself this: If they wanted to kill YouTube ReVanced, why haven’t they done.. anything to stop it like they did with Vanced? If they killed Vanced because it blocked ads, why have they done nothing to ReVanced?
If Google's recent aggression toward desktop ad blockers still makes you consider shutting down YouTube ReVanced as a possible primary goal, it is important to remember the key distinction. On the desktop, ad blockers directly impact Google's revenue. With Android, however, the vast majority of apps developers would not want to stand behind are not cutting into Google's bottom line. The gray area apps like emulators or piracy apps do not directly impact Google financially. This suggests that Google's motivation for the new policy might not be driven by a desire to protect its own revenue streams, but rather by another agenda.
Blocking Illegal and Grey Apps
One of the most immediate casualties of this new policy could be the emulation community. The developers of emulators for systems like the Nintendo Switch or 3DS often operate in a legal gray area and many choose to remain anonymous to avoid legal action from console manufacturers. Nintendo is well-known for its aggressive legal stance against emulators, as seen in its lawsuits against developers of the Yuzu and Citra emulators. These developers are highly unlikely to want to hand over their personal information to Google, knowing it could be subpoenaed by companies like Nintendo.
This policy could effectively kill off many of these projects. However, this is where this theory gets a bit murky. If Google’s goal was simply to stop emulation, why wouldn't they start with a simple Play Store ban of emulators? There are plenty of emulators available there right now and that means those developers are giving Google their ID already. A blanket ban would be a much more direct approach than this new verification process which won’t impact the emulators already in the store in any way. For apps that are straight-up piracy tools, there's no question. It's difficult to imagine any developer of a piracy app wanting to tie their government ID to their work. This policy gives Google a direct avenue to shut down those apps if they receive a legal request.
Quality Control
Another perspective is that Google's new policy is a form of quality control, designed to ensure that all apps available on Android meet a higher standard. The thinking goes that by requiring developers to be verified, Google can hold them accountable for the quality of their applications, leading to a more stable and reliable user experience. This would benefit everyone in the long run.
However, a closer look at the details reveals this might not be the case. Google has explicitly stated that the new policy is focused solely on stopping malicious software. You could always assume they’re lying, but that opens the door to pretty much anything being possible.
Control
A frequently voiced opinion is that Google's new policy is a clear move to gain more control over what users can install on their devices. While it is obviously true that Google is now exerting greater control, these comments rarely ever elaborate on the underlying motivation. Why would Google want this control? Control for the sake of control? When we’re talking about corporations, you always need to think about how things will impact the bottom line. To me, the answer goes beyond a simple desire for power. This policy, like it or not, is part of a broader shift to make Android a more locked-down and integrated ecosystem, similar to Apple's iOS.
To Compete With Apple
This leads to the most compelling theory for me: Google is doing this to compete with Apple. If you asked the average person which phone operating system is more susceptible to viruses, they would almost certainly say Android. Apple has cultivated a perception of being a more secure and controlled environment, and its "walled garden" approach is a major selling point for many consumers.
This new policy allows Google to lean into that strategy. It enables Google to say to the public, "Android is just as secure as iOS." I think Google would happily alienate the users who are upset about this change in order to grab more iOS users. It’s a numbers game. There are way more iPhone users to pull in than there are people who would literally leave Android because they can’t install an app for which the developer refuses to be identified. If we’re being honest, the apps we’re talking about tend to be apps people are using to avoid paying for things. I’m not sure Google cares if they leave..
And to the point I keep seeing made that this will in some way anger Android developers. I have to ask, which developers are we talking about here? You already have to verify to be in the Play Store. So we're talking about developers who have been anonymously distributing their apps? Are we sure Google cares about what they do or where they go? And where else would they go to distribute anonymously? If they want to distribute apps made for phones, there are only two games in town and both will be asking for their ID before the app can be installed.
Explanations, Not Endorsements
I want to make something very clear. None of this is to say that I endorse what Google is doing. Personally, I thin that when a user tries to install an unverified app, they should see a clear warning. “This app was not made by a verified developer and could be dangerous to install or use. By installing anyways, you must acknowledge the risk and take responsibility for what happens.” If grandma gets her bank account hacked after that, it’s on her.