Keep Android Open - GrapheneOS affected by Google's new requirement?

Sympathietraeger

Hi everyone,

I read here that a lot of apps won't work any longer or at least can't be installed any longer from September 2026. This is because Google from then on enforces that all app developers need to be registered with them (including verified identity, a fee and agreement to their terms of use). One app that I installed via the F-Droid store warned me that it will then stop working.
Besides the range about this attack on people's freedom, I wonder whether this will also affect my Pixel with GrapheneOS. I use two profiles, only one of them has Google Play Services installed.
Cheers,
Jijou

Murcielago

Sympathietraeger

Besides the range about this attack on people's freedom, I wonder whether this will also affect my Pixel with GrapheneOS. I use two profiles, only one of them has Google Play Services installed.

See:

It's not relevant to GrapheneOS. GrapheneOS does not have Google Mobile Services and rules for Google certified operating systems don't apply to it. Sandboxed Google Play are regular sandboxed apps and can't block installing apps. Play Protect already exists and isn't an issue.

source: https://xcancel.com/GrapheneOS/status/1962170959168675887#m

Kamika242

Sympathietraeger

I think or hope that this won't affect GrapheneOS and other custom roms, but I can imagine, that a lot of app developers won't develop again only for roms apart from official Google certified Android versions.

Developer-Dude

Sympathietraeger as wizoatk said with that link, This does not apply to GrapheneOS. GrapheneOS and apps will be fine

SiriusLeigh

Sympathietraeger I'm pretty sure this doesnt affect FOSS apps.

wizoatk

Android Developer Verification: Are we screwed? (no, doesn't apply to GOS)

Sympathietraeger

wizoatk Kamika242
And thanks for that one! I didn't think about the implication that developers might stop developing their apps. Very worrying!

Sympathietraeger

Murcielago
Thanks for your answer! That is what I hoped.

raccoondad

Kamika242 that a lot of app developers won't develop again only for roms apart from official Google certified Android versions.

Why would they do that? They can still run & test their apps via ADB, which means others can as well. Hopefully Google adds a developer toggle of some kind, but even then, adb works its just unfortunate for stockOS ppl

Kamika242

raccoondad Why would they do that?

The amount of phones with custom roms is very small unlike phones with official Google Android. Many developers provide their apps for free in sources like F-Droid, but paid versions in the Playstore. I can understand every developer, who doesn't want to lay oneself completely bare to Google, bu app development isn't only a humanitarian thing, a lot of developers have understandably to earn money for their work and I don't know if the custom rom market is large enough for that, as they mostly rely on donations there.
Additionally the normal Android user isn't familiar with ADB, sideloading or other sources apart from Playstore.

Sympathietraeger

@wizoatk ... and sorry I missed that thread. I searched the forum for "keep Android open" and didn't find anything.

raccoondad

Kamika242 you already need to give your ID to google for app publishing in play store, no? Not much has changed outside of not being able to load apks directly from the FS.

Its not a good change unless google makes it a dev toggle to enable, but the idea much has changed in regards to app publishing isn't true. Just how end users have to install it.

As far as I understand, you do not need a custom ROM to install apps from unverified sources, just that android has provisioned ADB as the main method of doing so. Not good but also isn't a complete system lockdown.

https://support.google.com/googleplay/android-developer/answer/13628312?hl=en

TrustExecutor

raccoondad The thing is that it is a slippery slope and it can be locked down further at any time in the future.

phone-company

Yes, the problem is not with the customer, but with the developer. The customer can still install all apps but the developer should identify himself

raccoondad

phone-company the customer doesn't need to even with these changes, I agree for googles official repos that they should identify themselves, but for unofficial there's no reason to require identification. A signing key is fine enough

raccoondad

SiriusLeigh it does, not in development but in installation for end users

Sympathietraeger

SiriusLeigh
I am pretty sure it does affect FOSS apps (on stock Android) because it was within a FOSS app that I got a warning that this app won't work any longer when these rules will be applied.

SiriusLeigh

Sympathietraeger I wasn't thinking in terms of stock Android. Why would I? I'm on a graphene OS discussion board.

Sympathietraeger

It crossed my mind that the new restrictions might actually be illegal in the EU as they could be in conflict with the Digital Services/Markets Act. One person has officially asked the European Commission about that in the beginning of April. It seems like there is no answer yet.

TrustExecutor

Sympathietraeger
This is really interesting.