Android Developer Verification

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>Consumer Rights Wiki</sitename>
    <dbname>wiki</dbname>
    <base>https://consumerrights.wiki/w/Main_Page</base>
    <generator>MediaWiki 1.44.0</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">Consumer Rights Wiki</namespace>
      <namespace key="5" case="first-letter">Consumer Rights Wiki talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
      <namespace key="106" case="first-letter">Form</namespace>
      <namespace key="107" case="first-letter">Form talk</namespace>
      <namespace key="828" case="first-letter">Module</namespace>
      <namespace key="829" case="first-letter">Module talk</namespace>
      <namespace key="3004" case="first-letter">Projects</namespace>
      <namespace key="3005" case="first-letter">Projects talk</namespace>
    </namespaces>
  </siteinfo>
  <page>
    <title>Android Developer Verification</title>
    <ns>0</ns>
    <id>5951</id>
    <revision>
      <id>22192</id>
      <timestamp>2025-08-25T20:36:28Z</timestamp>
      <contributor>
        <username>Pawke</username>
        <id>5514</id>
      </contributor>
      <comment>init</comment>
      <origin>22192</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="591" sha1="7godjknrlmhphsu45iposq2arimv3r8" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
{{Ph-I-Int}}
==Background==
{{Ph-I-B}}

==[Incident]==
{{Ph-I-I}}

===[Company]'s response===
{{Ph-I-ComR}}


==Lawsuit==
{{Ph-I-L}}


==Consumer response==
{{Ph-I-ConR}}


==References==
{{reflist}}

{{Ph-I-C}}</text>
      <sha1>7godjknrlmhphsu45iposq2arimv3r8</sha1>
    </revision>
    <revision>
      <id>22199</id>
      <parentid>22192</parentid>
      <timestamp>2025-08-25T21:28:20Z</timestamp>
      <contributor>
        <username>Pawke</username>
        <id>5514</id>
      </contributor>
      <comment>wip, start fleshing out the page</comment>
      <origin>22199</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2979" sha1="q0iszxnf8u8ar3y3p2m21l84w787492" xml:space="preserve">{{StubNotice}}

{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th 2025, Google has announced an upcoming application installation restriction on Google-certified Android devices, unless the developer is registered and verified through their Developer Verification program, which in some cases requires a legal identity document verification as well as a flat fee.

==Background==
On the Android mobile operating system, the user can, currently, freely install applications developed by anyone, with no kinds of penalty as to their origin, feature set or purpose. The only requirements is that the application follows the technical guidelines, that ensure that the application will be functional on the device, and is signed with any kind of certificate, which is required to maintain a chain of trust during application updates.

==Introduction of Developer Verification==
On August 25th 2025, Google has released&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer console {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; a roadmap of a new requirement for application installations called the Developer Verification, which will require developers to register on the Android Developer Console, if they want their applications to be installable after the roll out of this system. When registering, the developers are offered a choice&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; between "Limited" and "Full" distribution types. The "Limited" distribution type is considered by Google to be best for "students, hobbyists, and other personal use", and is free to register, unlike the "Full" distribution type, which is considered to be suited for "organizations and professional developers with wide distribution". The "Limited" type is stated to have a "capped number of apps and installs", unlike the "Full" type. It is currently unclear whether or not the "Limited" type requires any kind of identity verification, as opposed to "Full", which requires full identity verification, as stated by Google.

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>q0iszxnf8u8ar3y3p2m21l84w787492</sha1>
    </revision>
    <revision>
      <id>22253</id>
      <parentid>22199</parentid>
      <timestamp>2025-08-26T06:36:54Z</timestamp>
      <contributor>
        <username>AnotherConsumerRightsPerson</username>
        <id>4554</id>
      </contributor>
      <comment>Making URL status live - Wayback Machine takes a while to load</comment>
      <origin>22253</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3013" sha1="0j80df17h7o37apxvgydqu5k4hlvepf" xml:space="preserve">{{StubNotice}}

{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th 2025, Google has announced an upcoming application installation restriction on Google-certified Android devices, unless the developer is registered and verified through their Developer Verification program, which in some cases requires a legal identity document verification as well as a flat fee.

==Background==
On the Android mobile operating system, the user can, currently, freely install applications developed by anyone, with no kinds of penalty as to their origin, feature set or purpose. The only requirements is that the application follows the technical guidelines, that ensure that the application will be functional on the device, and is signed with any kind of certificate, which is required to maintain a chain of trust during application updates.

==Introduction of Developer Verification==
On August 25th 2025, Google has released&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer console {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; a roadmap of a new requirement for application installations called the Developer Verification, which will require developers to register on the Android Developer Console, if they want their applications to be installable after the roll out of this system. When registering, the developers are offered a choice&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; between "Limited" and "Full" distribution types. The "Limited" distribution type is considered by Google to be best for "students, hobbyists, and other personal use", and is free to register, unlike the "Full" distribution type, which is considered to be suited for "organizations and professional developers with wide distribution". The "Limited" type is stated to have a "capped number of apps and installs", unlike the "Full" type. It is currently unclear whether or not the "Limited" type requires any kind of identity verification, as opposed to "Full", which requires full identity verification, as stated by Google.

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>0j80df17h7o37apxvgydqu5k4hlvepf</sha1>
    </revision>
    <revision>
      <id>22359</id>
      <parentid>22253</parentid>
      <timestamp>2025-08-26T23:26:36Z</timestamp>
      <contributor>
        <username>Mr Pollo</username>
        <id>391</id>
      </contributor>
      <origin>22359</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3089" sha1="41re7su4uo264lme0cuyofbb4mnlr14" xml:space="preserve">{{StubNotice}}

{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th 2025, Google has announced an upcoming application installation restriction on Google-certified Android devices, unless the developer is registered and verified through their Developer Verification program, which in some cases requires a legal identity document verification as well as a flat fee.

==Background==
On the Android mobile operating system, the user can, currently, freely install applications developed by anyone, with no kinds of penalty as to their origin, feature set or purpose. The only requirements is that the application follows the technical guidelines, that ensure that the application will be functional on the device, and is signed with any kind of certificate, which is required to maintain a chain of trust during application updates.

==Introduction of Developer Verification==
On August 25th 2025, Google has released&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer console {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; a roadmap of a new requirement for application installations called the Developer Verification, which will require developers to register on the Android Developer Console, if they want their applications to be installable after the roll out of this system. When registering, the developers are offered a choice&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; between "Limited" and "Full" distribution types. The "Limited" distribution type is considered by Google to be best for "students, hobbyists, and other personal use", and is free to register, unlike the "Full" distribution type, which is considered to be suited for "organizations and professional developers with wide distribution". The "Limited" type is stated to have a "capped number of apps and installs", unlike the "Full" type. It is currently unclear whether or not the "Limited" type requires any kind of identity verification, as opposed to "Full", which requires full identity verification, as stated by Google.

===Google's response===
{{Ph-I-ComR}}

==Consumer response==
{{Ph-I-ConR}}

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>41re7su4uo264lme0cuyofbb4mnlr14</sha1>
    </revision>
    <revision>
      <id>22751</id>
      <parentid>22359</parentid>
      <timestamp>2025-08-29T07:37:34Z</timestamp>
      <contributor>
        <ip>2A02:C7E:5EC1:5500:B8D7:AE91:562B:5337</ip>
      </contributor>
      <comment>Added consumer response link</comment>
      <origin>22751</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3318" sha1="sjk73zgsx69xwpcpg7p3k1w2ihnwf0u" xml:space="preserve">{{StubNotice}}

{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th 2025, Google has announced an upcoming application installation restriction on Google-certified Android devices, unless the developer is registered and verified through their Developer Verification program, which in some cases requires a legal identity document verification as well as a flat fee.

==Background==
On the Android mobile operating system, the user can, currently, freely install applications developed by anyone, with no kinds of penalty as to their origin, feature set or purpose. The only requirements is that the application follows the technical guidelines, that ensure that the application will be functional on the device, and is signed with any kind of certificate, which is required to maintain a chain of trust during application updates.

==Introduction of Developer Verification==
On August 25th 2025, Google has released&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer console {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; a roadmap of a new requirement for application installations called the Developer Verification, which will require developers to register on the Android Developer Console, if they want their applications to be installable after the roll out of this system. When registering, the developers are offered a choice&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; between "Limited" and "Full" distribution types. The "Limited" distribution type is considered by Google to be best for "students, hobbyists, and other personal use", and is free to register, unlike the "Full" distribution type, which is considered to be suited for "organizations and professional developers with wide distribution". The "Limited" type is stated to have a "capped number of apps and installs", unlike the "Full" type. It is currently unclear whether or not the "Limited" type requires any kind of identity verification, as opposed to "Full", which requires full identity verification, as stated by Google.

===Google's response===
{{Ph-I-ComR}}

==Consumer response==
{{Ph-I-ConR}}&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>sjk73zgsx69xwpcpg7p3k1w2ihnwf0u</sha1>
    </revision>
    <revision>
      <id>22754</id>
      <parentid>22751</parentid>
      <timestamp>2025-08-29T07:57:49Z</timestamp>
      <contributor>
        <ip>2A02:C7E:5EC1:5500:B8D7:AE91:562B:5337</ip>
      </contributor>
      <comment>Consumer response expanded from some of the key points highlighted in the Q&amp;A. Also touching on the Youtube response</comment>
      <origin>22754</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4794" sha1="65l5cwfhr6itmx9w126py4805i2iawy" xml:space="preserve">{{StubNotice}}

{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th 2025, Google has announced an upcoming application installation restriction on Google-certified Android devices, unless the developer is registered and verified through their Developer Verification program, which in some cases requires a legal identity document verification as well as a flat fee.

==Background==
On the Android mobile operating system, the user can, currently, freely install applications developed by anyone, with no kinds of penalty as to their origin, feature set or purpose. The only requirements is that the application follows the technical guidelines, that ensure that the application will be functional on the device, and is signed with any kind of certificate, which is required to maintain a chain of trust during application updates.

==Introduction of Developer Verification==
On August 25th 2025, Google has released&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer console {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; a roadmap of a new requirement for application installations called the Developer Verification, which will require developers to register on the Android Developer Console, if they want their applications to be installable after the roll out of this system. When registering, the developers are offered a choice&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; between "Limited" and "Full" distribution types. The "Limited" distribution type is considered by Google to be best for "students, hobbyists, and other personal use", and is free to register, unlike the "Full" distribution type, which is considered to be suited for "organizations and professional developers with wide distribution". The "Limited" type is stated to have a "capped number of apps and installs", unlike the "Full" type. It is currently unclear whether or not the "Limited" type requires any kind of identity verification, as opposed to "Full", which requires full identity verification, as stated by Google.

===Google's response===
{{Ph-I-ComR}}

==Consumer response==
{{Ph-I-ConR}}Alongside the announcement, Google provided a Q&amp;A page for existing developers to ask further questions&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;. There was a range of responses, some with practical questions about the implementation whereas others highlighting key flaws with the plans from both a consumer and developer perspective including:

* The hypocrisy of enforcing security on side loaded apps (i.e. user installed apps not from the playstore) whilst Google's playstore maintains its levels of scamware, malware and adware.
* The ambiguity of the announcement leading some to conclude you would have to pay a one time $25 fee to install apps on your own device.
* Confusion over the requirement to register every package name before it can be installed leading some developers whom beta test multiple versions of the same app to register huge slightly duplicated package names.
* The confusion over 'development version' apps being installed over ADB (a USB android debugging interface) and how they would persist and whether they need full verification.
* The requirement of app signing thus potentially meaning installing apps requires an internet connection. This essentially bricks the functionality of devices that are intended to be used offline e.g. barcode scanners in supermarkets etc.


There has also been much kickback by the android community with a plethora of videos being published online, including Google's own platform YouTube, about the harms this will cause and the angry user sentiment.

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>65l5cwfhr6itmx9w126py4805i2iawy</sha1>
    </revision>
    <revision>
      <id>22757</id>
      <parentid>22754</parentid>
      <timestamp>2025-08-29T08:06:47Z</timestamp>
      <contributor>
        <ip>2A02:C7E:5EC1:5500:B8D7:AE91:562B:5337</ip>
      </contributor>
      <comment>Add Consumer Response video links</comment>
      <origin>22757</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5429" sha1="9dap0bzc3pzgs5x9rarcgnu0gzrdab1" xml:space="preserve">{{StubNotice}}

{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th 2025, Google has announced an upcoming application installation restriction on Google-certified Android devices, unless the developer is registered and verified through their Developer Verification program, which in some cases requires a legal identity document verification as well as a flat fee.

==Background==
On the Android mobile operating system, the user can, currently, freely install applications developed by anyone, with no kinds of penalty as to their origin, feature set or purpose. The only requirements is that the application follows the technical guidelines, that ensure that the application will be functional on the device, and is signed with any kind of certificate, which is required to maintain a chain of trust during application updates.

==Introduction of Developer Verification==
On August 25th 2025, Google has released&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer console {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; a roadmap of a new requirement for application installations called the Developer Verification, which will require developers to register on the Android Developer Console, if they want their applications to be installable after the roll out of this system. When registering, the developers are offered a choice&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; between "Limited" and "Full" distribution types. The "Limited" distribution type is considered by Google to be best for "students, hobbyists, and other personal use", and is free to register, unlike the "Full" distribution type, which is considered to be suited for "organizations and professional developers with wide distribution". The "Limited" type is stated to have a "capped number of apps and installs", unlike the "Full" type. It is currently unclear whether or not the "Limited" type requires any kind of identity verification, as opposed to "Full", which requires full identity verification, as stated by Google.

===Google's response===
{{Ph-I-ComR}}

==Consumer response==
{{Ph-I-ConR}}Alongside the announcement, Google provided a Q&amp;A page for existing developers to ask further questions&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;. There was a range of responses, some with practical questions about the implementation whereas others highlighting key flaws with the plans from both a consumer and developer perspective including:

*The hypocrisy of enforcing security on side loaded apps (i.e. user installed apps not from the playstore) whilst Google's playstore maintains its levels of scamware, malware and adware.
*The ambiguity of the announcement leading some to conclude you would have to pay a one time $25 fee to install apps on your own device.
*Confusion over the requirement to register every package name before it can be installed leading some developers whom beta test multiple versions of the same app to register huge slightly duplicated package names.
*The confusion over 'development version' apps being installed over ADB (a USB android debugging interface) and how they would persist and whether they need full verification.
*The requirement of app signing thus potentially meaning installing apps requires an internet connection. This essentially bricks the functionality of devices that are intended to be used offline e.g. barcode scanners in supermarkets etc.


There has also been much kickback by the android community with a plethora of videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; being published online, including Google's own platform YouTube, about the harms this will cause and the angry user sentiment.

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>9dap0bzc3pzgs5x9rarcgnu0gzrdab1</sha1>
    </revision>
    <revision>
      <id>22759</id>
      <parentid>22757</parentid>
      <timestamp>2025-08-29T08:14:12Z</timestamp>
      <contributor>
        <ip>2A02:810D:548D:E500:5C12:AC0E:83CE:3E2E</ip>
      </contributor>
      <comment>/* Consumer response */ Formatting</comment>
      <origin>22759</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5428" sha1="svtkw9ediyqxn14dj2sxaft2t1sasvx" xml:space="preserve">{{StubNotice}}

{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th 2025, Google has announced an upcoming application installation restriction on Google-certified Android devices, unless the developer is registered and verified through their Developer Verification program, which in some cases requires a legal identity document verification as well as a flat fee.

==Background==
On the Android mobile operating system, the user can, currently, freely install applications developed by anyone, with no kinds of penalty as to their origin, feature set or purpose. The only requirements is that the application follows the technical guidelines, that ensure that the application will be functional on the device, and is signed with any kind of certificate, which is required to maintain a chain of trust during application updates.

==Introduction of Developer Verification==
On August 25th 2025, Google has released&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer console {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; a roadmap of a new requirement for application installations called the Developer Verification, which will require developers to register on the Android Developer Console, if they want their applications to be installable after the roll out of this system. When registering, the developers are offered a choice&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; between "Limited" and "Full" distribution types. The "Limited" distribution type is considered by Google to be best for "students, hobbyists, and other personal use", and is free to register, unlike the "Full" distribution type, which is considered to be suited for "organizations and professional developers with wide distribution". The "Limited" type is stated to have a "capped number of apps and installs", unlike the "Full" type. It is currently unclear whether or not the "Limited" type requires any kind of identity verification, as opposed to "Full", which requires full identity verification, as stated by Google.

===Google's response===
{{Ph-I-ComR}}

==Consumer response==
{{Ph-I-ConR}}Alongside the announcement, Google provided a Q&amp;A page for existing developers to ask further questions&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;. There was a range of responses, some with practical questions about the implementation whereas others highlighting key flaws with the plans from both a consumer and developer perspective including:

*The hypocrisy of enforcing security on side loaded apps (i.e. user installed apps not from the playstore) whilst Google's playstore maintains its levels of scamware, malware and adware.
*The ambiguity of the announcement leading some to conclude you would have to pay a one time $25 fee to install apps on your own device.
*Confusion over the requirement to register every package name before it can be installed leading some developers whom beta test multiple versions of the same app to register huge slightly duplicated package names.
*The confusion over 'development version' apps being installed over ADB (a USB android debugging interface) and how they would persist and whether they need full verification.
*The requirement of app signing thus potentially meaning installing apps requires an internet connection. This essentially bricks the functionality of devices that are intended to be used offline e.g. barcode scanners in supermarkets etc.

There has also been much kickback by the android community with a plethora of videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; being published online, including Google's own platform YouTube, about the harms this will cause and the angry user sentiment.

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>svtkw9ediyqxn14dj2sxaft2t1sasvx</sha1>
    </revision>
    <revision>
      <id>22769</id>
      <parentid>22759</parentid>
      <timestamp>2025-08-29T10:03:35Z</timestamp>
      <contributor>
        <ip>2A02:C7E:5EC1:5500:E46C:E13E:C1E2:F37B</ip>
      </contributor>
      <comment>Archived Q&amp;A page</comment>
      <origin>22769</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5647" sha1="4gno4auil6almab156te21qc3i9ghzv" xml:space="preserve">{{StubNotice}}

{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th 2025, Google has announced an upcoming application installation restriction on Google-certified Android devices, unless the developer is registered and verified through their Developer Verification program, which in some cases requires a legal identity document verification as well as a flat fee.

==Background==
On the Android mobile operating system, the user can, currently, freely install applications developed by anyone, with no kinds of penalty as to their origin, feature set or purpose. The only requirements is that the application follows the technical guidelines, that ensure that the application will be functional on the device, and is signed with any kind of certificate, which is required to maintain a chain of trust during application updates.

==Introduction of Developer Verification==
On August 25th 2025, Google has released&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer console {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; a roadmap of a new requirement for application installations called the Developer Verification, which will require developers to register on the Android Developer Console, if they want their applications to be installable after the roll out of this system. When registering, the developers are offered a choice&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; between "Limited" and "Full" distribution types. The "Limited" distribution type is considered by Google to be best for "students, hobbyists, and other personal use", and is free to register, unlike the "Full" distribution type, which is considered to be suited for "organizations and professional developers with wide distribution". The "Limited" type is stated to have a "capped number of apps and installs", unlike the "Full" type. It is currently unclear whether or not the "Limited" type requires any kind of identity verification, as opposed to "Full", which requires full identity verification, as stated by Google.

===Google's response===
{{Ph-I-ComR}}

==Consumer response==
{{Ph-I-ConR}}Alongside the announcement, Google provided a Q&amp;A page for existing developers to ask further questions&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;. There was a range of responses, some with practical questions about the implementation whereas others highlighting key flaws with the plans from both a consumer and developer perspective including:

*The hypocrisy of enforcing security on side loaded apps (i.e. user installed apps not from the playstore) whilst Google's playstore maintains its levels of scamware, malware and adware.
*The ambiguity of the announcement leading some to conclude you would have to pay a one time $25 fee to install apps on your own device.
*Confusion over the requirement to register every package name before it can be installed leading some developers whom beta test multiple versions of the same app to register huge slightly duplicated package names.
*The confusion over 'development version' apps being installed over ADB (a USB android debugging interface) and how they would persist and whether they need full verification.
*The requirement of app signing thus potentially meaning installing apps requires an internet connection. This essentially bricks the functionality of devices that are intended to be used offline e.g. barcode scanners in supermarkets etc.

There has also been much kickback by the android community with a plethora of videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; being published online, including Google's own platform YouTube, about the harms this will cause and the angry user sentiment.

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>4gno4auil6almab156te21qc3i9ghzv</sha1>
    </revision>
    <revision>
      <id>22770</id>
      <parentid>22769</parentid>
      <timestamp>2025-08-29T10:37:44Z</timestamp>
      <contributor>
        <username>ZoomySmile</username>
        <id>4929</id>
      </contributor>
      <comment>updating wording of this article</comment>
      <origin>22770</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5719" sha1="8ytht826p4xu2ewdhp3xxw1zbr8526u" xml:space="preserve">{{StubNotice}}

{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th 2025, Google has announced an upcoming application installation restriction on Google-certified Android devices, unless the developer is registered and verified through their Developer Verification program, which in some cases requires a legal identity document verification as well as a flat fee.

==Background==
On the Android mobile operating system, the user can, currently, freely install applications developed by anyone, with no kinds of penalty as to their origin, feature set or purpose. The only requirements is that the application follows the technical guidelines, that ensure that the application will be functional on the device, and is signed with any kind of certificate, which is required to maintain a chain of trust during application updates.

==Introduction of Developer Verification==
On August 25th 2025, Google has released&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer console {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; a roadmap of a new requirement for application installations called the Developer Verification, which will require developers to register on the Android Developer Console, if they want their applications to be installable after the roll out of this system. When registering, the developers are offered a choice&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; between "Limited" and "Full" distribution types. The "Limited" distribution type is considered by Google to be best for "students, hobbyists, and other personal use", and is free to register, unlike the "Full" distribution type, which is considered to be suited for "organizations and professional developers with wide distribution". The "Limited" type is stated to have a "capped number of apps and installs", unlike the "Full" type. It is currently unclear whether or not the "Limited" type requires any kind of identity verification, as opposed to "Full", which requires full identity verification, as stated by Google.

==Consumer response==
Alongside the announcement, Google provided a Q&amp;A page for existing developers to ask further questions&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;. There was a range of responses, some with practical questions about the implementation whereas others highlighting key flaws with the plans from both a consumer and developer perspective including:

*Android users highlighting the hypocrisy of enforcing security on side loaded apps (i.e. user installed apps not from the playstore) whilst they have observed Google's playstore distributing apps that could be classified as scamware, malware and adware.
*The ambiguity of the announcement leading some to conclude you would have to pay a one time $25 fee to install apps on your own device.
*Confusion over the requirement to register every package name before it can be installed leading some developers whom beta test multiple versions of the same app by using different package names with problems about how they will be able to resolve this issue.
*The confusion over 'development version' apps being installed over ADB (a USB android debugging interface) and how they would persist on device and whether they need full verification.
*The requirement of app signing thus potentially meaning installing apps requires an internet connection. This essentially bricks the functionality of devices that are intended to be used offline e.g. barcode scanners in supermarkets etc.

There has also been much kickback by the android community with a plethora of videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; being published online, including Google's own platform YouTube, about the harms this will cause and the angry user sentiment.

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>8ytht826p4xu2ewdhp3xxw1zbr8526u</sha1>
    </revision>
    <revision>
      <id>22972</id>
      <parentid>22770</parentid>
      <timestamp>2025-08-30T21:30:54Z</timestamp>
      <contributor>
        <username>Louis</username>
        <id>1</id>
      </contributor>
      <origin>22972</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17507" sha1="j1e9akji9r20lg7gnf3tqjgr619bygg" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, Google announced an upcoming application installation restriction on Google-certified Android devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source through a process known as sideloading. This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like F-Droid, &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the Epic Games case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and Rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

==Technical Implementation==

===Distribution Types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full Distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited Distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package Name Registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-29}}&lt;/ref&gt;.

===Affected Devices===
The requirements apply to all ''"Google-certified Android devices,"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer Response==

===Technical Concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and Safety Concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open Source Community Impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and User Response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and Organizational Response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://developersalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |website=Developers Alliance |access-date=2025-08-29}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

===Notable Silence===
Major advocacy organizations remained notably absent from initial responses, with no specific statements located from:
*Electronic Frontier Foundation
*Consumer Reports
*BEUC (European Consumer Organisation)
*Which? (UK consumer advocacy)

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative App Stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational Development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory Context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU Digital Markets Act investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==Implementation Timeline==
Google announced a phased global rollout&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Unanswered Questions==
Several critical implementation details remain unclear:
*Specific caps for Limited Distribution accounts
*Debug keystore handling for development workflows
*Treatment of apps installed before the deadline
*Offline/airgapped deployment procedures
*Identity verification requirements for Limited accounts
*Appeals process for rejected verifications
*Data retention and deletion policies for developer information

==See Also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]
[[Category:Digital restrictions]]
[[Category:Privacy violations]]
[[Category:2025]]</text>
      <sha1>j1e9akji9r20lg7gnf3tqjgr619bygg</sha1>
    </revision>
    <revision>
      <id>22986</id>
      <parentid>22972</parentid>
      <timestamp>2025-08-30T23:05:58Z</timestamp>
      <contributor>
        <username>Keith</username>
        <id>4</id>
      </contributor>
      <comment>Sentence case. Deleted notable silence section, as I don;t think it makes sense for an article on such a recent topic</comment>
      <origin>22986</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17245" sha1="o0rlkprhfx5ucyzwe15o601e78vuixr" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, Google announced an upcoming application installation restriction on Google-certified Android devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source through a process known as sideloading. This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like F-Droid, &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the Epic Games case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-29}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"Google-certified Android devices,"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://developersalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |website=Developers Alliance |access-date=2025-08-29}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU Digital Markets Act investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==Implementation timeline==
Google announced a phased global rollout&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Unanswered questions==
Several critical implementation details remain unclear:
*Specific caps for Limited Distribution accounts
*Debug keystore handling for development workflows
*Treatment of apps installed before the deadline
*Offline/airgapped deployment procedures
*Identity verification requirements for Limited accounts
*Appeals process for rejected verifications
*Data retention and deletion policies for developer information

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]
[[Category:Digital restrictions]]
[[Category:Privacy violations]]
[[Category:2025]]</text>
      <sha1>o0rlkprhfx5ucyzwe15o601e78vuixr</sha1>
    </revision>
    <revision>
      <id>22987</id>
      <parentid>22986</parentid>
      <timestamp>2025-08-30T23:07:43Z</timestamp>
      <contributor>
        <username>Keith</username>
        <id>4</id>
      </contributor>
      <comment>/* Unanswered questions */</comment>
      <origin>22987</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="16808" sha1="06jpoeigghjg5xhao8ob8pfv2crnya0" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, Google announced an upcoming application installation restriction on Google-certified Android devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source through a process known as sideloading. This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like F-Droid, &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the Epic Games case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-29}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"Google-certified Android devices,"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://developersalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |website=Developers Alliance |access-date=2025-08-29}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU Digital Markets Act investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==Implementation timeline==
Google announced a phased global rollout&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]
[[Category:Digital restrictions]]
[[Category:Privacy violations]]
[[Category:2025]]</text>
      <sha1>06jpoeigghjg5xhao8ob8pfv2crnya0</sha1>
    </revision>
    <revision>
      <id>23001</id>
      <parentid>22987</parentid>
      <timestamp>2025-08-31T05:37:53Z</timestamp>
      <contributor>
        <username>-u-n-</username>
        <id>4586</id>
      </contributor>
      <minor/>
      <comment>Link some articles, move timeline to Announcement section</comment>
      <origin>23001</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="16855" sha1="rufdhq82k8zm877g1m175apetqvxmwu" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source through a process known as [[sideloading]]. This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

===Implementation timeline===
The implementation will be conducted in global rollout phases&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-29}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"Google-certified Android devices,"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://developersalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |website=Developers Alliance |access-date=2025-08-29}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]
[[Category:Digital restrictions]]
[[Category:Privacy violations]]
[[Category:2025]]</text>
      <sha1>rufdhq82k8zm877g1m175apetqvxmwu</sha1>
    </revision>
    <revision>
      <id>23002</id>
      <parentid>23001</parentid>
      <timestamp>2025-08-31T06:17:54Z</timestamp>
      <contributor>
        <ip>110.226.176.187</ip>
      </contributor>
      <comment>/* Affected devices */  add link to official list of android partners</comment>
      <origin>23002</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="16900" sha1="n9wrp6zqy22zqa3l21if979768ejwlz" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source through a process known as [[sideloading]]. This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

===Implementation timeline===
The implementation will be conducted in global rollout phases&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-29}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://developersalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |website=Developers Alliance |access-date=2025-08-29}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]
[[Category:Digital restrictions]]
[[Category:Privacy violations]]
[[Category:2025]]</text>
      <sha1>n9wrp6zqy22zqa3l21if979768ejwlz</sha1>
    </revision>
    <revision>
      <id>23237</id>
      <parentid>23002</parentid>
      <timestamp>2025-09-01T19:21:18Z</timestamp>
      <contributor>
        <username>Jelly1joe</username>
        <id>3997</id>
      </contributor>
      <comment>It is not sideloading, don't accept the premise of assholes</comment>
      <origin>23237</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="16892" sha1="kueynhokqri7jf6w6z5o0aalwfwtwho" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

===Implementation timeline===
The implementation will be conducted in global rollout phases&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-29}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://developersalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |website=Developers Alliance |access-date=2025-08-29}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]
[[Category:Digital restrictions]]
[[Category:Privacy violations]]
[[Category:2025]]</text>
      <sha1>kueynhokqri7jf6w6z5o0aalwfwtwho</sha1>
    </revision>
    <revision>
      <id>23418</id>
      <parentid>23237</parentid>
      <timestamp>2025-09-02T13:26:51Z</timestamp>
      <contributor>
        <ip>70.22.187.30</ip>
      </contributor>
      <comment>Add additional reference for 50% install ownership threshold</comment>
      <origin>23418</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17197" sha1="rrsq7ckq7q8kf6y546fgp8vnttofz16" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

===Implementation timeline===
The implementation will be conducted in global rollout phases&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://developersalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |website=Developers Alliance |access-date=2025-08-29}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]
[[Category:Digital restrictions]]
[[Category:Privacy violations]]
[[Category:2025]]</text>
      <sha1>rrsq7ckq7q8kf6y546fgp8vnttofz16</sha1>
    </revision>
    <revision>
      <id>28109</id>
      <parentid>23418</parentid>
      <timestamp>2025-10-21T19:25:58Z</timestamp>
      <contributor>
        <username>AnotherConsumerRightsPerson</username>
        <id>4554</id>
      </contributor>
      <comment>-cats</comment>
      <origin>28109</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17113" sha1="eqawlt21x51fe8rmke4qjvqguclp8cs" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

===Implementation timeline===
The implementation will be conducted in global rollout phases&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://developersalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |website=Developers Alliance |access-date=2025-08-29}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>eqawlt21x51fe8rmke4qjvqguclp8cs</sha1>
    </revision>
    <revision>
      <id>28993</id>
      <parentid>28109</parentid>
      <timestamp>2025-10-29T12:21:19Z</timestamp>
      <contributor>
        <username>EricKotato</username>
        <id>6834</id>
      </contributor>
      <comment>Replaced dead url to Developer Alliance article with working one, added archived copy of it</comment>
      <origin>28993</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17294" sha1="nqcafma30951w0cqeh90fxzc9hhyhaz" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

===Implementation timeline===
The implementation will be conducted in global rollout phases&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>nqcafma30951w0cqeh90fxzc9hhyhaz</sha1>
    </revision>
    <revision>
      <id>29097</id>
      <parentid>28993</parentid>
      <timestamp>2025-10-30T23:34:38Z</timestamp>
      <contributor>
        <username>JustClippy</username>
        <id>6842</id>
      </contributor>
      <comment>added urgent take action section and useful resources from techlore</comment>
      <origin>29097</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17693" sha1="297hya271e7x7i51lgxg89uhnlrj1gw" xml:space="preserve">== Take Action, Make Our Voice Heard ==
Direct link to the useful resources provided by the [https://www.youtube.com/@techlore Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

* ways to contact national regulators
* petitions
* open letter and petitions
* f-droid additional sources
* editorial blogs and press reactions
* public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

===Implementation timeline===
The implementation will be conducted in global rollout phases&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>297hya271e7x7i51lgxg89uhnlrj1gw</sha1>
    </revision>
    <revision>
      <id>29235</id>
      <parentid>29097</parentid>
      <timestamp>2025-11-01T00:19:15Z</timestamp>
      <contributor>
        <username>JustClippy</username>
        <id>6842</id>
      </contributor>
      <comment>minor fix on duplicates</comment>
      <origin>29235</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17674" sha1="4drji5re41euv3k5p25ax5ggmawku2n" xml:space="preserve">==Take Action, Make Our Voice Heard==
Direct link to the useful resources provided by the [https://www.youtube.com/@techlore Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

===Implementation timeline===
The implementation will be conducted in global rollout phases&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>4drji5re41euv3k5p25ax5ggmawku2n</sha1>
    </revision>
    <revision>
      <id>30143</id>
      <parentid>29235</parentid>
      <timestamp>2025-11-08T18:26:10Z</timestamp>
      <contributor>
        <ip>2A02:16A:6405:0:1D32:6057:AF3E:53E</ip>
      </contributor>
      <comment>fix capitalisation</comment>
      <origin>30143</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17674" sha1="dnejtcbdvh1t8v3bc5hrrdfsk18r6xx" xml:space="preserve">==Take Action, Make Our Voice Heard==
Direct link to the useful resources provided by the [https://www.youtube.com/@techlore Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple"&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;.

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;. According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt;. The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags."''

===Implementation timeline===
The implementation will be conducted in global rollout phases&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification |url-status=live |access-date=2025-08-29}}&lt;/ref&gt;:

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;:

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;.

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;:
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming"&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt;. Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;, including:

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;, with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;.

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on Specific Use Cases==

===Enterprise and MDM Deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt;. Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt;. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;.

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt;, though no specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>dnejtcbdvh1t8v3bc5hrrdfsk18r6xx</sha1>
    </revision>
    <revision>
      <id>30167</id>
      <parentid>30143</parentid>
      <timestamp>2025-11-08T21:25:10Z</timestamp>
      <contributor>
        <ip>2A00:23C8:2384:101:B34:3E7B:6AF4:18CF</ip>
      </contributor>
      <comment>better matching the style guide, replaced dupe ref</comment>
      <origin>30167</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17496" sha1="diy6erahg1pxjfxkdjkestd06rmzoo4" xml:space="preserve">==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://www.youtube.com/@techlore Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>diy6erahg1pxjfxkdjkestd06rmzoo4</sha1>
    </revision>
    <revision>
      <id>30168</id>
      <parentid>30167</parentid>
      <timestamp>2025-11-08T21:26:32Z</timestamp>
      <contributor>
        <ip>2A00:23C8:2384:101:B34:3E7B:6AF4:18CF</ip>
      </contributor>
      <comment>/* Take action, make our voice heard */ better link for Techlore</comment>
      <origin>30168</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17484" sha1="gr8b8jbh2o133gfieiofhcwaz5zrvwc" xml:space="preserve">==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with Google Mobile Services (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>gr8b8jbh2o133gfieiofhcwaz5zrvwc</sha1>
    </revision>
    <revision>
      <id>30284</id>
      <parentid>30168</parentid>
      <timestamp>2025-11-11T05:27:24Z</timestamp>
      <contributor>
        <username>Rudxain</username>
        <id>5995</id>
      </contributor>
      <minor/>
      <comment>link to GMS</comment>
      <origin>30284</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17488" sha1="85vvtpl6mbh380tc0i16etick5jhbwr" xml:space="preserve">==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*Play Store developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>85vvtpl6mbh380tc0i16etick5jhbwr</sha1>
    </revision>
    <revision>
      <id>30285</id>
      <parentid>30284</parentid>
      <timestamp>2025-11-11T05:31:30Z</timestamp>
      <contributor>
        <username>Rudxain</username>
        <id>5995</id>
      </contributor>
      <minor/>
      <comment>link to wp:G-Play-Store</comment>
      <origin>30285</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17514" sha1="2vttj8sr7zvjysuttti0upsaz1y7xc0" xml:space="preserve">==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Full distribution====
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**For organizations: D-U-N-S number (can take up to 28 days to obtain)
*No limits on app numbers or installations

====Limited distribution====
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Identity verification requirements unclear

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via FreeDroidWarn that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>2vttj8sr7zvjysuttti0upsaz1y7xc0</sha1>
    </revision>
    <revision>
      <id>30304</id>
      <parentid>30285</parentid>
      <timestamp>2025-11-11T11:33:22Z</timestamp>
      <contributor>
        <ip>2001:DF4:E000:3FD3:A4E3:D846:E3A5:4FFA</ip>
      </contributor>
      <comment>Summarized a bunch of criticisms with citations, reorganized a section to highlight important bits</comment>
      <origin>30304</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22018" sha1="7n2kymuynfqabwky1k4axy7dkbpshei" xml:space="preserve">==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email 
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>7n2kymuynfqabwky1k4axy7dkbpshei</sha1>
    </revision>
    <revision>
      <id>30552</id>
      <parentid>30304</parentid>
      <timestamp>2025-11-16T00:05:35Z</timestamp>
      <contributor>
        <ip>2001:DF4:E000:3FD3:DCE9:CB8C:5D66:F3E5</ip>
      </contributor>
      <comment>/* Open source community impact */ Kotatsu shutdown</comment>
      <origin>30552</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22445" sha1="ia2b7vwywwpnncukpbjeycpf1f52div" xml:space="preserve">==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]
[[Category:Google]]</text>
      <sha1>ia2b7vwywwpnncukpbjeycpf1f52div</sha1>
    </revision>
    <revision>
      <id>31013</id>
      <parentid>30552</parentid>
      <timestamp>2025-11-24T17:53:58Z</timestamp>
      <contributor>
        <username>AnotherConsumerRightsPerson</username>
        <id>4554</id>
      </contributor>
      <comment>-cats</comment>
      <origin>31013</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22425" sha1="m3rhi5ebomjxya0a6ndfvocnqr26jre" xml:space="preserve">==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Has ''"capped number of apps and installs"'' (specific limits not disclosed)
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>m3rhi5ebomjxya0a6ndfvocnqr26jre</sha1>
    </revision>
    <revision>
      <id>32147</id>
      <parentid>31013</parentid>
      <timestamp>2025-12-19T11:00:56Z</timestamp>
      <contributor>
        <ip>31.175.14.26</ip>
      </contributor>
      <comment>Updated the description of the "limited distribution" to mention a limit provided by google when creating an early access account</comment>
      <origin>32147</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22597" sha1="htwws3lqzlz6ktsrcavkd4behcr1ht1" xml:space="preserve">==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>htwws3lqzlz6ktsrcavkd4behcr1ht1</sha1>
    </revision>
    <revision>
      <id>33543</id>
      <parentid>32147</parentid>
      <timestamp>2026-01-14T21:42:09Z</timestamp>
      <contributor>
        <username>JodyBruchonFan</username>
        <id>5871</id>
      </contributor>
      <comment>+[[:File:If Google were honest - Android developer verification.png]]</comment>
      <origin>33543</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22723" sha1="pekwrkz6z2wss0v8eqku18d9n0e5t2k" xml:space="preserve">[[File:If Google were honest - Android developer verification.png|thumb|If Google were honest about developer verification.]]
==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem.

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>pekwrkz6z2wss0v8eqku18d9n0e5t2k</sha1>
    </revision>
    <revision>
      <id>33544</id>
      <parentid>33543</parentid>
      <timestamp>2026-01-14T21:45:04Z</timestamp>
      <contributor>
        <username>JodyBruchonFan</username>
        <id>5871</id>
      </contributor>
      <comment>Abandonment of Android's founding principles.</comment>
      <origin>33544</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22941" sha1="ixmp883hptxcx4zbtxi3jas2i2abi31" xml:space="preserve">[[File:If Google were honest - Android developer verification.png|thumb|If Google were honest about developer verification.]]

On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their real-life identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;[https://archive.today/2012.12.04-171030/http://source.android.com/about/philosophy.html Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt;

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions
{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>ixmp883hptxcx4zbtxi3jas2i2abi31</sha1>
    </revision>
    <revision>
      <id>33546</id>
      <parentid>33544</parentid>
      <timestamp>2026-01-14T22:52:28Z</timestamp>
      <contributor>
        <username>Bythmusters</username>
        <id>6960</id>
      </contributor>
      <comment>I think it's a funny image but it's not suitable for an informative article. Maybe it could exist somewhere else</comment>
      <origin>33546</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22824" sha1="i0cg0mp1vwvfznf7gvy3mbq6zrxkfqm" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register &amp; verify their real-life identity through the Developer Verification program before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including sideloading, third-party app stores, &amp; direct APK installations. This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;[https://archive.today/2012.12.04-171030/http://source.android.com/about/philosophy.html Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt;

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>i0cg0mp1vwvfznf7gvy3mbq6zrxkfqm</sha1>
    </revision>
    <revision>
      <id>33735</id>
      <parentid>33546</parentid>
      <timestamp>2026-01-16T10:12:20Z</timestamp>
      <contributor>
        <username>JodyBruchonFan</username>
        <id>5871</id>
      </contributor>
      <comment>"Open... except apps we dislike." "Don't you dare own permanent local backups of YouTube videos!" - the corporate doublespeak is extremely in-your-face.</comment>
      <origin>33735</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="23693" sha1="lsvl7gvii0xh495u5iif8sgqnyk53n5" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/http://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;[https://archive.today/2012.12.04-171030/http://source.android.com/about/philosophy.html Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt; It gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem (a popular example being TubeMate), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects&lt;/ref&gt;

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>lsvl7gvii0xh495u5iif8sgqnyk53n5</sha1>
    </revision>
    <revision>
      <id>35065</id>
      <parentid>33735</parentid>
      <timestamp>2026-01-26T09:45:13Z</timestamp>
      <contributor>
        <username>JodyBruchonFan</username>
        <id>5871</id>
      </contributor>
      <comment>Another reason this is diabolical and why Google won't change their minds.</comment>
      <origin>35065</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="23907" sha1="he86ifx7qq57hbtuneuqfy058bt3wnr" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/http://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;[https://archive.today/2012.12.04-171030/http://source.android.com/about/philosophy.html Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects&lt;/ref&gt;

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app stores, open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>he86ifx7qq57hbtuneuqfy058bt3wnr</sha1>
    </revision>
    <revision>
      <id>35066</id>
      <parentid>35065</parentid>
      <timestamp>2026-01-26T09:53:34Z</timestamp>
      <contributor>
        <username>JodyBruchonFan</username>
        <id>5871</id>
      </contributor>
      <comment>/* Background */ more benefits of APK files</comment>
      <origin>35066</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="24242" sha1="dqygrb4w7jvgwhdlujmtvqy4o7r5ln3" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/http://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;[https://archive.today/2012.12.04-171030/http://source.android.com/about/philosophy.html Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects&lt;/ref&gt;

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>dqygrb4w7jvgwhdlujmtvqy4o7r5ln3</sha1>
    </revision>
    <revision>
      <id>35067</id>
      <parentid>35066</parentid>
      <timestamp>2026-01-26T09:55:48Z</timestamp>
      <contributor>
        <username>JodyBruchonFan</username>
        <id>5871</id>
      </contributor>
      <comment>/* Background */ added exmple</comment>
      <origin>35067</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="24306" sha1="2n48gyccs8v7jhxfu644yaglpt4ccqf" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/http://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;[https://archive.today/2012.12.04-171030/http://source.android.com/about/philosophy.html Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects&lt;/ref&gt;

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>2n48gyccs8v7jhxfu644yaglpt4ccqf</sha1>
    </revision>
    <revision>
      <id>36078</id>
      <parentid>35067</parentid>
      <timestamp>2026-02-03T23:55:49Z</timestamp>
      <contributor>
        <username>JodyBruchonFan</username>
        <id>5871</id>
      </contributor>
      <comment>Added more reasons this is very bad. This benefits the elite ruling class to the detriment of the rest of us.</comment>
      <origin>36078</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="26145" sha1="5z66tih9xbn771ec9dmlwvmc5k5m6ga" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/http://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;[https://archive.today/2012.12.04-171030/http://source.android.com/about/philosophy.html Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN]&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products]&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google]&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>5z66tih9xbn771ec9dmlwvmc5k5m6ga</sha1>
    </revision>
    <revision>
      <id>36704</id>
      <parentid>36078</parentid>
      <timestamp>2026-02-11T17:39:55Z</timestamp>
      <contributor>
        <username>JodyBruchonFan</username>
        <id>5871</id>
      </contributor>
      <comment>clarified</comment>
      <origin>36704</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="26170" sha1="lh4ypq6m1igcyopx6qfdriancc3nt1u" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/http://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;[https://archive.today/2012.12.04-171030/http://source.android.com/about/philosophy.html Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN]&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products]&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google]&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>lh4ypq6m1igcyopx6qfdriancc3nt1u</sha1>
    </revision>
    <revision>
      <id>36706</id>
      <parentid>36704</parentid>
      <timestamp>2026-02-11T17:42:09Z</timestamp>
      <contributor>
        <username>AnotherConsumerRightsPerson</username>
        <id>4554</id>
      </contributor>
      <minor/>
      <comment>http to https with [[wikipedia:WP:AWB|AutoWikiBrowser]], replaced: http: → https: (2)</comment>
      <origin>36706</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="26172" sha1="hlaic51vlh1471fsozliwevpv1x1msg" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;[https://archive.today/2012.12.04-171030/https://source.android.com/about/philosophy.html Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN]&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products]&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google]&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>hlaic51vlh1471fsozliwevpv1x1msg</sha1>
    </revision>
    <revision>
      <id>37081</id>
      <parentid>36706</parentid>
      <timestamp>2026-02-15T22:49:06Z</timestamp>
      <contributor>
        <username>Banana</username>
        <id>6361</id>
      </contributor>
      <comment>Added archive URLs for 16 citation(s) using CRWCitationBot</comment>
      <origin>37081</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="28997" sha1="mj82z4pbmkar6wbuzyz7snyz5ymhhpv" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;[https://archive.today/2012.12.04-171030/https://source.android.com/about/philosophy.html Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN]&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products]&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google]&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>mj82z4pbmkar6wbuzyz7snyz5ymhhpv</sha1>
    </revision>
    <revision>
      <id>37082</id>
      <parentid>37081</parentid>
      <timestamp>2026-02-15T22:53:44Z</timestamp>
      <contributor>
        <username>Banana</username>
        <id>6361</id>
      </contributor>
      <minor/>
      <origin>37082</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="29057" sha1="ej7i9jbk34a821guez19fxjdkqho1h8" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([https://archive.today/2012.12.04-171030/https://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN]&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products]&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google]&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>ej7i9jbk34a821guez19fxjdkqho1h8</sha1>
    </revision>
    <revision>
      <id>38031</id>
      <parentid>37082</parentid>
      <timestamp>2026-02-21T18:33:03Z</timestamp>
      <contributor>
        <ip>2001:DF4:E000:3FD3:D033:2127:B544:BDD8</ip>
      </contributor>
      <comment>/* Announcement and rationale */ advanced flow and f-droid latest news</comment>
      <origin>38031</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="30297" sha1="2ge4takomo3b1inut5kg5vz4pdchp3r" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([https://archive.today/2012.12.04-171030/https://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012)&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN]&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products]&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google]&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

=== Updates ===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}}&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}}&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}}&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}}&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}}&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>2ge4takomo3b1inut5kg5vz4pdchp3r</sha1>
    </revision>
    <revision>
      <id>38478</id>
      <parentid>38031</parentid>
      <timestamp>2026-02-23T02:53:54Z</timestamp>
      <contributor>
        <username>Bananabot</username>
        <id>8392</id>
      </contributor>
      <comment>Added archive URLs for 13 citation(s) using CRWCitationBot</comment>
      <origin>38478</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="32051" sha1="onyvirfsqjsp4puy4ydthf21cosa1vv" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([https://archive.today/2012.12.04-171030/https://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

=== Updates ===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}} ([https://preservetube.com/watch?v=-nCgnXByGrY Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>onyvirfsqjsp4puy4ydthf21cosa1vv</sha1>
    </revision>
    <revision>
      <id>38479</id>
      <parentid>38478</parentid>
      <timestamp>2026-02-23T02:57:11Z</timestamp>
      <contributor>
        <username>Banana</username>
        <id>6361</id>
      </contributor>
      <minor/>
      <origin>38479</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31993" sha1="adai3heiu30ztc5s54cz1t4hmem0bm6" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([https://archive.today/2012.12.04-171030/https://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

=== Updates ===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>adai3heiu30ztc5s54cz1t4hmem0bm6</sha1>
    </revision>
    <revision>
      <id>39116</id>
      <parentid>38479</parentid>
      <timestamp>2026-02-23T12:15:48Z</timestamp>
      <contributor>
        <username>Bananabot</username>
        <id>8392</id>
      </contributor>
      <comment>Added archive URLs for 1 citation(s) using CRWCitationBot</comment>
      <origin>39116</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="32077" sha1="ffwi4hrdu9ltdy1yctv02su1yqcs3i9" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([https://archive.today/2012.12.04-171030/https://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

=== Updates ===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>ffwi4hrdu9ltdy1yctv02su1yqcs3i9</sha1>
    </revision>
    <revision>
      <id>39537</id>
      <parentid>39116</parentid>
      <timestamp>2026-02-24T17:27:45Z</timestamp>
      <contributor>
        <ip>2001:DF4:E000:3FD3:71:5E36:B650:9B75</ip>
      </contributor>
      <comment>/* Updates */ Info on Open Letter to Google just published</comment>
      <origin>39537</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="33719" sha1="mws8iuq6qk8pvpg4erfvaspzgytcfjf" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([https://archive.today/2012.12.04-171030/https://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeeping software beyond it's own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>mws8iuq6qk8pvpg4erfvaspzgytcfjf</sha1>
    </revision>
    <revision>
      <id>39556</id>
      <parentid>39537</parentid>
      <timestamp>2026-02-24T19:22:20Z</timestamp>
      <contributor>
        <username>Bananabot</username>
        <id>8392</id>
      </contributor>
      <comment>Replace archive.today citations with archive.org equivalents (1 citation(s))</comment>
      <origin>39556</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="33720" sha1="qgbg3w4v63us364b65uo3evh3myfevx" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeeping software beyond it's own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>qgbg3w4v63us364b65uo3evh3myfevx</sha1>
    </revision>
    <revision>
      <id>39587</id>
      <parentid>39556</parentid>
      <timestamp>2026-02-24T23:06:00Z</timestamp>
      <contributor>
        <username>JustClippy</username>
        <id>6842</id>
      </contributor>
      <minor/>
      <comment>/* Take action, make our voice heard */</comment>
      <origin>39587</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="33869" sha1="8bb63htu5k86a4kke4bt9d8bjrkx4hp" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

=== Open Letter to Google ===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeeping software beyond it's own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>8bb63htu5k86a4kke4bt9d8bjrkx4hp</sha1>
    </revision>
    <revision>
      <id>40981</id>
      <parentid>39587</parentid>
      <timestamp>2026-03-04T23:20:17Z</timestamp>
      <contributor>
        <ip>185.47.220.165</ip>
      </contributor>
      <comment>/* Announcement and rationale */ fix grammar</comment>
      <origin>40981</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="33865" sha1="fgsjs1m789vv3k7flbpckxb2vrrt7re" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

=== Open Letter to Google ===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>fgsjs1m789vv3k7flbpckxb2vrrt7re</sha1>
    </revision>
    <revision>
      <id>41294</id>
      <parentid>40981</parentid>
      <timestamp>2026-03-06T02:23:02Z</timestamp>
      <contributor>
        <ip>2804:214:88E1:B3BD:B07C:9AD1:105D:C06C</ip>
      </contributor>
      <comment>Usuario</comment>
      <origin>41294</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="33898" sha1="4egi1s2tgyrnthx4opja8j0bszq0js0" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>4egi1s2tgyrnthx4opja8j0bszq0js0</sha1>
    </revision>
    <revision>
      <id>41376</id>
      <parentid>41294</parentid>
      <timestamp>2026-03-06T13:08:25Z</timestamp>
      <contributor>
        <ip>2001:DF4:E000:3FD3:9CBF:171E:FA88:15CF</ip>
      </contributor>
      <comment>/* Updates */ info on registered appstore program</comment>
      <origin>41376</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="35209" sha1="tgqew579u47bl2elk49u9b6x3bccww3" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>tgqew579u47bl2elk49u9b6x3bccww3</sha1>
    </revision>
    <revision>
      <id>41377</id>
      <parentid>41376</parentid>
      <timestamp>2026-03-06T13:09:32Z</timestamp>
      <contributor>
        <ip>2001:DF4:E000:3FD3:9CBF:171E:FA88:15CF</ip>
      </contributor>
      <comment>/* Updates */ date</comment>
      <origin>41377</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="35211" sha1="a41wrb4j8rnsfi3thlbkw2uoyywlasc" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;[https://archive.today/2025.08.26-115350/https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Android developer console  &amp;#x7c;  Android developer verification  &amp;#x7c;  Android Developers]&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |title=(Archive) Keep Android Open |url=https://web.archive.org/web/20251109112509/keepandroidopen.org |url-status=live}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>a41wrb4j8rnsfi3thlbkw2uoyywlasc</sha1>
    </revision>
    <revision>
      <id>42246</id>
      <parentid>41377</parentid>
      <timestamp>2026-03-10T00:24:01Z</timestamp>
      <contributor>
        <username>Marc84</username>
        <id>8296</id>
      </contributor>
      <comment>/* References */ Fix archive links.</comment>
      <origin>42246</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="35455" sha1="qtupf4wvehakkibvza4bdhr25gbjpob" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://archive.ph/MHGun |archive-date=2025-11-12 |website=Android Developers}} [https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification Archived] 2025-08-25.&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>qtupf4wvehakkibvza4bdhr25gbjpob</sha1>
    </revision>
    <revision>
      <id>42260</id>
      <parentid>42246</parentid>
      <timestamp>2026-03-10T00:29:59Z</timestamp>
      <contributor>
        <username>Marc84</username>
        <id>8296</id>
      </contributor>
      <comment>/* References */ Remove archive.today link.</comment>
      <origin>42260</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="35407" sha1="jps7edypk3h49t1ze1vrws8t5v0ehwp" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |website=Android Developers}}&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>jps7edypk3h49t1ze1vrws8t5v0ehwp</sha1>
    </revision>
    <revision>
      <id>43089</id>
      <parentid>42260</parentid>
      <timestamp>2026-03-13T11:50:02Z</timestamp>
      <contributor>
        <ip>49.237.17.8</ip>
      </contributor>
      <origin>43089</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="35447" sha1="l29ehec7jesp9wwkq7owuvmhgta6yqs" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=d89e2e8dc28a93bcdc3984265466242a4493fbaf
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |website=Android Developers}}&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>l29ehec7jesp9wwkq7owuvmhgta6yqs</sha1>
    </revision>
    <revision>
      <id>43847</id>
      <parentid>43089</parentid>
      <timestamp>2026-03-16T07:03:52Z</timestamp>
      <contributor>
        <username>Rudxain</username>
        <id>5995</id>
      </contributor>
      <minor/>
      <comment>add "Forced account" to "See also"</comment>
      <origin>43847</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="35467" sha1="ojx4hw73oihl4yfyw3umdbwi16acwuw" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=d89e2e8dc28a93bcdc3984265466242a4493fbaf
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |website=Android Developers}}&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Forced account]]
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>ojx4hw73oihl4yfyw3umdbwi16acwuw</sha1>
    </revision>
    <revision>
      <id>44186</id>
      <parentid>43847</parentid>
      <timestamp>2026-03-17T08:10:01Z</timestamp>
      <contributor>
        <ip>188.236.230.240</ip>
      </contributor>
      <comment>Fixed typo</comment>
      <origin>44186</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="30586" sha1="3190ocbzlytdbqh9xu3t7ckw2i17be9" xml:space="preserve">==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Forced account]]
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>3190ocbzlytdbqh9xu3t7ckw2i17be9</sha1>
    </revision>
    <revision>
      <id>45016</id>
      <parentid>44186</parentid>
      <timestamp>2026-03-19T21:07:20Z</timestamp>
      <contributor>
        <ip>103.27.10.78</ip>
      </contributor>
      <comment>/* Updates */ Google's Advanced flow finally published</comment>
      <origin>45016</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31743" sha1="kixs16vqe89746eo3fagx2r7v3wy523" xml:space="preserve">==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

=== Advanced flow ===
On 19 March 2026, Google finally revealed how its advanced flow program for installing unverified apps is being implemented. Clarifying that this is a one-time process for power users, but was crafted to prevent coerced install of unverified apps.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=19 Mar 2026 |title=Android developer verification: Balancing openness and choice with safety |url=https://android-developers.googleblog.com/2026/03/android-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260319202706/android-developers.googleblog.com/2026/03/android-developer-verification.html |archive-date=19 March 2026}}&lt;/ref&gt;

* '''Enable developer mode in system settings'''
* '''Confirm you aren't being coached'''
* '''Restart your phone and reauthenticate'''
* '''Come back after the protective waiting period and verify''' '''-''' One-time, one-day wait
* '''Install apps''' '''-''' option of enabling for 7 days or indefinitely 

Whether developer mode need to be left on after enabling unverified apps, potentially preventing critical banking apps from functioning is not clarified.

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Forced account]]
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>kixs16vqe89746eo3fagx2r7v3wy523</sha1>
    </revision>
    <revision>
      <id>45152</id>
      <parentid>45016</parentid>
      <timestamp>2026-03-20T05:06:04Z</timestamp>
      <contributor>
        <ip>103.27.10.78</ip>
      </contributor>
      <comment>Undo revision [[Special:Diff/44186|44186]] by [[Special:Contributions/188.236.230.240|188.236.230.240]] ([[User talk:188.236.230.240|talk]])</comment>
      <origin>45152</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="36624" sha1="l5kgz4fn4ncojophzlr1kg5omi0i2pb" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=d89e2e8dc28a93bcdc3984265466242a4493fbaf
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |website=Android Developers}}&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

=== Advanced flow ===
On 19 March 2026, Google finally revealed how its advanced flow program for installing unverified apps is being implemented. Clarifying that this is a one-time process for power users, but was crafted to prevent coerced install of unverified apps.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=19 Mar 2026 |title=Android developer verification: Balancing openness and choice with safety |url=https://android-developers.googleblog.com/2026/03/android-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260319202706/android-developers.googleblog.com/2026/03/android-developer-verification.html |archive-date=19 March 2026}}&lt;/ref&gt;

* '''Enable developer mode in system settings'''
* '''Confirm you aren't being coached'''
* '''Restart your phone and reauthenticate'''
* '''Come back after the protective waiting period and verify''' '''-''' One-time, one-day wait
* '''Install apps''' '''-''' option of enabling for 7 days or indefinitely 

Whether developer mode need to be left on after enabling unverified apps, potentially preventing critical banking apps from functioning is not clarified.

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Forced account]]
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>l5kgz4fn4ncojophzlr1kg5omi0i2pb</sha1>
    </revision>
    <revision>
      <id>45185</id>
      <parentid>45152</parentid>
      <timestamp>2026-03-20T12:50:41Z</timestamp>
      <contributor>
        <ip>103.27.10.71</ip>
      </contributor>
      <comment>/* Advanced flow */ more info</comment>
      <origin>45185</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="37370" sha1="abbl440xbzmojv35aqo0hp5wv9422ws" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=d89e2e8dc28a93bcdc3984265466242a4493fbaf
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |website=Android Developers}}&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

===Advanced flow===
On 19 March 2026, Google finally revealed how its advanced flow program for installing unverified apps is being implemented. Google mentions that this is a one-time process for power users, but was crafted to prevent coerced install of unverified apps.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=19 Mar 2026 |title=Android developer verification: Balancing openness and choice with safety |url=https://android-developers.googleblog.com/2026/03/android-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260319202706/android-developers.googleblog.com/2026/03/android-developer-verification.html |archive-date=19 March 2026}}&lt;/ref&gt;

*'''Enable developer mode in system settings'''
*'''Confirm you aren't being coached'''
*'''Restart your phone and reauthenticate'''
*'''Come back after the protective waiting period and verify''' '''-''' One-time, one-day wait
*'''Install apps''' '''-''' option of enabling for 7 days or indefinitely

Since advanced flow is delivered through Google Play Services and not through Android OS, Google can modify, restrict, or remove it at any time without an OS update and without any user consent. Organizations such as keep android open movement continue to hold the position against the program because of this aspect. Since the implementation has not appeared in dev, beta or canary builds of android yet, Google is prompting the community to accept a product announcement as a functional safeguard five months before the mandate takes effect.

Preventing critical banking apps from functioning due to enabled state of developer mode also makes installing unverified applications unfeasible to many users which majorly affects the rapidly growing FOSS android community and forces developer verification as well as payment of verification fee to Google, only to operate under limitations Google grants.

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Forced account]]
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>abbl440xbzmojv35aqo0hp5wv9422ws</sha1>
    </revision>
    <revision>
      <id>46628</id>
      <parentid>45185</parentid>
      <timestamp>2026-03-22T04:34:31Z</timestamp>
      <contributor>
        <username>SJH111</username>
        <id>9018</id>
      </contributor>
      <comment>Add Jean-Héon source about Privacy and safety concerns</comment>
      <origin>46628</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="37836" sha1="pjxjm08u7nqak5194gseywv2yxsczf5" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=d89e2e8dc28a93bcdc3984265466242a4493fbaf
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |website=Android Developers}}&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

===Advanced flow===
On 19 March 2026, Google finally revealed how its advanced flow program for installing unverified apps is being implemented. Google mentions that this is a one-time process for power users, but was crafted to prevent coerced install of unverified apps.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=19 Mar 2026 |title=Android developer verification: Balancing openness and choice with safety |url=https://android-developers.googleblog.com/2026/03/android-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260319202706/android-developers.googleblog.com/2026/03/android-developer-verification.html |archive-date=19 March 2026}}&lt;/ref&gt;

*'''Enable developer mode in system settings'''
*'''Confirm you aren't being coached'''
*'''Restart your phone and reauthenticate'''
*'''Come back after the protective waiting period and verify''' '''-''' One-time, one-day wait
*'''Install apps''' '''-''' option of enabling for 7 days or indefinitely

Since advanced flow is delivered through Google Play Services and not through Android OS, Google can modify, restrict, or remove it at any time without an OS update and without any user consent. Organizations such as keep android open movement continue to hold the position against the program because of this aspect. Since the implementation has not appeared in dev, beta or canary builds of android yet, Google is prompting the community to accept a product announcement as a functional safeguard five months before the mandate takes effect.

Preventing critical banking apps from functioning due to enabled state of developer mode also makes installing unverified applications unfeasible to many users which majorly affects the rapidly growing FOSS android community and forces developer verification as well as payment of verification fee to Google, only to operate under limitations Google grants.

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;
*Jean-Héon points out that mandatory developer registration puts users at risk by pushing them to use dangerous workarounds to install unverified APKs of their choice. It also puts developers at risk by exposing them to data leaks and identity theft. Jean-Héon advocates for a solution based on the device's antivirus software. &lt;ref&gt;{{Cite web |title= |url=https://sites.google.com/view/jean-honmctm/communiqu%C3%A9press-releases/keep-android-open-english}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Forced account]]
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>pjxjm08u7nqak5194gseywv2yxsczf5</sha1>
    </revision>
    <revision>
      <id>46686</id>
      <parentid>46628</parentid>
      <timestamp>2026-03-22T12:47:41Z</timestamp>
      <contributor>
        <ip>2001:4BC9:905:4F9D:2205:B7FF:FE00:E700</ip>
      </contributor>
      <comment>/* References */ add title</comment>
      <origin>46686</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="37962" sha1="90cp55flkjjquft1ktm3eed2x08pcu6" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=d89e2e8dc28a93bcdc3984265466242a4493fbaf
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |website=Android Developers}}&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

===Advanced flow===
On 19 March 2026, Google finally revealed how its advanced flow program for installing unverified apps is being implemented. Google mentions that this is a one-time process for power users, but was crafted to prevent coerced install of unverified apps.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=19 Mar 2026 |title=Android developer verification: Balancing openness and choice with safety |url=https://android-developers.googleblog.com/2026/03/android-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260319202706/android-developers.googleblog.com/2026/03/android-developer-verification.html |archive-date=19 March 2026}}&lt;/ref&gt;

*'''Enable developer mode in system settings'''
*'''Confirm you aren't being coached'''
*'''Restart your phone and reauthenticate'''
*'''Come back after the protective waiting period and verify''' '''-''' One-time, one-day wait
*'''Install apps''' '''-''' option of enabling for 7 days or indefinitely

Since advanced flow is delivered through Google Play Services and not through Android OS, Google can modify, restrict, or remove it at any time without an OS update and without any user consent. Organizations such as keep android open movement continue to hold the position against the program because of this aspect. Since the implementation has not appeared in dev, beta or canary builds of android yet, Google is prompting the community to accept a product announcement as a functional safeguard five months before the mandate takes effect.

Preventing critical banking apps from functioning due to enabled state of developer mode also makes installing unverified applications unfeasible to many users which majorly affects the rapidly growing FOSS android community and forces developer verification as well as payment of verification fee to Google, only to operate under limitations Google grants.

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;
*Jean-Héon points out that mandatory developer registration puts users at risk by pushing them to use dangerous workarounds to install unverified APKs of their choice. It also puts developers at risk by exposing them to data leaks and identity theft. Jean-Héon advocates for a solution based on the device's antivirus software. &lt;ref&gt;{{Cite web |title=Google restricts the installation of third-party APKs on Android: what this means for Jean-Héon™. (Updated March 21, 2026). |url=https://sites.google.com/view/jean-honmctm/communiqu%C3%A9press-releases/keep-android-open-english}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Forced account]]
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>90cp55flkjjquft1ktm3eed2x08pcu6</sha1>
    </revision>
    <revision>
      <id>46697</id>
      <parentid>46686</parentid>
      <timestamp>2026-03-22T16:13:45Z</timestamp>
      <contributor>
        <username>SJH111</username>
        <id>9018</id>
      </contributor>
      <comment>Modifing Jean-Héon arguement in the Privacy and safety concerns.  Adding Jean-Héon argument in the Criticism section.</comment>
      <origin>46697</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="38206" sha1="1meqsokrh2s32s0kiyn2do82wumyzi0" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=d89e2e8dc28a93bcdc3984265466242a4493fbaf
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |website=Android Developers}}&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

===Advanced flow===
On 19 March 2026, Google finally revealed how its advanced flow program for installing unverified apps is being implemented. Google mentions that this is a one-time process for power users, but was crafted to prevent coerced install of unverified apps.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=19 Mar 2026 |title=Android developer verification: Balancing openness and choice with safety |url=https://android-developers.googleblog.com/2026/03/android-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260319202706/android-developers.googleblog.com/2026/03/android-developer-verification.html |archive-date=19 March 2026}}&lt;/ref&gt;

*'''Enable developer mode in system settings'''
*'''Confirm you aren't being coached'''
*'''Restart your phone and reauthenticate'''
*'''Come back after the protective waiting period and verify''' '''-''' One-time, one-day wait
*'''Install apps''' '''-''' option of enabling for 7 days or indefinitely

Since advanced flow is delivered through Google Play Services and not through Android OS, Google can modify, restrict, or remove it at any time without an OS update and without any user consent. Organizations such as keep android open movement continue to hold the position against the program because of this aspect. Since the implementation has not appeared in dev, beta or canary builds of android yet, Google is prompting the community to accept a product announcement as a functional safeguard five months before the mandate takes effect.

Preventing critical banking apps from functioning due to enabled state of developer mode also makes installing unverified applications unfeasible to many users which majorly affects the rapidly growing FOSS android community and forces developer verification as well as payment of verification fee to Google, only to operate under limitations Google grants.

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;
*Jean-Héon points out that mandatory developer registration puts users at risk by pushing them to use dangerous workarounds to install unverified APKs of their choice and also puts developers at risk by exposing them to data leaks and identity theft. Jean-Héon advocates for a solution based on the device's antivirus software. &lt;ref&gt;{{Cite web |title=Google restricts the installation of third-party APKs on Android: what this means for Jean-Héon™. (Updated March 21, 2026). |url=https://sites.google.com/view/jean-honmctm/communiqu%C3%A9press-releases/keep-android-open-english}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;
*According to Jean-Héon “Android Developer Verification is an absurdity for the free mobile ecosystem.”&lt;ref&gt;{{Cite web |title= |url=https://sites.google.com/view/jean-honmctm/communiqu%C3%A9press-releases/keep-android-open-english}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Forced account]]
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>1meqsokrh2s32s0kiyn2do82wumyzi0</sha1>
    </revision>
    <revision>
      <id>46698</id>
      <parentid>46697</parentid>
      <timestamp>2026-03-22T16:23:15Z</timestamp>
      <contributor>
        <username>SJH111</username>
        <id>9018</id>
      </contributor>
      <comment>Added:The vast majority of Android devices sold outside of China in the section Affected devices</comment>
      <origin>46698</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="38266" sha1="siyl684fe803mku0dilrz1t8q3tuq29" xml:space="preserve">{{IncidentCargo
|Company=Google
|StartDate=2025-08-25
|EndDate=d89e2e8dc28a93bcdc3984265466242a4493fbaf
|Status=Active
|ProductLine=Google-certified Android devices
|Product=Android
|ArticleType=Service
|Type=Anticompetitive Behavior, Digital restrictions, Privacy
|Description=A planned restriction that forces developers to submit their identity to Google and pay a fee for their apps to be installable onto Android devices.
}}
On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |website=Android Developers}}&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles.&lt;ref&gt;https://source.android.com/about/philosophy.html ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archive]) Philosophy and Goals &amp;#x7C; Android Open Source] (2012) ([http://web.archive.org/web/20140621023054/http://source.android.com/about/philosophy.html Archived])&lt;/ref&gt; It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no [[data lock-in]] (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.&lt;ref&gt;[https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Apple Is Censoring its App Store for China] - Tech Transparency Projects ([http://web.archive.org/web/20251124220615/https://www.techtransparencyproject.org/articles/apple-censoring-its-app-store-china Archived])&lt;/ref&gt;

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet.&lt;ref&gt;[https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl The future of Iran’s internet connectivity is still bleak, even as weeks-long blackout begins to lift &amp;#x7C; CNN] ([https://web.archive.org/web/20260223025239/https://www.cnn.com/2026/01/30/middleeast/iran-internet-blackout-censorship-intl Archived])&lt;/ref&gt; 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications.&lt;ref&gt;[https://karl-voit.at/cloud/ You Can't Control Your Data in the Cloud] - Karl Voit ([http://web.archive.org/web/20260202071758/https://karl-voit.at/cloud/ Archived])&lt;/ref&gt; Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with [[#Limited_distribution|student accounts]]. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services.&lt;ref&gt;[https://gcemetery.co/ The Google Cemetery - Dead Google products] ([http://web.archive.org/web/20260221111719/https://gcemetery.co/ Archived])&lt;/ref&gt;&lt;ref&gt;[https://killedbygoogle.com/ Google Graveyard - Killed by Google] ([http://web.archive.org/web/20260221152454/https://killedbygoogle.com/ Archived])&lt;/ref&gt; If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

===Advanced flow===
On 19 March 2026, Google finally revealed how its advanced flow program for installing unverified apps is being implemented. Google mentions that this is a one-time process for power users, but was crafted to prevent coerced install of unverified apps.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=19 Mar 2026 |title=Android developer verification: Balancing openness and choice with safety |url=https://android-developers.googleblog.com/2026/03/android-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260319202706/android-developers.googleblog.com/2026/03/android-developer-verification.html |archive-date=19 March 2026}}&lt;/ref&gt;

*'''Enable developer mode in system settings'''
*'''Confirm you aren't being coached'''
*'''Restart your phone and reauthenticate'''
*'''Come back after the protective waiting period and verify''' '''-''' One-time, one-day wait
*'''Install apps''' '''-''' option of enabling for 7 days or indefinitely

Since advanced flow is delivered through Google Play Services and not through Android OS, Google can modify, restrict, or remove it at any time without an OS update and without any user consent. Organizations such as keep android open movement continue to hold the position against the program because of this aspect. Since the implementation has not appeared in dev, beta or canary builds of android yet, Google is prompting the community to accept a product announcement as a functional safeguard five months before the mandate takes effect.

Preventing critical banking apps from functioning due to enabled state of developer mode also makes installing unverified applications unfeasible to many users which majorly affects the rapidly growing FOSS android community and forces developer verification as well as payment of verification fee to Google, only to operate under limitations Google grants.

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel
*The vast majority of Android devices sold outside of China

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;
*Jean-Héon points out that mandatory developer registration puts users at risk by pushing them to use dangerous workarounds to install unverified APKs of their choice and also puts developers at risk by exposing them to data leaks and identity theft. Jean-Héon advocates for a solution based on the device's antivirus software. &lt;ref&gt;{{Cite web |title=Google restricts the installation of third-party APKs on Android: what this means for Jean-Héon™. (Updated March 21, 2026). |url=https://sites.google.com/view/jean-honmctm/communiqu%C3%A9press-releases/keep-android-open-english}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;
*According to Jean-Héon “Android Developer Verification is an absurdity for the free mobile ecosystem.”&lt;ref&gt;{{Cite web |title= |url=https://sites.google.com/view/jean-honmctm/communiqu%C3%A9press-releases/keep-android-open-english}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Forced account]]
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>siyl684fe803mku0dilrz1t8q3tuq29</sha1>
    </revision>
    <revision>
      <id>46756</id>
      <parentid>46698</parentid>
      <timestamp>2026-03-23T22:48:54Z</timestamp>
      <contributor>
        <ip>188.236.161.17</ip>
      </contributor>
      <comment>Fixed typo</comment>
      <origin>46756</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="36343" sha1="8sfx55g22nh25alwsop4xm3q8sizy2m" xml:space="preserve">On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register and verify their real-life identity through the Developer Verification program and be approved by Google before their apps can be installed on Android devices. This requirement extends to '''''all''''' installation methods including "[[sideloading]]", third-party app repositories like [[F-Droid]], and direct APK installations. Google stated that this change "keeps the ecosystem open".&lt;ref&gt;{{Cite web |last= |date=Aug 2025 |title=Elevating Android's security to keep it open and safe |url=https://developer.android.com/developer-verification |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://developer.android.com/developer-verification |archive-date=2025-08-25 |website=Android Developers}}&lt;/ref&gt;

This is a giant shift from Android's traditionally open ecosystem and an abandonment of Android's founding principles. It renders all existing APK files created throughout the years useless, and gives Google the ability to censor apps they dislike, such as those that can create permanent local backups of YouTube videos outside of Google's ecosystem with no data lock-in (a popular example being TubeMate), and lets them terminate developers out of spite for reasons unrelated to their apps (such as holding political views Google disagrees with), in addition to giving governments the ability to order Google to censor unwanted apps, similar to what already happened with Apple in China.

It also prevents new Android applications from being developed offline with no Internet connection or Google account, given that every package name has to be registered in the developer console. This can prevent even verified developers from creating apps in countries where governments intermittently turn off Internet access, block access to Google services, or selectively block individuals from accessing the Internet. 

Individuals who lose access to their Google accounts (for example, as a result of losing an authentication factor) would no longer be able register new applications. Unlimited offline distribution can also become a thing of the past. Google can impose arbitrary installation quotas, meaning limit the number of installations, like they are planning to do with student accounts. In the future, Google can also stop accepting submissions for older Android versions altogether, forcing people to purchase new devices to run software that could technically run on their existing device.

As with any Google service, there exists a possibility that it will shut down entirely, given that Google has a long history of launching and shutting down experimental services. If Google shut down the Android Developer Console, no one could develop new Android application anymore, for any device sold with this verification requirement built in.

==Take action, make our voice heard==
Direct link to the useful resources provided by the [https://techlore.tech Techlore]  https://keepandroidopen.org/

===Open Letter to Google===
[https://keepandroidopen.org/open-letter/ The Open Letter] signed by most of the privacy advocates and organizations.

The keep android open website includes the following resources:

*ways to contact national regulators
*open letter and petitions
*f-droid additional sources
*editorial blogs and press reactions
*public discussions

==Background==
Android has historically allowed users to freely install applications from any source through APK files (sometimes called [[sideloading]]). This openness differentiated Android from competitors like iOS. It enabled alternative app repositories, including open-source repositories like [[F-Droid]], &amp; direct developer-to-user distribution, offline installation with no Internet connection and Google account required, installation of applications not available in the Play Store (such as ''Flappy Bird'', after it was taken down by its developer, or ''TubeMate'', which Google does not allow on the Play Store), and installation of earlier versions (such as non-adware versions of ''ES File Explorer'').

The only technical requirements were that applications follow Android's technical guidelines for functionality &amp; be signed with any certificate to maintain a chain of trust during updates.

This openness has been a defining characteristic of Android since its inception, supporting many different use cases from enterprise deployments to privacy-focused distributions. Google has defended this approach in antitrust proceedings, with Google's lawyers arguing in the [[Epic Games]] case that "Android and Google Play provide more choice and openness than any other major mobile platform"&lt;ref&gt;{{Cite web |date=2023-12-11 |title=Fortnite maker Epic Games wins its antitrust fight against Google |url=https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |access-date=2025-08-29 |website=TechCrunch |url-status=live |archive-url=http://web.archive.org/web/20251126195055/https://techcrunch.com/2023/12/11/epic-games-google-antitrust-win/ |archive-date=26 Nov 2025}}&lt;/ref&gt; &amp; that the company's app store practices were "part of its fierce competition with Apple".&lt;ref&gt;{{Cite web |date=2023-12-12 |title=Epic Games wins antitrust lawsuit against Google |url=https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |access-date=2025-08-29 |website=The Washington Post |url-status=live |archive-url=http://web.archive.org/web/20250723224500/https://www.washingtonpost.com/technology/2023/12/11/epic-google-trial-verdict/ |archive-date=23 Jul 2025}}&lt;/ref&gt;

==Announcement and rationale==
Google announced the Developer Verification requirements on August 25th, 2025, through the Android Developers Blog.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Android Developers Blog: A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |archive-url=https://web.archive.org/web/20250825180832/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt; According to Suzanne Frey, VP of Product, Trust &amp; Growth for Android, the system is designed to combat malicious actors who "''hide behind anonymity to harm users by impersonating developers and using their brand image to create convincing fake apps."''

Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play".''&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google will require developer verification to install Android apps, including sideloading |url=https://9to5google.com/2025/08/25/android-apps-developer-verification/ |website=9to5Google |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211442/https://9to5google.com/2025/08/25/android-apps-developer-verification/ |archive-date=19 Jan 2026}}&lt;/ref&gt; The company framed the verification as ''"an ID check at the airport, which confirms a traveler's identity but is separate from the security screening of their bags".''

===Implementation timeline===
The implementation will be conducted in global rollout phases:&lt;ref name=":0"&gt;{{Cite web |date=2025-08-25 |title=Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/android-developer-console |url-status=live |archive-url=https://web.archive.org/web/20250825204008/https://developer.android.com/developer-verification/guides/android-developer-console |archive-date=2025-08-25 |access-date=2025-08-25}}&lt;/ref&gt;

*'''October 2025''': Early access opens for invited developers
*'''March 2026''': Open to all developers
*'''September 2026''': Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
*'''2027 and beyond''': Global rollout continues

Key implementation details:
*No grandfather clauses for existing apps or developers
*[[wikipedia:Google_Play|Play Store]] developers likely already meet requirements through 2023's D-U-N-S implementation
*Organizations requiring D-U-N-S numbers should begin the process 28 days before deadlines
*Developers can initiate verification 60 days before enforcement
*90-day deadline extensions available for developers needing additional time
*After deadlines, users encounter system-level blocks with no override option when attempting to install unverified apps

===Updates===
Google announced that it is developing an 'advanced flow' for 'experienced users' to be able to install apps from unverified developers and described the process as 'maximally obscure and high-friction'.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=12 Nov 2025 |title=Android developer verification: Early access starts now as we continue to build with your feedback |url=https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html}} ([http://web.archive.org/web/20260221030624/https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html Archived])&lt;/ref&gt;&lt;ref&gt;{{Cite news |last=Schoon |first=Ben |date=19 Jan 2026 |title=Google calls Android’s new sideloading flow ‘high friction’ |url=https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/}} ([http://web.archive.org/web/20260120014243/https://9to5google.com/2026/01/19/google-calls-androids-new-sideloading-flow-high-friction/ Archived])&lt;/ref&gt; Free and open software distributor, F-Droid, clarified in a blog post that the android developer program remains to a credible threat to open source ecosystem on android and added a banner on the website as well as app linking to https://keepandroidopen.org/, for informing the dangers and recommending users to voice their concerns to relevant authority.&lt;ref&gt;{{Cite web |date=20 Feb 2026 |title=Keep Android Open - TWIF curated on Friday, 20 Feb 2026, Week 8 - f-droid.org |url=https://f-droid.org/en/2026/02/20/twif.html}} ([https://web.archive.org/web/20260223025319/https://f-droid.org/en/2026/02/20/twif.html Archived])&lt;/ref&gt; 

In February 24 2026, the KeepAndroidOpen movement published an open letter to google signed by various free and open source software organizations, digital rights groups and developer communities accessible under https://keepandroidopen.org/open-letter/.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter to Google regarding Mandatory Developer Registration for Android App Distribution |url=https://keepandroidopen.org/open-letter/ |url-status=live |archive-url=https://web.archive.org/web/20260224172459/https://keepandroidopen.org/open-letter/ |archive-date=24 Feb 2026}}&lt;/ref&gt;  The letter criticizes the need for google to gatekeep software beyond its own distribution platform, centralization of power having implications to privacy, censorship and surveillance especially with Google's historically opaque decision-making and review approach, imposition of barriers to entry for developers in various scenarios, anti-competitive implications and regulatory concerns. F-Droid was among the various organizations to sign the letter that in a blog post also stands opposed to signing up for developer verification that will begin the process in March 2026, recommending to developers to oppose the move by refusing to sign up as well.&lt;ref&gt;{{Cite web |date=24 Feb 2026 |title=An Open Letter Opposing Android Developer Verification |url=https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260224172628/https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html |archive-date=24 Feb 2026}}&lt;/ref&gt;

On 4 March 2026, as part of changes following Google vs. Epic store Lawsuit, Google announced that it is allowing registered app stores to be published on google play platform if they "meet certain quality and safety benchmarks", which would otherwise be subject to same restrictions as those for other 'sideloaded' app.&lt;ref&gt;{{Cite web |last=Samat |first=Sameer |date=4 Mar 2026 |title=A new era for choice and openness |url=https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |url-status=live |archive-url=https://web.archive.org/web/20260305062940/android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html |archive-date=5 Mar 2026}}&lt;/ref&gt; Notably as part of the settlement, Epic games signed away its rights to sue Google over anything related as covered in the term sheet, until September 2032.&lt;ref&gt;{{Cite news |last=Hollister |first=Sean |date=5 Mar 2026 |title=Tim Sweeney signed away his right to criticize Google’s app store until 2032 |url=https://www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |url-status=live |archive-url=https://web.archive.org/web/20260305000517/www.theverge.com/news/889595/tim-sweeney-signed-away-his-right-to-criticize-google-until-2032 |archive-date=5 Mar 2026}}&lt;/ref&gt;

===Advanced flow===
On 19 March 2026, Google finally revealed how its advanced flow program for installing unverified apps is being implemented. Google mentions that this is a one-time process for power users, but was crafted to prevent coerced install of unverified apps.&lt;ref&gt;{{Cite web |last=Forsythe |first=Matthew |date=19 Mar 2026 |title=Android developer verification: Balancing openness and choice with safety |url=https://android-developers.googleblog.com/2026/03/android-developer-verification.html |url-status=live |archive-url=https://web.archive.org/web/20260319202706/android-developers.googleblog.com/2026/03/android-developer-verification.html |archive-date=19 March 2026}}&lt;/ref&gt;

*'''Enable developer mode in system settings'''
*'''Confirm you aren't being coached'''
*'''Restart your phone and reauthenticate'''
*'''Come back after the protective waiting period and verify''' '''-''' One-time, one-day wait
*'''Install apps''' '''-''' option of enabling for 7 days or indefinitely

Since advanced flow is delivered through Google Play Services and not through Android OS, Google can modify, restrict, or remove it at any time without an OS update and without any user consent. Organizations such as keep android open movement continue to hold the position against the program because of this aspect. Since the implementation has not appeared in dev, beta or canary builds of android yet, Google is prompting the community to accept a product announcement as a functional safeguard five months before the mandate takes effect.

Preventing critical banking apps from functioning due to enabled state of developer mode also makes installing unverified applications unfeasible to many users which majorly affects the rapidly growing FOSS android community and forces developer verification as well as payment of verification fee to Google, only to operate under limitations Google grants.

==Technical implementation==

===Distribution types===
The Developer Verification system creates two tiers of developer accounts:&lt;ref name=":0" /&gt;

====Limited distribution====
*Allows for distribution on up to 20 devices&lt;ref&gt;{{Cite web |date= |title=Android Developer Console: Account creation form |url=https://get.google.com/adc-early-access/u/0/onboarding |access-date=2025-12-19 |website=Android Developer Console}} ([https://web.archive.org/web/20260223010845/https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;dsh=S-116450265%3A1771808922850823&amp;followup=https%3A%2F%2Fget.google.com%2Fadc-early-access%2Fu%2F0%2Fonboarding&amp;ifkv=ASfE1-qms7IwZjbAdjvxowYFy5Kb9DL9vPDu06W9LMpkaBqy285wVRrX7HSp5xXdFaxXqzHM9tztDA&amp;osid=1&amp;passive=1209600&amp;flowName=WebLiteSignIn&amp;flowEntry=ServiceLogin Archived])&lt;/ref&gt;
*Intended for ''"students, hobbyists, and other personal use"''
*Free registration
*Identity verification requirements unclear

====Full distribution====
*No limits on app numbers or installations
*Intended for ''"organizations and professional developers with wide distribution"''
*Requires a one-time $25 fee
*Requires complete identity verification including:
**Government-issued photo ID
**Proof of address
**Private email
**Phone number
**For organizations: 
***Website
***D-U-N-S number (can take up to 28 days to obtain)

===Package name registration===
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity &amp; app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority.&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Updates to Play Console for Android developer verification: A first look |url=https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |website=Android Developers |access-date=2025-09-01 |url-status=live |archive-url=http://web.archive.org/web/20260128020558/https://developer.android.com/developer-verification/assets/pdfs/updates-to-play-console-for-android-developer-verification.pdf |archive-date=28 Jan 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Resources {{!}} Android developer verification {{!}} Android Developers |url=https://developer.android.com/developer-verification/guides/resources |website=Android Developers |access-date=2025-08-25}} ([http://web.archive.org/web/20251123194919/https://developer.android.com/developer-verification/guides/resources Archived])&lt;/ref&gt;

===Affected devices===
The requirements apply to all ''"[https://www.android.com/certified/partners/ Google-certified Android devices]"'' which includes:
*Devices with Google Play Store
*Devices with [[Google Mobile Services]] (GMS)
*Devices with Play Protect
*All mainstream Android devices from manufacturers including Samsung, Xiaomi, Motorola, OnePlus, and Google Pixel
*The vast majority of Android devices sold outside of China

Custom ROMs without Google services &amp; uncertified devices are not affected by these restrictions.

==Developer response==

===Technical concerns===
Prominent Android developer Mark Murphy (CommonsWare) raised several technical concerns:&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Uncomfortable Questions About Android Developer Verification |url=https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |website=CommonsWare |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251121201157/https://commonsware.com/blog/2025/08/26/uncomfortable-questions-android-developer-verification.html |archive-date=21 Nov 2025}}&lt;/ref&gt;
*Debug keystore handling for development workflows remains unaddressed
*Sample code from Android development books would become unusable as "at most one person on the entire planet" could register each package name
*Beta testing workflows using different package names face complications
*Questions whether "it will no longer be possible to test apps under development on Google-certified production hardware" after 2027

===Privacy and safety concerns===
Developers expressed significant privacy concerns:
*Murphy cited the ICEBlock app developer who faced federal prosecution threats after identity disclosure, with his wife being fired from a DOJ job
*EFF, Electronic Frontier Foundation, criticized risks of centralization in censorship as well as surveillance capability retained by Google&lt;ref&gt;{{Cite web |last=McSherry |first=Corynne |date=2025-11-03 |title=Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship |url=https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |url-status=live |archive-url=https://web.archive.org/web/20251111101548/https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship |archive-date=2025-11-11}}&lt;/ref&gt;
*Google's privacy policy allows sharing developer information with ''"trusted businesses or persons"'' without clear restrictions&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*Open source developers fear harassment and doxxing after forced identity disclosure
*F-Droid mentions that play store verification is proven to be ineffective at combating malware due to repeated instances of malware distributed through play store&lt;ref&gt;{{Cite web |last=Arntz |first=Pieter |date=2025-09-17 |title=224 malicious apps removed from the Google Play Store after ad fraud campaign discovered |url=https://www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |url-status=live |archive-url=https://web.archive.org/web/20251005173848/www.malwarebytes.com/blog/news/2025/09/224-malicious-apps-removed-from-the-google-play-store-after-ad-fraud-campaign-discovered |archive-date=2025-10-05 |website=malwarebytes}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Thompson |first=Lain |date=2025-08-26 |title=Malware-ridden apps made it into Google's Play Store, scored 19 million downloads |url=https://www.theregister.com/2025/08/26/apps_android_malware/ |url-status=live |archive-url=https://web.archive.org/web/20251005173850/www.theregister.com/2025/08/26/apps_android_malware/ |archive-date=2025-10-05 |website=The Register}}&lt;/ref&gt;
*Jean-Héon points out that mandatory developer registration puts users at risk by pushing them to use dangerous workarounds to install unverified APKs of their choice and also puts developers at risk by exposing them to data leaks and identity theft. Jean-Héon advocates for a solution based on the device's antivirus software. &lt;ref&gt;{{Cite web |title=Google restricts the installation of third-party APKs on Android: what this means for Jean-Héon™. (Updated March 21, 2026). |url=https://sites.google.com/view/jean-honmctm/communiqu%C3%A9press-releases/keep-android-open-english}}&lt;/ref&gt;

===Open source community impact===
The F-Droid community reacted strongly, with one forum member stating: "F*** Google. Use GrapheneOS to drop Android... I find this development downright alarming".&lt;ref&gt;{{Cite web |title=FAQ - App Developers {{!}} F-Droid - Free and Open Source Android App Repository |url=https://f-droid.org/en/docs/FAQ_-_App_Developers/ |website=F-Droid |access-date=2025-08-29}} ([http://web.archive.org/web/20260116144646/https://f-droid.org/en/docs/FAQ_-_App_Developers/ Archived])&lt;/ref&gt; Specific challenges include:
*F-Droid builds apps from source with its own signing keys, creating coordination requirements with upstream developers to ensure that the applications distributed are reproducible
*Community estimates suggest 85% of F-Droid apps could be "stuck in limbo" due to package ID conflicts
*Some developers announced via [https://github.com/woheller69/FreeDroidWarn FreeDroidWarn] that their apps "will no longer work on certified Android devices after that time"
*Open source app, Kotatsu, shuts down development citing pressure from Google against sideloading among other threats against its operation.&lt;ref&gt;{{Cite web |title=KotatsuApp/Kotatsu: Manga reader for android |url=https://github.com/KotatsuApp/Kotatsu |url-status=live |archive-url=https://web.archive.org/web/20251105185519/github.com/KotatsuApp/Kotatsu |archive-date=5 Nov 2025 |access-date=16 Nov 2025 |website=Github}}&lt;/ref&gt;

==Consumer and user response==
Google's Q&amp;A page for the announcement received lots of feedback, including:&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Q&amp;A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}&lt;/ref&gt;

*Users highlighting the hypocrisy of enforcing security on sideloaded apps while Google Play distributes apps classified as scamware, malware, and adware
*Confusion over whether users would need to pay $25 to install apps on their own devices
*Concerns about offline device functionality (barcode scanners, kiosks) requiring internet connections for app signing verification
*Comparisons to Windows, where users noted: "I can install an app onto a Windows computer from any source without verification by Microsoft"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google to restrict Android app sideloading to verified devs |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |website=The Register |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}&lt;/ref&gt;
*Users voiced their opinions through community wiki, [https://keepandroidopen.org/ keepandroidopen.org] criticizing it as an anti-consumer move since a software update irrevocably blocks right to install any software and requires developers to seek permission from Google to develop apps. The users also noted that it harms digital sovereignty of nations as well as raising questions on placing critical infrastructure "at the mercy of distant and unaccountable organization"&lt;ref&gt;{{Cite web |date=Aug 2025 |title=Keep Android Open |url=https://keepandroidopen.org/ |url-status=live |archive-url=https://web.archive.org/web/20251109112509/keepandroidopen.org |archive-date=2025-11-09 |website=Keep Android Open}}&lt;/ref&gt;

The Android community produced numerous critical videos,&lt;ref&gt;{{Cite web |last=Mental Outlaw |date=2025-08-29 |title=Google is Locking Down Android |url=https://www.youtube.com/watch?v=L1S0SiBuJN8 |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=L1S0SiBuJN8 |archive-date=16 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=BrenTech |date=2025-08-26 |title=Google Will Soon Block Apps from Unverified Developers! Is This The End of Sideloading on Android? |url=https://www.youtube.com/watch?v=-nCgnXByGrY |access-date=2025-08-29 |website=YouTube |archive-url=https://preservetube.com/watch?v=-nCgnXByGrY |archive-date=23 Feb 2026}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=TechLore |date=2025-08-27 |title=Android Is Becoming iOS: The End of Sideloading? |url=https://www.youtube.com/watch?v=PxGjwtiI8uM |access-date=2025-08-29 |website=YouTube |url-status=live |archive-url=https://preservetube.com/watch?v=PxGjwtiI8uM |archive-date=16 Feb 2026}}&lt;/ref&gt; with titles like "Google is Locking Down Android" and "Android Is Becoming iOS: The End of Sideloading?"


Google quiere dominar el mundo !

==Industry and organizational response==

===Support===
The Developers Alliance stood as the sole organizational voice supporting the change, with co-founder Jake Ward stating it was "a critical step to ensure trust, accountability, and security across the Android ecosystem".&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Developers Alliance Applauds Google's New Android Developer Verification |url=https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-url=https://web.archive.org/web/20251029120724/https://news.devalliance.org/developers-alliance-applauds-googles-new-android-developer-verification/ |archive-date=2025-10-29 |access-date=2025-10-29 |website=Developers Alliance}}&lt;/ref&gt;

Government support emerged from initial rollout regions:
*Brazil's Federation of Banks called it a "significant advancement in protecting users"
*Indonesia's Ministry of Communications praised the "balanced approach that protects users while keeping Android open"
*Thailand's Ministry of Digital Economy described it as a "positive and proactive measure"&lt;ref&gt;{{Cite web |date=2025-08-25 |title=Google to Verify All Android Developers in 4 Countries to Block Malicious Apps |url=https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |website=The Hacker News |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260128015131/https://thehackernews.com/2025/08/google-to-verify-all-android-developers.html |archive-date=28 Jan 2026}}&lt;/ref&gt;

===Criticism===
Technology publications characterized the change as fundamental to Android's nature:
*The Daily Security Review called it "a significant philosophical shift for Android, mirroring Apple's tightly curated ecosystem"
*Cory Doctorow writes that Google is abusing it's duopoly position in mobile ecosystem to lock-in users for monetary profit&lt;ref&gt;{{Cite web |last=Doctorow |first=Cory |date=2025-09-01 |title=Darth Android |url=https://pluralistic.net/2025/09/01/fulu/ |url-status=live |archive-url=https://web.archive.org/web/20251012004854/pluralistic.net/2025/09/01/fulu/ |archive-date=2025-10-12}}&lt;/ref&gt;
*Many news outlets warn that the ID requirements could end alternative app stores and affirm play store's position as an effective monopoly&lt;ref&gt;{{Cite web |last=Debasish |date=30 Sep 2025 |title=Google’s new developer rules could threaten sideloading and F-Droid’s future |url=https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |url-status=live |archive-url=https://web.archive.org/web/20251102075559/www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ |archive-date=2 Nov 2025}}&lt;/ref&gt;&lt;ref&gt;{{Cite web |last=Mous |first=Anton |date=30 Sep 2025 |title=Google’s developer registration ‘decree’ means the end for alternative app stores |url=https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |url-status=live |archive-url=https://web.archive.org/web/20251111111050/https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ |archive-date=11 Nov 2025}}&lt;/ref&gt;
*Afam Onyimadu writes for makeuseof, that the move is an overreach of google's position when programs such as Play Protect already exist, calling it "security theatre"&lt;ref&gt;{{Cite web |last=Onyimadu |first=Afam |date=11 Oct 2025 |title=Android’s sideloading limits are its most anti-consumer move yet |url=https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |url-status=live |archive-url=https://web.archive.org/web/20251012005122/www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ |archive-date=12 Oct 2025}}&lt;/ref&gt;
*It's FOSS warned "this could turn Google into the effective gatekeeper for all apps on 'certified' Android devices"&lt;ref&gt;{{Cite web |date=2025-08-29 |title=Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy |url=https://news.itsfoss.com/new-android-sideloading-rules/ |website=It's FOSS |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251107074008/https://news.itsfoss.com/new-android-sideloading-rules/ |archive-date=7 Nov 2025}}&lt;/ref&gt;
*OSnews criticized it as "the death of our digital freedoms"
*Hackaday noted the timing "coincides with Google's court-mandated opening of Android following Epic Games' antitrust victory"&lt;ref&gt;{{Cite web |date=2025-08-26 |title=Google Will Require Developer Verification Even For Sideloading |url=https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |website=Hackaday |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260203082923/https://hackaday.com/2025/08/26/google-will-require-developer-verification-even-for-sideloading/ |archive-date=3 Feb 2026}}&lt;/ref&gt;
*According to Jean-Héon “Android Developer Verification is an absurdity for the free mobile ecosystem.”&lt;ref&gt;{{Cite web |title= |url=https://sites.google.com/view/jean-honmctm/communiqu%C3%A9press-releases/keep-android-open-english}}&lt;/ref&gt;

==Impact on specific use cases==

===Enterprise and MDM deployments===
NomidMDM advised IT managers to "audit application inventory today" &amp; make sure all line-of-business app developers complete verification before deadlines.&lt;ref&gt;{{Cite web |title=The Core Change: Mandatory Verification for All Android Apps |url=https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |website=NomidMDM |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251209230703/https://www.nomidmdm.com/en/blog/the-core-change-mandatory-verification-for-all-android-apps |archive-date=9 Dec 2025}}&lt;/ref&gt; Affected deployments include:
*Wall-mounted displays
*Classroom broadcasting systems
*Shared device configurations
*Kiosk applications
*Industrial control systems

===Alternative app stores===
F-Droid faces serious challenges with the repository's build-from-source model conflicting with developer verification requirements. Alternative stores must make sure all hosted apps come from verified developers, effectively extending Google's verification to all distribution channels.

===Educational development===
Educational institutions face challenges as well:
*Student projects require individual verification for testing
*Sample code from textbooks becomes unusable without verification
*Classroom demonstrations need verified developer accounts
*Research projects face additional identity disclosure requirements

==Regulatory context==
The announcement arrives during active regulatory scrutiny of Google's platform practices:

===European Union===
The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions.&lt;ref&gt;{{Cite web |date=2025-03-19 |title=Google Search, Play Store falling foul of Digital Markets Act rules, says EU |url=https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |website=TechCrunch |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20251123150559/https://techcrunch.com/2025/03/19/google-search-play-store-falling-foul-of-digital-markets-act-rules-says-eu/ |archive-date=23 Nov 2025}}&lt;/ref&gt; Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services.

===United States===
The timing coincides with court-mandated changes following Epic Games' antitrust victory. The FTC outlined remedy concerns in an August 2024 amicus brief after the jury found Google illegally monopolized app distribution.&lt;ref&gt;{{Cite web |date=2024-08-29 |title=FTC Outlines Remedy Concerns in Amicus Brief After Jury Finds Google Illegally Monopolized App Store |url=https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |website=Federal Trade Commission |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20260116072044/https://www.ftc.gov/news-events/news/press-releases/2024/08/ftc-outlines-remedy-concerns-amicus-brief-after-jury-finds-google-illegally-monopolized-app-store |archive-date=16 Jan 2026}}&lt;/ref&gt;

===United Kingdom===
The UK Competition and Markets Authority continues its Strategic Market Status investigation, with consultation closing on August 20, 2025.&lt;ref&gt;{{Cite web |title=SMS investigation into Google's mobile platform |url=https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |website=GOV.UK |access-date=2025-08-29 |url-status=live |archive-url=http://web.archive.org/web/20250725034936/https://www.gov.uk/cma-cases/sms-investigation-into-googles-mobile-ecosystem |archive-date=25 Jul 2025}}&lt;/ref&gt; No specific response to the verification requirements has been issued.

==See also==
*[[Forced account]]
*[[Digital Markets Act]]
*[[Sideloading]]

==References==
{{reflist}}

[[Category:Android]]</text>
      <sha1>8sfx55g22nh25alwsop4xm3q8sizy2m</sha1>
    </revision>
  </page>
</mediawiki>