Google: pay and register as a developer with us, or your users must wait a day after deciding to install your app.

No surprise that the alternative to handing over ID, money, and contractual agreement to Google is a hostile experience for users.

https://android-developers.googleblog.com/2026/03/android-developer-verification.html?m=1

#keepandroidopen

Android developer verification: Balancing openness and choice with safety

News and insights on the Android platform, developer tools, and events.

Android Developers Blog
"Give us money and data, or your users' experience will suck" is, apparently, "balance".

Selfishly, I will not be affected by this, because I use a version of Android without Google - GrapheneOS.

But this will be of little solace for the myriad users stuck with Google-flavoured Android, who did not agree to this ludicrous dance simply to be able to install software on their own phone.

#KeepAndroidOpen

"We have heard your feedback. We have a balanced solution: we are only going to punch you in the nuts once."
@neil That's a step up on the usual behaviour.
@neil How is the GrapheneOS experience? I'm keen to make the jump but hear mixed feedback about the UK banking apps not playing well with it. I guess the trade off is not to use my phone for banking, but I would miss the convenience.

@darren

> How is the GrapheneOS experience?

Superb.

Yes, some banks have, disappointingly, chosen to cease support for some customers, and I use a web login for those instead.

@neil GrapheneOS users will be affected if developers decide to discontinue apps rather than put up with Google's bullshit.
@neil Are you running that on a Pixel or a non-Google device?
@kbm0 Pixel
@neil 😭
@kbm0 There is a Motorola device coming, but I will need to upgrade before then.
@neil Ooh thanks for the tip, I will wait and see what happens. Not sure yet quite how unworkable all the F-Droid apps will become.
@neil does graphineos manage to make stuff work that requires device attestation? E.g. banking apps, google wallet, etc?

@steve I have not used Google Wallet, so I do not know.

Some banking apps work, some do not.

@neil well, at the moment I can't use any of that stuff because my phone is rooted and I gave up jumping through hoops every time Google changed attestation.

@steve

That's how I view it too - I prefer to use GrapheneOS over banks who'd prefer to lock me out.

Fortunately, I can access all of my accounts through their bank's website, which suits me fine.

I've moved in many cases away from apps entirely, to websites, as that helps as part of me exploring non-Android Linux-based phones.

Contactless Payments with GrapheneOS

Google's monopolistic stranglehold on Android results in poor experience for power-users, and artificially restricts choice for those who have older phones. For example, Google Wallet is the de facto way to use NFC payments on Android. There's one problem though - it only works with Google's Android. If you have the temerity to install a 3rd party Android OS - like the hyper-secure GrapheneOS - …

Terence Eden’s Blog
@neil now I want a phone with Graphene

@neil If I read correctly, this is something you do once to enable the ability to sideload.

I will probably do that when I open the box of a new phone, and then be done with it.

I still see how it could annoy someone in a time-critical situation

@jfparis To me, it is far more about Google's increasing assertion of control, than the specifics of this measure.
@jfparis @neil If I lose my phone and can't use my Pager for 24 hours, that's a serious problem as a person who handles emergencies
@neil That's a nice app you have there, it'd be a shame if something happened to it.
@neil Of course it's balanced... both options are horrible.
@neil Predictable response, I'm afraid. Is this their new compromise to the backlash? Instead of a total lockout, it's "only" a dark pattern?
@abmurrow @neil This can't really be called a "dark pattern". It is not trying to trick you into doing anything. It is trying to prevent you from being tricked into doing something.
@WAHa_06x36 @neil Sure it is. The system won't prevent you from installing third party software, it just makes it a pain to do so. The verification and registration process for developers is a pretense for preventing you from using apps Google isn't getting paid to distribute.

@abmurrow @neil That isn't a "dark pattern", though. A dark pattern is trying to mislead you into doing something you didn't actually want to do.

And it doesn't really make it that much of a pain: You do this once, and then you can go ahead and install third party software as much as you'd like. For someone who likes to do so it'd just be an annoying extra step when setting up their phone for the first time.

@WAHa_06x36 @neil I think we're splitting hairs here on the definition.

Look-- why are we even talking about allowing someone else decide how you're allowed to use your device? Someone who has a financial interest in pushing you toward a software ecosystem that they control and can use to monetize your interactions with that platform? Why defend an obvious power grab by one of the largest corporations on the planet?

Sure, it starts with a mild inconvenience, and then, a year from now when no one is paying attention and for some abstract security reason they refuse to explain, a new update comes in that makes the day long wait mandatory for every download. Or maybe, they just disable side loading, like they've been talking about doing for ages.

It's not unheard of, and it's not being defended in good faith.

@abmurrow @neil Because having a device with strict security guarantees is actually a good thing for most people, much more so than having a device that can run arbitrary software.

It may not be for you and me, but to deny that it is an advantage for many is to blind yourself to the truth and to choose to be ignorant, and that is never going to get you anywhere.

@WAHa_06x36 @abmurrow

It seems rather convenient that the necessary and proportionate solution to a problem (which is not clearly enunciated) just happens to entail Google taking more control over Android, locking out competing app stores, and requiring government-issued ID from everyone who wants to distribute software conveniently for Android.

#KeepAndroidOpen

@neil @abmurrow I mean I am sure they are not unhappy about those things. But that doesn't mean that it is not also a real solution to the issue.

@WAHa_06x36 @abmurrow Perhaps, one day, they will publish the analysis which shows that it is the only solution, or the most proportionate of all available solutions.

I am sceptical of this.

@neil
So I see that they're using scammers as the reasoning behind this, but like, don't most scammers use legit apps/software to run scams anyway??
@neil looks like you only have to wait the 24 hours once and then you're good? still unjustifiable though

@aburka That was my reading: enable developer mode, answer some questions, reboot, and then wait a day. Once you've done all that, you can enable "unverified developers" forever.

Slightly annoying, but only once per phone.

@neil

@neil this will kill OSS install parties and similar. google moment.

@neil

Looks like it's one time to enable unregistered apps rather than per app at least. Still quite a while

@neil While I would much prefer Google to clean out their own app store from all the malware that's already there, instead of hassling independent developers, I think that the "advanced flow" as shown in the linked blog post seems mostly reasonable. The one-day wait is only for the first time the flow is used, it doesn't apply on further installs or updates.

I would have expected worse (for example the user having to register with Google to bypass it, or there just being no bypass at all outside of ADB)
@neil this is obviously better than a total lockout. But even if they're technically allowing it, the added inconvenience still represents an attack on "general purpose computing". Which I can tell you as an educator of teenagers is going very well for big tech.
@neil Ah yes, one day wait, that will stop scammers
@neil that's both not as bad as I thought it would be and also pretty fucking bad
@neil what the hell. Is that iOS hell ecosystem with extra steps??