Android Developer Verification: Difference between revisions
Add additional reference for 50% install ownership threshold |
|||
(3 intermediate revisions by 3 users not shown) | |||
Line 10: | Line 10: | ||
}} | }} | ||
On August 25th, 2025, Google announced an upcoming application installation restriction on Google-certified Android devices, requiring '''all''' developers to register & 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, & direct APK installations. This is a giant shift from android's traditionally open ecosystem. | On August 25th, 2025, [[Google]] announced an upcoming application installation restriction on Google-certified [[Android]] devices, requiring '''all''' developers to register & 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, & direct APK installations. This is a giant shift from android's traditionally open ecosystem. | ||
==Background== | ==Background== | ||
Android has historically allowed users to freely install applications from any source | 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]], & direct developer-to-user distribution. The only technical requirements were that applications follow Android's technical guidelines for functionality & 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"<ref>{{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}}</ref> & that the company's app store practices were "part of its fierce competition with Apple"<ref>{{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}}</ref>. | 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"<ref>{{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}}</ref> & that the company's app store practices were "part of its fierce competition with Apple"<ref>{{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}}</ref>. | ||
==Announcement and rationale== | ==Announcement and rationale== | ||
Line 21: | Line 21: | ||
Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''<ref>{{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}}</ref>. 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."'' | Google cited security statistics showing ''"over 50 times more malware from internet-sideloaded sources than on apps available through Google Play"''<ref>{{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}}</ref>. 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<ref>{{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}}</ref>: | |||
*'''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== | ==Technical implementation== | ||
Line 43: | Line 59: | ||
===Package name registration=== | ===Package name registration=== | ||
Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity & app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority<ref>{{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- | Developers must register package names before apps can be installed. The system creates a cryptographic link between developer identity & app signing keys. Ownership priority is determined by installation statistics - developers whose signing keys account for over 50% of known installs receive registration priority<ref>{{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}}</ref><ref>{{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}}</ref>. | ||
===Affected devices=== | ===Affected devices=== | ||
The requirements apply to all ''"Google-certified Android 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 Play Store | ||
*Devices with Google Mobile Services (GMS) | *Devices with Google Mobile Services (GMS) | ||
Line 126: | Line 142: | ||
===European Union=== | ===European Union=== | ||
The EU Digital Markets Act investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions<ref>{{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}}</ref>. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services. | The EU [[Digital Markets Act]] investigation issued preliminary findings against Google on March 19, 2025, for self-preferencing and payment system restrictions<ref>{{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}}</ref>. Legal experts note potential conflicts with DMA provisions requiring gatekeepers to permit third-party software installation without the gatekeeper's identification services. | ||
===United States=== | ===United States=== | ||
Line 133: | Line 149: | ||
===United Kingdom=== | ===United Kingdom=== | ||
The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025<ref>{{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}}</ref>, though no specific response to the verification requirements has been issued. | The UK Competition and Markets Authority continues its Strategic Market Status investigation with consultation closing August 20, 2025<ref>{{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}}</ref>, though no specific response to the verification requirements has been issued. | ||
==See also== | ==See also== |