Amidst all the chaos in the world, some significant moves are being orchestrated that could potentially have detrimental effects on people’s privacy and right to choose. Google’s Developer Verification program falls under the latter.

Starting September 2026 (in certain regions), any app installed on a certified Android device will need to come from a developer who has gone through Google’s new verification process. This applies regardless of where the app comes from: the Play Store, a third-party storefront, or a direct APK download.

To get verified, developers must register through a dedicated Android Developer Console and provide their legal name, address, email address, and phone number. In some cases, they will also need to upload a government-issued ID.

  • spaghettiwestern@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    16
    ·
    1 day ago

    Pure gaslighting by a multi-billion dollar company that’s responsible for the vast majority of Android malware in the wild. If Google wanted to make Android safer they’d make a concerted effort to stop distributing malware through the Play store.

    • ozymandias@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      not that i trust multi-billion dollar companies, but that would be a fairly effective way to fight malware on the store.
      (oh course malware authors will find loopholes that regular developers don’t use, or just buy hacked developer accounts for $1.00 on the dark web)

  • NarrativeBear@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    20 hours ago

    I will literally go back to a dumb flip-phone and definitely Linux phones are starting to look more appealing

  • shortwavesurfer@lemmy.zip
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 day ago

    Thankfully, many of the apps I use every day have said that they will refuse to do this.

    I am also now more seriously than ever looking into Linux phones such as PostmarketOS. Sure, for now, it’s going to be Google certified devices only. But what’s to keep Google from attempting to put this into AOSP in a couple of versions from now?

    • Infernal_pizza@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      3
      ·
      23 hours ago

      I feel like if it gets put in AOSP it will still be possible to remove since it’s open source. My biggest concern is just not having any new hardware available to even run the alternatives. There are already few devices that still have unlockable bootloaders, and Googles own device are some of the most prominent ones. And with OS level age verification laws popping up everywhere there’s even more incentive for manufacturers to lock the bootloader

  • ThomasWilliams@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    20 hours ago

    Amidst all the chaos in the world, some significant moves are being orchestrated that could potentially have detrimental effects on people’s privacy and right to choose

    There is no privacy on Android.