cross-posted from: https://discuss.tchncs.de/post/45277582

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.

  • ReversalHatchery@beehaw.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    13 hours ago

    certified android devices are those you can get in most stores. the play store is important for many people, ajd many apps don’t work correctly without the google mobile services components, and device makers can only legally install these on their phones if they certify their device. the certification process requires an array of quality controls and restrictions.

    How can they enforce this for apps not on the play store?

    certified devices will need to integrate an app verifier that will check if an app has been approved by google. the public AOSP project is said to also get this, but anyone basing on it can rip it out or modify it to their advantage. but certified device makers don’t have a choice thn to include this restriction.

    Like if I write my own APK will my phone just refuse to run it if I don’t go through some paperwork with Google?

    what we know so far, apps you made can be installed through a development tool. but app store aps like fdroid don’t have access to this tool, it’s difficult to enable, and somewhat risky too