{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiekymhos6asxjanhv7iuex74syknqrraos3tdizpiq7topz64l37i",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mlkbokcejnn2"
  },
  "path": "/t/people-fear-mongering-google-blocking-android-sideloading-is-causing-more-harm-than-good/37787#post_1",
  "publishedAt": "2026-05-11T02:09:46.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "I’m not against the protest. I’m equally upset that Google has done this and the path they’re on. But the fear mongering of what this actually means in the short-term is causing the unintended effect of causing people to give up on FOSS Android projects completely and prematurely.\n\nAs of now, in practice, it appears Google will require a one-time toggle in developer settings followed by a 24 hour delay before restoring your ability to install apps from outside the Play Store. This also only affects certified Google devices while devices running things like GrapheneOS, LineageOS, etc are unaffected.\n\nFor the typical person in the privacy community, we’re either already setup to bypass it or it will amount to a single brief annoyance.\n\nBut more concerning is how it may affect ordinary android users. The drop in convenience may cause ordinary users to not bother looking for FOSS alternatives outside the Play Store. And if these FOSS alternative see their users drop, developers may abandon their work, which will affect all android users, even those of us on unaffected devices.\n\nThis fear mongering though is causing a storm of misguided advice amongst ordinary users. I’m seeing it all over the place whenever this topic comes up. People are suggesting they ditch android altogether and buy iPhones. They’re spreading misinformation about what Google officially plans to do. They’re saying privacy and freedom on Android are dead - not that they’re on the path to dying, but that once this update comes through, they’re dead dead with no salvation.\n\nDon’t get me wrong. There needs to be a very loud pushback against Google for doing this. They’ve already loosened up the restrictions after the initial backlash. But right now, the biggest threat to user freedom on Android is the user itself.\n\nGoogle is hoping that ordinary users won’t figure out how to enable “sideloading” and the fear mongering from protestors is only re-enforcing that it will be too difficult and too intimidating for ordinary users to try.\n\nIf we want to save these FOSS android projects, at least in the short and medium term, social media should be flooded with accurate guides of what to expect and easy to follow tutorials for people to follow. The goal should be that every person with an Android phone either switches to something like GrapheneOS (ideally) or at minimum, permanently re-enables sideloading on day 1.\n\nThere can be various social movements in this effort as well like encouraging people to “save” their friend’s and family’s phones too.\n\nWe need to familiarize people with the process and normalize doing it. Imagine, for example, popular unboxing videos where YouTubers restore sideloading functionality as part of a standard android unboxing and initial setup process.\n\nAssuming it’s allowed, third-party developers should include very visible guides to unlock sideloading for new user onboarding. F-Droid should have it front and center. This is a fight for convenience. Make it as convenient as possible for ordinary users to figure out what to do.\n\nPrivacy Guides should include this guide as well as a note for users still using Google certified Android devices. A privacy guides video explanations and short-form tutorial wouldn’t hurt either.",
  "title": "People fear mongering Google blocking Android \"sideloading\" is causing more harm than good"
}