In August 2025, Google announced that starting next year, it will no longer be possible to develop apps for the Android platform without first registering centrally with Google. This registration will involve:

  • Paying a fee to Google

  • Agreeing to Google’s Terms and Conditions

  • Providing government identification

  • Uploading evidence of the developer’s private signing key

  • Listing all current and future application identifiers

  • Here is the https://keepandroidopen.org/

  • Arghblarg@lemmy.caEnglish
    35·
    2 days ago

    I’m keenly watching GrapheneOS and what they plan to do; supposedly they are working on a strategy.

    Long-term, yeah Android needs a rival; I hope at least one of the Linux Phone projects out there can get good enough to use on some common brands or make an entirely new platform viable.

    • ColeSloth@discuss.tchncs.deEnglish
      9·
      2 days ago

      What sucks is more and more android phones are locked down and won’t ever allow you to root or change the OS. As far as US working phones, it’s almost down to only Pixels, which is likely going to change soon; and OnePlus.

      I don’t know anyone who owns a OnePlus phone.

      • jcarax@beehaw.orgEnglish
        3·
        1 day ago

        That seems to be their mid-term strategy, release their own certified device. That should have some interesting implications on safetynet attestation, too.

        I still think we need a fork of AOSP, before the community atrophies any further.

        • artyom@piefed.socialEnglish
          3·
          1 day ago

          That seems to be their mid-term strategy, release their own certified device.

          If you look up what “Certified Device” means in the context of Android, we don’t want that.

          I still think we need a fork of AOSP, before the community atrophies any further.

          GrapheneOS is a fork of AOSP.

          • jcarax@beehaw.orgEnglish
            2·
            1 day ago

            Honestly, I don’t know if having play services running in a profile that can be deleted would pass that standard for certification. Probably not, I guess.

            As for being a fork, I mean the larger community of Graphene, Lineage, Calyx if it continues to exist, and probably a couple Chinese manufacturers who rely on AOSP to manage a fork that is collaboratively developed going forward, that no longer relies on Google’s maintenance of the project.

            • artyom@piefed.socialEnglish
              3·
              1 day ago

              that no longer relies on Google’s maintenance of the project.

              Yeah that’s just a gargantuan task or someone would have done it already. Sadly, too few people care to make that happen.

              Huawei did it (HarmonyOS) but only because they’re a huge company with the necessary resources, and because they were legally prevented from using Android.

              • jcarax@beehaw.orgEnglish
                2·
                1 day ago

                I know, but it’s looking more and more like there won’t be an alternative for long. I’d rather have a consortium of interests united in moving a fork forward as the core for all of their own OS’s.