Skip this first page if you don’t care about subreddit drama.

Skip to page 4 if you just want actionable steps.

Ok, so this info was originally a post on reddit. Unfortunately, the post I was sharing around was removed by "reddit's filters". I have no idea why this happened, especially why it happened right as that post was gaining more traction than it ever has before. That means right as loads of people were being informed of ways to fight developer verification, reddit and their mysterious “filters” decided to remove my post. Thank you reddit for going after the real troublemakers on your platform. You are truly keeping this community safe. A special thank you as well to the moderators of r/Android for consistently removing and not approving any post I make containing this information, and thus preventing this from being available on a subreddit with significantly more active users who may be driven to action, because obviously the users of that subreddit wouldn’t find any of this information useful or wish to know about it. (Sidenote: This is me just venting my frustration. This is not a call to action to harass any of the mods on any subreddit. I really shouldn’t have to say this but a mod from a specific subreddit permanently banned me and accused me of intentionally sending a harassment wave to the mods, among other things. I am not, and if you do harass the mods then you are worse than any action they could have potentially taken against me. It’s not that big of a deal, and I’m just taking the piss. I’m also not trying to imply any “conspiracy” between reddit and google for removing my first post. Again, I didn’t think I had to specify this, but that same mod mentioned this, so here we go)

My first thought was to move this to a Google doc, but that felt hypocritical for info that is very anti-Google. I feel I should be boycotting their products as much as possible until they roll back developer verification. I thus tried to find an alternative, and u/Melodic-Ice-9247 recommended cryptpad. Unfortunately, on every subreddit I posted on people thought the link was “sketchy”, and the post was even banned by the mods of r/androiddev, people who should really know better as it only took me like 30 seconds of research to understand what this “mysterious” service was and if it was safe or not. Thank you r/androiddev mods. You and your sub are truly doing your best to help fight against Google’s enshitification of their platforms. (Sidenote: Read above sidenote)

So, begrudgingly, I will be hosting this info on Google docs. If anyone has a problem with that, please suggest another alternative. Also, please comment about things you would like to add, or any improvements I can make. I’d like to give a special thanks to u/Uberunix, whose original post for developers specifically is what I based this entire document off of and what inspired me to collect all of these actionable steps.

Also, skip to pg. 4 if you just want to see actionable steps rather than summarizations of the issue.

—------------------------------------------------------------------------------------------------------------------------

I've been posting a lot about things that can be done about the new Android developer verification system. I've decided to combine everything I know about into one post that can be easily shared around.

Some of this I found myself, but others I got from this post by user u/Uberunix. When I quote directly from their post, I use quotation marks.

Please share this to as many subreddits as possible, and please link these resources anywhere you see this situation being discussed.

The Situation:

Articles:

Videos:

  • Techlore
  • LTT
  • Lewis Rossman
  • Mental Outlaw
  • SAMTIME

Reason to believe we can force Google's hand:

Microsoft recently pulled out of a mass surveillance program done in partnership with the Israeli government. The specific reason this occurred was never stated, but some argue it was in response to mass protests, Microsoft employees speaking up within the company, and news organizations covering the controversy. While it may seem we are powerless against large corporations, this development suggests we can make them budge on things like we saw here.

Why this is an issue:

Resources:

Why this is bad for Google

  • Quote from 4-min. mark: "One thing I’m really glad was brought up is how coincidental the timing of this policy change is.There has been an ongoing lawsuit between Epic Games and Google regarding third-party app stores. The outcome of that case allows third-party app stores on Android, lets other stores redistribute Play Store content, and reduces Google’s control over app store distribution.The timing is suspicious because Google is at risk of losing many developers from the Play Store. They could lose valuable insights, as well as apps that developers may now choose to build for other platforms instead.This new policy still requires developers—even those not publishing on the Play Store—to register with Google and get Google’s approval. If Google disapproves of an app, they can block it, even if it’s distributed outside the Play Store.That’s highly ironic. Google is being forced to allow people to move away from the Play Store, supposedly reducing its control. But at the same time, they’re introducing a policy that gives them more control than ever before.It seems clear that Google is doing this to maintain control over the ecosystem. We’re seeing Android shift more and more toward a closed, Apple-like model."

"What about ADB"?

  • Regardless of any workarounds, Google should not have this much control over what can run on your device. Period
  • Average people who might otherwise want to download apps not available on the playstore will not be willing to use ADB. While it is simple to use, if you ask the average phone user to use command lines to download an app, you’ve already lost them. Even if the vast majority of average users do not “sideload”, it should still be an option for them and it should still be easy to do so. You should not have to find workarounds to install the apps you want on the phone you paid hundreds of dollars for
  • While ADB may still be a good way to bypass developer verification and keep

Things We Can Do:

For Android Developers Specifically:

  • Google feedback survey on developer verification system:
  • Sign up for early access to program:
  • An invitation to an exclusive community discussion forum.
  • The chance to provide feedback and help us shape the experience."
  • Comment on Issue Tracker request or make your own:
  • Add FreeDroidWarn to your app
  • https://github.com/woheller69/FreeDroidWarn
  • Notifies users of your app of the Google developer verification thing, and the fact that you as a developer are not willing to give your information to Google
  • Will help spread awareness of the issue

For Everyone:

  • Send feedback on EU Digital Fairness Act:
  • Change.org petition (won't do much but it's worth a shot):
  • Sign petition for UK Parliament (if you live in UK)
  • Petition for UK Parliament
  • Sent directly to parliament and is a part of UK political system, so has much better chance of actually being acted on compared to other online petitions
  • Contact DOJ:
  • DOJ Anonymous Contact Form
  • "Developer Verification is easily qualified as an attempt to maintain Google's monopolistic control of App distribution on their platform. Despite an emergency stay, the court has found Google guilty. Let the feds know they aren't listening. This form can be anonymously submitted to encourage the DOJ to Investigate" u/Uberunix
  • Contact the CMA (UK)
  • Contact euro consumers and request they send letters and take action against Google and their behavior
  • Recently had success with holding Microsoft accountable in regards to Windows 10
  • Contact Electronic Frontier Foundation and request them to take action against Google
  • Contact Epic Games and request them to take legal action against Google
  • Contact the FCC:
  • FCC Contact Form
  • "The FCC is jointly responsible with the DOJ in pursuing antitrust violations." u/Uberunix
  • Contact Procon & Senacon (Brazil)
  • Send feedback via Gmail:
  • Email EU Director General for Compensation (deals with anti-trust cases):
  • comp-greffe-antitrust@ec.europa.eu
  • Contact Sameer Samat, head of Android, directly (please be nice and don't send death threats):
  • "Vote with your feet"
  • Contact large Youtubers and get them talking about this more (examples below)
  • Bug Google's Social Media
  • Reply under every post made by:

Ways to Potentially Bypass Verification System:

  • Shizuku
  • ADB
  • Install custom rom that doesn't have Google Play Services
  • GraphineOS
  • iodeOS
  • CalyxOS
  • Open Harmony?
  • Remove Google Play Services from your phone and replace them with MicroG

Example Templates for Developers (All of this is taken from u/Uberunix)

Example Feedback to Google:

I understand and appreciate the stated goal of elevating security for all Android users. A safe ecosystem benefits everyone. However, I have serious concerns that the implementation of this policy, specifically the requirement for mandatory government ID verification for _all_ developers, will have a profoundly negative impact on the Android platform.

My primary concerns are as follows:

  1. It Undermines the Openness of Android: The greatest strength of Android has always been its flexibility and openness, allowing developers the freedom to distribute their work outside of a single, centrally-controlled marketplace. This policy fundamentally changes that dynamic by appointing Google as the mandatory registrar for all development on the platform. True platform openness means not having to seek permission from the platform owner to distribute software directly to users.

  1. It Creates Barriers for Legitimate Developers: The requirement of government identification will disproportionately harm the vibrant community of independent, open-source, and privacy-conscious developers who are crucial to the health of the ecosystem. Many legitimate developers value their anonymity for valid reasons and will be unable or unwilling to comply. This will stifle innovation and ultimately reduce the diversity of applications available to users.

  2. It Erodes Developer Trust: Many developers are already wary of automated enforcement systems that have, at times, incorrectly flagged or banned established developers from the Play Store with little recourse. Granting Google this new layer of universal oversight outside the Play Store raises concerns that these issues could become more widespread, making the platform a riskier environment for developers to invest their time and resources in.

While your announcement states, "Developers will have the same freedom to distribute their apps directly to users," this new requirement feels like a direct contradiction to that sentiment. Freedom to distribute is not compatible with a mandate to first register and identify oneself with a single corporate entity.

I believe it is possible to enhance security without compromising the core principles that have made Android successful. I strongly urge you to reconsider this policy, particularly its application to developers who operate outside of the Google Play Store.

Thank you for the opportunity to provide feedback. I am passionate about the Android platform and hope to see it continue to thrive as a truly open ecosystem.

 

Example Report to DOJ:

Subject: Report of Anticompetitive Behavior by Google LLC Regarding Android App Distribution

To the Antitrust Division of the Department of Justice:

I am writing to report what I believe to be a clear and deliberate attempt by Google LLC to circumvent the recent federal court ruling in _Epic v. Google_ and unlawfully maintain its monopoly over the Android app distribution market.

Background

Google recently lost a significant antitrust lawsuit in the District Court of Northern California, where a jury found that the company operates an illegal monopoly with its Google Play store and billing services. In what appears to be a direct response to this ruling, Google has announced a new platform policy called "Developer Verification," scheduled to roll out next month.

The Anticompetitive Action

Google presents "Developer Verification" as a security measure. In reality, it is a policy that extends Google's control far beyond its own marketplace. This new rule will require **all software developers**—even those who distribute their applications independently or through alternative app stores—to register with Google and submit personal information, including government-issued identification.

If a developer does not comply, Google will restrict users from installing their software on any certified Android device.

Why This Violates Antitrust Law

This policy is a thinly veiled attempt to solidify Google's monopoly and nullify the court's decision for the following reasons:

  1. Unlawful Extension of Market Power: Google is leveraging its monopoly in the mobile operating system market (Android) to control the separate market of app distribution. By forcing all developers to register with them, regardless of whether they use the Google Play Store, Google is effectively making itself the mandatory gatekeeper for all software on its platform. This action directly contradicts the spirit of the _Epic v. Google_ ruling, which found Google's existing control to be illegal.
  2. Stifling Competition and Innovation: The policy creates significant barriers for independent developers. Many developers value their privacy or choose to develop and distribute their work anonymously for legitimate reasons. This requirement will force them off the platform, reducing consumer choice and harming the open and competitive ecosystem that Android was intended to foster. As the provided text notes, demanding privacy is not the same as engaging in illicit activity.
  3. Pretextual Justification: Google's claim that this is for user security is not credible. Android already contains multiple, explicit safeguards and warnings that a user must bypass to install applications from outside the official Play Store ("sideloading"). The true motive is not security but control—a way to claw back the monopolistic power the courts have deemed illegal.

This "Developer Verification" program is a direct assault on the principles of an open platform. It is an abuse of Google's dominant position to police all content and distribution, even outside its own store, thereby ensuring its continued monopoly.

I urge the Department of Justice to investigate this new policy as an anticompetitive practice and a bad-faith effort to defy a federal court's judgment. Thank you for your time and consideration.

 

 

In summary:

"Like it or not, Google provides us with the nearest we have to an ideal mobile computing environment. Especially compared to our only alternative in Apple, it's actually mind-boggling what we can accomplish with the freedom to independently configure and develop on the devices we carry with us every day. The importance of this shouldn't be understated.

“For all its flaws, without Android, our best options trail in the dust. Despite the community's best efforts, the financial thrust needed to give an alternative platform the staying power to come into maturity doesn't exist right now, and probably won't any time soon. That's why we **must** take care to protect what we have when it's threatened. And today Google itself is doing the threatening.

“If you aren't already aware, Google announced new restrictions to the Android platform that begin rolling out next month.

“According to Google themselves it's 'a new layer of security for certified Android devices' called 'Developer Verification.' Developer Verification is, in reality, a euphemism for mandatory self-doxxing.

“Let's be clear, 'Developer Verification' has existed in some form for a time now. Self-identification is required to submit your work to Google's moderated marketplaces. This is at it should be. In order to distribute in a controlled storefront, the expectation of transparency is far from unreasonable. What is unreasonable is Google's attempt to extend their control outside their marketplace so that they can police anyone distributing software from any source whatsoever.

“Moving forward, Google proposes to restrict the installation of any software from any marketplace or developer that has not been registered with Google by, among other things, submitting your government identification. The change is presented as an even-handed attempt to protect all users from the potential harms of malware while preserving the system's openness.

“'Developers will have the same freedom to distribute their apps directly to users through sideloading or to use any app store they prefer. We believe this is how an open system should work—by preserving choice while enhancing security for everyone. Android continues to show that with the right design and security principles, open and secure can go hand in hand.'

“It's reasonable to assume user-safety is the farthest thing from their concern. Especially when you consider the barriers Android puts in place to prevent uninformed users from accidentally installing software outside the Playstore. What is much more likely is that Google is attempting to claw back what control they can after being dealt a decisive blow in the District Court of Northern California.

“'Developer Verification' appears to be a disguise for an attempt to completely violate the spirit of this ruling. And it's problematic for a number of reasons. To name a few:

  1. Google shouldn't be allowed to moderate content distributed outside their marketplace. It's as absurd as claiming that because you bought a Telecaster, Fender should know every song you play to make sure none of them affronts anyone who hears.
  2. The potential for mismanagement, which could disproportionately harm independent developers. Quoting user Sominemo on 9-5 Google, 'We've already seen how Google's automated systems can randomly ban established developers from Google Play with little to no feedback. A system like this, which grants Google even more oversight, could easily make this problem worse.'
  3. It stifles the health of the platform. Demanding privacy does not equal illicit activity. Many developers who value anonymity will be disallowed from the platform, and users will suffer.
  4. What happens next? The 'don't be evil' days are far behind us. It's naive to expect that Google's desire for control ends here. Even if you don't distribute apps outside the Playstore, ask yourself what comes next once this system is put in place with no argument from the users. It will affect you too." u/Uberunix