[…]
In the new blog post, Google’s Matthew Forsythe confirms that the developer verification system is slated to come online on September 30 of this year. The initial deployment will be limited to countries with a high level of app scams: Brazil, Indonesia, Singapore, and Thailand.
[…]
Google released its new developer console back in March, inviting external developers the opportunity to pay $25 and verify their identities early. Developers who don’t register will find that their apps cannot be sideloaded on Google-certified Android devices once verification has rolled out. Google says that almost every app in the Play Store is now ready for the change, and a “large majority” of apps outside Google Play have completed verification.
[…]
Google says it will verify the apps in the following stores when it begins enforcing the new restrictions.
Google (Google Play)
Honor (HONOR App Market)
OPlus (OPPO App Market)
Samsung (Galaxy Store)
Transsion (Palm Store)
vivo (V-Appstore)
Xiaomi (GetApps)
[…]
The next step toward verifying apps will come this month as Google deploys a new system service on most certified devices. The package (com.google.android.verifier) will appear on phones and tablets running Android 8 or higher, allowing Google to block the installation of unverified apps. It will remain dormant until verification is activated in your specific region.
In July, Google plans to roll out the new developer APIs and begin testing for “limited distribution” accounts. This is Google’s solution for hobbyists who want to make their own apps and share them with a small group. Limited accounts won’t require a fee or government ID verification, but you can install these apps on up to 20 devices.
In August, the advanced flow will become available globally ahead of verification becoming mandatory in the first markets. As detailed a few months ago, the advanced flow will allow users to bypass verification, but the process isn’t easy. You’ll have to navigate to a buried menu, confirm you understand the risks multiple times, and wait a whole day before completing the process.
And that brings us to September, when Android devices in Brazil, Indonesia, Singapore, and Thailand will begin checking verification status before installing apps. However, things get murky after that. Google will undoubtedly monitor how verification works as millions of users are suddenly limited to verified apps, which could affect how it moves forward. Google says it intends to expand developer verification in 2027, eventually making it a global device policy.
Hey Google, could you not dictate what I’m allowed to install on my own damn device for my “safety”? I don’t need a third parent, and if I had to pick one it wouldn’t be you.
May a thousand bricks breach Google HQ’s windows.
Bricks aren’t enough, every Google building needs carpet bombing while the assholes who’s main purpose is to do evil are locked inside.
Fuck this shit!
How greedy are you?
Google, you stick to your guns, I’ll stick to mine. Sayonara.
This is like if Walmart started policing what products Target can sell and policing what products can go into your house, while not bothering to police their own store.
LineageOS is the way.
I hate this timeline
An additional sting for some of us -
In Australia, not only is 3G deprecated (I miss my Nokia n91), but 4G / 5G must be of the VoLTE variety. To date, there is no after market OS that is fully VoLTE compatible (Legacy, Graphine etc) here - its hit or miss. Additionally, most (but not all) overseas phones are on IMEI black lists by default.
Essentially, because the OEM are lock step with Google, you can’t avoid this issue by purchasing a common phone, unlocking your boot loader (assuming you could in the first place) and flashing CFW. Do that and you can’t make phone calls. Don’t do it, and you get caught up with this new app verification slop.
They think they’re winning… but I think “lol. Keep going. I have a flip phone.” As soon as this Samsung dies (adb debloated and all), I’m out entirely.
My Galaxy A20 has been going strong since 2019. If I get anything, I’ll either be something from that era or just go full flip phone.
PS: someone mentioned the commodore flipphone. I like Perri and the C64 revival but let’s be honest here…the Callback 8020 phone is $$$ for pretty bog standard dumb phone parts. The components don’t justify it (barring perhaps the 48MP camera), let alone some of the design decisions.
If you look, I imagine you can find a local equivalent of this instead -
https://www.officeworks.com.au/shop/officeworks/p/opel-mobile-touchflip-4g-flip-phone-optouchfp
(TTfone or Sunbeam I think?)
With right launcher and larger battery, I find it perfectly cromulent, with very good keyboard. It even runs FUTO voice STT (albeit slowly), my banking apps, Signal, FB messenger, maps, 5MP camera etc. It’s not going to replace flagship anything… but maybe it doesn’t need to. And it’s 1/8th the cost.
There’s a good YouTube channel for anyone considering such devices -
How can I stop it from happening on a Samsung s25? Can I just not update Google services somehow? Atleast until I can import a phone with graphene or Motorola releases one? I dont care about the apps from outside store but I do about the verified device shit.
I really just hope that this “com.google.android.verifier” package won’t become a system app so i can just uninstall it whenever it appears on my device.
Reinstall the OS without google.
Or you could buy a new or used device that’s already degoogled. Or go to your local phone repair shop and pay them to do it for you.
Maybe Commodore saw this coming and that explains the crazy pricing of their linux flip phone.
So just because I refuse to forfeit my soul to the Satan’s company, I won’t be able to use my phone? Fuck this and fuck Poogle, I’d rather switch to Nokia 3310!
Unlinked, code 7919e0d4
I’m not happy about this but they really have no choice.
The android app marketplace is infested with spyware and Android devices were recently found to be the vector for one of if not the worlds biggest botnet (super/bad box).
If you wanna be able to keep using your os to make ad money you gotta lock it down and since Android is largely open source and used by tons of oems that means locking down some part that you could conceivably do without but no one really will.
None of this even attempts to address the problem of Google Play (the primary android app marketplace) being filled with malware. Every single app that’s being distributed through Google Play today already has a “verified” developer by the same criteria they’re applying system-wide. That malware can continue working as it already does without any changes.
This is exclusively about Google imposing control on all apps distributed through channels that otherwise used to be outside Google’s control.
Google’s claimed reasoning is that this control is a good thing and makes them be able to block apps made by malware developers in the same way they already do in Google Play, even for users who install apps from other sources. Critics disagree because Google forcibly taking personal information and money from all software developers and wielding the ability to remotely kill any app they don’t like for any reason have far wider consequences than protecting users from malware, and the proliferation of malware on Google Play shows how (in)effective Google’s measures against it are. Neither side believes or claims this can or will make Google Play any safer.
Yes it does.
It forces developers to register if they wanna distribute software. Now they can’t just pivot to a new identity whenever they’re under investigation.
It prevents devices from running software from unverified developers. Now the malware developer can’t just use a third party store to bypass the verification requirements.
That’s both sides of the coin, but wait, there’s more:
End users can disable it if they’re willing to go without play services or can do their own sideloading and support with a “limited” developer account.
The end result is not a panacea that fixes every problem with Android but a move to bring the various official android marketplaces in line with the ios app store.
Google already does what it should: sideloading apps requires you to manually approve the source, and when you do, a popup appears warning user of potential dangers. No need to play daddy any more than this.
Having a locked ecosystem is very convenient and profitable for Google, but terrible for its users. Google wants this walled garden not out of safety, but to get a tight grip on the app stores - and get a solid buck while doing it.
