Criticism: reuse citation instead of duplicating it
Rudxain (talk | contribs)
m link Google_Android_restrict_app_sideloading
 
Line 1: Line 1:
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".<ref>{{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}}</ref>
On August 25th, 2025, [[Google]] announced an upcoming [[Google Android restrict app sideloading|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".<ref>{{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}}</ref>


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.
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.