Opening my weather app this morning I was greeted by this warning:

Google has announced that, starting in 2026/2027, all apps on certified Android devices will require the developer to submit personal identity details directly to Google. Since the developers of this app do not agree to this requirement, this app will no longer work on certified Android devices after that time.

It's the first time I hear about this, seems to be about:

Tech crunch article from august, "google will require developer verification for android apps outside the play store"

Cirrus app: Github

Was this a big thing I somehow missed? I hope more devs will follow suit.

you are viewing a single comment's thread
view the rest of the comments
[–] 118 points 1 year ago (21 children)

They're not "pulling" the app from anywhere, it's just simply not going to work on "certified devices". This is the end of Android as we know. It's been a good run.

  • source
  • hideshow 21 child comments
  • [–] [S] 19 points 1 year ago (2 children)

    Yes you're right. I've worded that wrong in the title!

  • source
  • parent
  • hideshow 2 child comments
  • [–] 12 points 1 year ago (7 children)

    When one thing dies, another thing is born.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 11 points 1 year ago (4 children)

    UBPorts is ready to go and isn’t tied to Google hardware like Graphene.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 1 year ago (2 children)

    Doesn’t have manufacturer support

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago

    It's also absurdly lacking in features compared to Android/iOS (never mind app support) and the dev team is so small they can barely maintain existing device support. VoLTE is still unsupported in the majority of devices. The OS doesn't even have basic security features like drive encryption

    I like UBPorts a lot but I think the alternative/FOSS smartphone market is too fragmented between it and SailfishOS/PostMarketOS that none of them will emerge with enough adoption to be real competitors to the iOS/Android duopoly. Didn't mean to be overly negative. Just my two cents

  • source
  • parent
  • [–] 8 points 1 year ago (5 children)

    Only works for those of us who own a pixel or bought one for the reason but this won't effect Graphene users

  • source
  • parent
  • hideshow 5 child comments
  • [–] 22 points 1 year ago (1 child)

    Except it will, because developers aren't going to bother maintaining an app where the install base is just pixel users with Graphene

  • source
  • parent
  • hideshow 1 child comment
  • [–] 12 points 1 year ago

    Yep. We'll be fine for a while but Google's seriously axing the platform for foss projects and security-minded users. In no more than half a decade I anticipate Android's open-source development scene will begin looking very similar to Apple's.

  • source
  • parent
  • [–] 6 points 1 year ago (3 children)

    I believe you can sideload with ADB.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 13 points 1 year ago (1 child)

    Nope, from how Google puts it, play services will block any and all apps without a valid signature from working at all on play certified devices.

    You'll be able to install them via adb probably, but when you run them play services will stop you.

    Play services already prevents certain apps from starting until you say a yes/no on a popup, so the framework for this is already in place.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 1 year ago*

    This is completely wrong. I asked this exact question to google in their poll and I got an answer from them saying it would always work with adb. It's for devs so you can run those apps of course. This means F-Droid can implement a Shizuku backend to install apps and the UX will be even better since it will bypass popups. However, initial setup will be far more complicated

  • source
  • parent