Hello HN,I ve been playing around with AOSP alot and one thing i noticed is how much android depends on google even if Android itself doesnt need it. Here s everything i found out:1. Forced Integration of GPS (google play services) - This single handedly causes alot of problem to power users because without it almost nothing works.. Even if you use MicroG there s still some server side verifications that it just cannot help with.2. Sideloading Restrictions - Starting in 2026, Google requires developers to submit government IDs, pay fees, and register signing keys to distribute apps via sideloading, effectively blocking independent software distribution on certified devices.3. Ecosystem dependence. I don t need to explain this one at all i think4. Apps literally won t work. Banking apps and any app that uses play integrity will just refuse to work.What made me the most furious was Google locking down opensource apps with unverified devs. This caused an uproar in the open source community and F-droid because of which google (around december 2025) made an option which is outrageous. You need to click the build number 7 times - click allow unverified Packages and then put your device pin. Then you have to wait 24 hours before anything can be downloaded at all.Although you can still download via adb, The workaround seems very obstructive. Google didn t even plan to allow unverified packages until the open-source community said something.I ve made this extremely easy to understand without any community-specific wording so anyone can understand this.