L’agost de 2025, Google va anunciar ↗ que, a partir del setembre de 2026, ja no serà possible desenvolupar aplicacions per a la plataforma Android sense registrar-se prèviament de manera centralitzada amb Google.
Aquest registre implicarà:
- Pagar una taxa a Google
- Acceptar els Termes i Condicions de Google
- Proporcionar una identificació governamental
- Pujar proves de la clau privada de signatura del desenvolupador
- Llistar tots els identificadors d’aplicacions actuals i futurs
Què significa això per als teus drets
➤ Tu, com a consumidor, vas comprar el teu dispositiu Android confiant en la promesa de Google que era una plataforma informàtica oberta i que hi podries executar qualsevol programari que triessis.
En canvi, a partir del setembre de 2026, t’imposaran sense consentiment una actualització del sistema operatiu que bloquejarà irrevocablement aquest dret i et deixarà a mercè del seu criteri sobre quin programari et permeten considerar fiable.
➤ Tu, com a creador, ja no podràs desenvolupar una aplicació i compartir-la directament amb amics, família i comunitat sense demanar abans l’aprovació de Google.
La promesa d’Android -i un avantatge de màrqueting que ha utilitzat per distingir-se de l’iPhone- sempre ha estat que és “obert”. Però Google clarament considera que ja té prou control sobre l’ecosistema Android, juntament amb una captura reguladora suficient, com per poder abandonar aquest principi de manera deliberada i amb total impunitat.
➤ Tu, com a estat, estàs cedint els drets de la teva ciutadania i la teva pròpia sobirania digital a una empresa amb un historial de complir les demandes extrajudicials de règims autoritaris per eliminar aplicacions perfectament legals que simplement no els agraden. El programari crític per al funcionament dels teus negocis i governs quedarà a mercè dels capricis opacs d’una corporació llunyana i no responsable davant de ningú.
Actualització: Google no ha “fet marxa enrere” amb la verificació de desenvolupadors
Malgrat una vaga menció ↗ d’un possible “flux avançat” que potser eventualment permeti que “usuaris experimentats acceptin els riscos d’instal·lar programari que no està verificat”, la descripció del programa ↗ de Google continua afirmant clarament que:
A partir del setembre de 2026, Android exigirà que totes les aplicacions estiguin registrades per desenvolupadors verificats per poder instal·lar-se en dispositius Android certificats
Fins que no demostrin amb proves que serà possible evitar el procés de verificació sense fricció indeguda, hem de creure el que diu la seva pàgina oficial: que totes les aplicacions de desenvolupadors no registrats seran bloquejades quan entri en vigor aquest tancament.
Com pots ajudar
Desenvolupadors: Resistiu i rebutgeu-ho
Si ets desenvolupador d’aplicacions, no t’hi inscriguis al programa d’accés anticipat, no facis la verificació d’identitat ni acceptis una invitació a la Android Developer Console. Respon (educadament) a qualsevol invitació amb una llista de les teves preocupacions i objeccions.
—— Només a través de l’acatament dels desenvolupadors el seu pla de presa de control pot tenir èxit. ——
Desencoratja altres desenvolupadors d’aplicacions i organitzacions perquè no s’hi adhereixin. Utilitza fòrums comunitaris, xarxes socials i entrades de blog per difondre el missatge. Inclou la biblioteca FreeDroidWarn ↗ al teu codi per informar els usuaris de la teva aplicació.
Si ets un empleat o contractista de Google amb bona consciència i tens més informació sobre el programa, inclosos detalls tècnics previstos d’implementació o justificacions addicionals, posa’t en contacte amb tips@keepandroidopen.org des d’una màquina no laboral i amb un compte no Gmail. La teva informació es tractarà amb estricta confidencialitat.
Tothom: Feu sentir la vostra veu
- Instal·la F-Droid ↗ al(s) teu(s) dispositiu(s) Android. Com més gent utilitzi mercats alternatius d’aplicacions, més difícil serà deixar-los fora.
- Dona la teva opinió directament a Google mitjançant la seva enquesta sobre els requisits de verificació de desenvolupadors d’Android ↗.
- Fes sentir la teva veu a les xarxes socials i amb entrades de blog, i enllaça a
- Combateix l’astroturfing: quan trobis publicacions sospitoses a fòrums comunitaris i xarxes socials a favor de la política (“Bé, en realitat…”), qüestiona-les i no et tallis.
- Ajuda aquest projecte editant aquesta pàgina ↗ amb informació més útil.
- Signa aquesta petició a change.org ↗
Consumers: Contact national regulators
Regulators worldwide are genuinely concerned about monopolies and the centralization of power in the tech sector, and want to hear directly from individuals who are affected and concerned. When contacting regulators directly, you should be polite and specific about the harm you believe these policies will cause, both to consumers and to competition.
Complaints are especially impactful when they are authored by a citizen of that country or region, and when the language of the email is written in one of the official languages of the region's governing body. Request a written acknowledgement of the complaint, and consider forwarding any responses you receive to victory@keepandroidopen.org so that we might highlight and reference them.
European Union
- Email Digital Markets Act team: EC-DMA@ec.europa.eu
- Contact DMA team: https://digital-markets-act.ec.europa.eu/contact-dma-team_en ↗
Send feedback on EU interplay between DMA and GDPR: Consultation on joint guidelines on the interplay between DMA and GDPR ↗ until December 4.- Email Antitrust: COMP-GREFFE-ANTITRUST@ec.europa.eu
- Complain to the EU Competition Policy ↗
[EXPIRED] Send feedback on EU Digital Fairness Act: EU Digital Fairness Act: Have Your Say ↗
United Kingdom
- Email: general.enquiries@cma.gov.uk
- Make a report to the UK Competition & Markets Authority ↗
United States
- Make a report to the US Department of Justice Antitrust Report Online ↗
- File a complaint with the US Federal Trade Commission: Antitrust Complaints ↗
Email (DEFUNCT): antitrust@ftc.govEmail (DEFUNCT): antitrust.complaints@usdoj.gov
Brazil
- Email: superintendencia@cade.gov.br
- Reach out to Procon (depends on your state) and Senacon ↗
- Note: Brazil is slated to be one of the initial 4 countries ↗ where developer registration will be enforced
Singapore
- Email: cccs_feedback@cccs.gov.sg
- Contact the Competition and Consumer Commission of Singapore (CCCS) ↗
- Note: Singapore is slated to be one of the initial 4 countries ↗ where developer registration will be enforced
Thailand
- Email: saraban@tcct.or.th
- Contact the Office of Trade Competition Commission (OTCC) ↗
- Email: info@etda.or.th
- Contact the Electronic Transactions Development Agency (ETDA) ↗
- Email: contact@tcc.or.th
- Contact the Thailand Consumers Council (TCC) ↗
- Note: Thailand is slated to be one of the initial 4 countries ↗ where developer registration will be enforced
Indonesia
- Email: infokom@kppu.go.id
- Contact the KPPU for Competition Complaints ↗
- Note: Indonesia is slated to be one of the initial 4 countries ↗ where developer registration will be enforced
Switzerland
- File a report with the Competition Commission ↗
Australia
- Email: international@accc.gov.au
- File a report with the Australian Competition and Consumer Commission (ACCC) ↗
- Send a request to Australian Consumers’ Association (CHOICE ↗). Ask them to lodge a designated complaint to the Australian Competition & Consumer Comission (ACCC).
- Contact your local Member of Parliament or State Senator. If you don’t know your electorate, you can find it here ↗, and you can search for your Parliamentarians or Senators here ↗.
Japan
- Email: intnldiv@jftc.go.jp
- Contact the Japan Fair Trade Commission (JFTC) ↗
South Korea
- Email: kftc@korea.kr
- Contact the Korea Fair Trade Commission (KFTC) ↗
India
- Email: cci‑chairman@nic.in
- Contact the Competition Commission of India (CCI) ↗
Canada
- Email: info@competitionbureau.gc.ca
- Make a complaint to Competition Bureau Canada ↗
- File a report with the https://competition-bureau.canada.ca/en ↗
Taiwan
- Email: ftc@ftc.gov.tw
- Contact the Fair Trade Commission (FTC) ↗
Turkey
Argentina
Mexico
- Email: denuncias@antimonopolio.gob.mx
- Contact the Comisión Nacional Antimonopolio ↗
Philippines
- Contact the Philippine Competition Commission (PCC) ↗
Poland
- Email: uokik@uokik.gov.pl
- Contact the Office of Competition and Consumer Protection (Urząd Ochrony Konkurencji i Konsumentów - UOKiK) ↗
Czech Republic
- Email: posta@uohs.gov.cz
- Contact the Office for the Protection of Competition (Úřad pro ochranu hospodářské soutěže – ÚOHS) ↗
Ukraine
- Contact the National Commission for the State Regulation of Electronic Communications ↗
- Contact the Ministry of Digital Transformation ↗
- Contact the Antimonopoly Committee of Ukraine ↗
Contact These Consumer/Digital Rights Groups
- April (France) ↗
- Bits of Freedom (Netherlands) ↗
- Digital Freedom and Rights Association (Sweden) ↗
- Digital Rights Ireland ↗
- Digital Rights Watch (Australia) ↗
- Electronic Frontier Foundation ↗
- Euroconsumers ↗
- European Digital Rights ↗
- Free Software Foundation ↗
- Free Software Foundation Europe ↗
- Free Software Movement India ↗
- IT-Political Association of Denmark ↗
- Korea Consumer Agency ↗
- La Quadrature du Net (France) ↗
- Open Rights Group (UK) ↗
- Software Freedom Conservancy ↗
- Swecha Andhra Pradesh ↗
References
Overview
Editorials and Blogs
- “Your Smartphone, Their Rules: How App Stores Enable Corporate-Government Censorship” — https://www.aclu.org/news/free-speech/app-store-oligopoly ↗
- “Application Gatekeeping: An Ever-Expanding Pathway to Internet Censorship” — https://www.eff.org/deeplinks/2025/11/application-gatekeeping-ever-expanding-pathway-internet-censorship ↗
- “What We Talk About When We Talk About Sideloading” — https://f-droid.org/en/2025/10/28/sideloading.html ↗ (Hacker News Thread ↗)
- “F-Droid and Google's Developer Registration Decree” — https://f-droid.org/en/2025/09/29/google-developer-registration-decree.html ↗ (Hacker News Thread ↗)
- “Pluralistic: Darth Android” — https://pluralistic.net/2025/09/01/fulu/ ↗
- “Google plans to block side-loading like Apple, declaring war on Android freedom” — https://tuta.com/blog/android-side-load-apps-google ↗
- “Keep Android Free and Open” — https://www.swechaap.org/blog/keep-android-free-and-open/ ↗
- “Join The Protest Against The Closing Of Android” — https://www.i-programmer.info/news/193-android/18419-join-the-protest-against-the-closing-of-android.html ↗
Press Reactions
- “'Keep Android Open' movement fights back against Google sideloading restrictions” — https://www.theregister.com/2025/10/29/keep_android_open_movement/ ↗
- “Resistance to Google's Android verification grows among developers” — https://www.techzine.eu/news/devops/135878/resistance-to-googles-android-verification-grows-among-developers/ ↗
- “'Keep Android Open' Movement Challenges Google's Developer Verification Rule” — https://www.opensourceforu.com/2025/10/keep-android-open-movement-challenges-googles-developer-verification-rule/ ↗
- “Google kneecaps indie Android devs, forces them to register” — https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ ↗
- “Open-Source Android Apps at Risk Under Google's New Decree” — https://www.techrepublic.com/article/news-f-droid-warns-google-developer-decree-open-source-android/ ↗
- “Google's New Developer ID Rule Could Harm F-Droid, Says Open-Source Advocate” — https://reclaimthenet.org/googles-android-id-rule-threatens-f-droids-future ↗
- “Google's developer registration 'decree' means the end for alternative app stores” — https://cybernews.com/tech/googles-developer-registration-decree-end-alternative-app-stores/ ↗
- “Open-Source Android Apps Threatened by Google's New Policy” — https://www.datamation.com/open-source/android-apps-google-policy/ ↗
- “Google's new ID requirements could destroy independent app stores” — https://www.techspot.com/news/109728-google-confirms-new-android-rules-significantly-restrict-app.html ↗
- “Google's Requirement For All Android Developers To Register And Be Verified Threatens To Close Down Open Source App Store F-Droid” — https://www.techdirt.com/2025/10/07/googles-requirement-for-all-android-developers-to-register-and-be-verified-threatens-to-close-down-open-source-app-store-f-droid/ ↗
- “Google's new developer rules could threaten sideloading and F-Droid's future” — https://www.gizmochina.com/2025/09/30/googles-new-developer-rules-could-threaten-sideloading-and-f-droids-future/ ↗
- “Google is restricting one of Android's most important features, and users are outraged” — https://www.slashgear.com/1962802/google-restricting-important-android-feature-reason-why-users-outraged/ ↗
- “Android's sideloading limits are its most anti-consumer move yet” — https://www.makeuseof.com/androids-sideloading-limits-are-anti-consumer-move-yet/ ↗
- “Google's dev registration plan 'will end the F-Droid project'” — https://www.theregister.com/2025/09/29/googles_dev_registration_plan_will/ ↗
- “F-Droid says Google's new sideloading restrictions will kill the project” — https://arstechnica.com/gadgets/2025/09/f-droid-calls-for-regulators-to-stop-googles-crackdown-on-sideloading/ ↗
- “Google will require developer verification for Android apps outside the Play Store” — https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ ↗
- “Google will verify Android developers distributing apps outside the Play store” — https://www.theverge.com/news/765881/google-android-apps-side-loading-developer-verification ↗
- “Google will require developer verification to install Android apps, including sideloading” — https://9to5google.com/2025/08/25/android-apps-developer-verification/ ↗
- “Android Security or Vendor Lock-In? Google's New Sideloading Rules Smell Fishy” — https://news.itsfoss.com/new-android-sideloading-rules/ ↗
- “Google Demands Dev Identity For All Android Apps” — https://www.i-programmer.info/news/193-android/18276-google-demands-dev-identity-for-all-android-apps.html ↗
- “Google Defends Developer Verification” — https://www.i-programmer.info/news/193-android/18356-google-defends-developer-verification.html ↗
- “Keep Android Open – Abwehr gegen Verbot anonymer Apps von Google” — https://www.heise.de/news/Keep-Android-Open-Abwehr-gegen-Verbot-anonymer-Apps-von-Google-10965483.html ↗
Video Responses
- “Google: 'Your $1000 phone needs our permission to install apps now'” — Louis Rossmann — https://youtu.be/QBEKlIV_70E ↗
- “F-Droid Will Die in 2026 Unless We Act Now” — Techlore — https://youtu.be/wRvqdLsnsKY ↗
- “Google is Removing Sideloading” — LMG Clips — https://youtu.be/-R76VJtTDJ8 ↗
- “Google's changes to sideloading could end F-Droid” — Linux Weekly News — https://youtu.be/iMqpm2Ahmt0 ↗
- “Is F-Droid in Trouble? Google Developer Verification” — https://youtu.be/-SOOoQWv4kk ↗
- “Google is Applefying Android: The End of Openness” — ChiefGyk3D — https://youtu.be/WFOPzixHoLY ↗
Discussions
- https://news.ycombinator.com/item?id=47091419 ↗
- https://www.reddit.com/r/degoogle/comments/1ralfa2/googles_sideloading_lockdown_is_coming_september/ ↗
- https://www.reddit.com/r/fossdroid/comments/1rallch/googles_sideloading_lockdown_is_coming_september/ ↗
- https://news.ycombinator.com/item?id=45742488 ↗
- https://news.ycombinator.com/item?id=45409794 ↗
- https://news.ycombinator.com/item?id=45507173 ↗
- https://news.ycombinator.com/item?id=45569371 ↗
- https://news.ycombinator.com/item?id=45742488 ↗
- https://lobste.rs/s/x1sdu5/f_droid_google_s_developer_registration ↗
- https://www.reddit.com/r/androiddev/comments/1n1m699/horrible_news/ ↗
- https://www.reddit.com/r/androiddev/comments/1n3jtrf/google_you_royally_screwed_up/ ↗
- https://www.reddit.com/r/androiddev/comments/1n0uy6g/just_received_this_email_now_you_can_get/ ↗
- https://www.reddit.com/r/androiddev/comments/1n2im4j/this_may_mark_the_end_of_android_development_for/ ↗
- https://www.reddit.com/r/androiddev/comments/1n0f41c/google_will_require_developer_verification_to/ ↗
- https://www.reddit.com/r/androiddev/comments/1km8jof/google_play_developer_verification/ ↗
- https://www.reddit.com/r/androiddev/comments/1mzw877/android_developers_blog_a_new_layer_of_security/ ↗
- https://www.reddit.com/r/androiddev/comments/1n7g0cc/to_all_android_devs_speak_up_now_before_you_lose/ ↗
- https://www.reddit.com/r/androiddev/comments/1oaj908/collection_of_actions_we_can_take_to_stop/ ↗
Official Documentation
- Initial announcement — https://android-developers.googleblog.com/2025/08/elevating-android-security.html ↗
- Let's talk security: Answering your top questions about Android developer verification — https://android-developers.googleblog.com/2025/09/lets-talk-security-answering-your-top.html ↗
- Android developer verification: Early access starts now as we continue to build with your feedback — https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html ↗
- Android developer verification: Guides — https://developer.android.com/developer-verification/guides/android-developer-console#complete-identity ↗
- Android developer verification: Frequently asked questions — https://developer.android.com/developer-verification/guides/faq ↗
- Introducing the Android Developer Console: A first look — https://developer.android.com/developer-verification/assets/pdfs/introducing-the-android-developer-console.pdf ↗
- Download an early look of the new Android Developer Console — https://support.google.com/android-developer-console/answer/16450960 ↗
- API Documentation — https://developer.android.com/reference/android/content/pm/PackageInstaller#DEVELOPER_VERIFICATION_FAILED_REASON_DEVELOPER_BLOCKED ↗