This trend of being actively hostile toward your user base is so confusing to me.
They project that they’ll make more money by forcing people to accept surveillance so they can run their apps, even if they lose a few users and app developers by doing so.
I’ve always been of the opinion that apps are almost always useless because there is usually a way to do it through a web browser and if there isn’t I don’t need it. And its usually better because then I have more control (in firefox anyway).
For example the youtube app is entirely unuseable but if I open firefox and use ublock and no script then suddenly I can actually use the website.
deleted by creator
Their goal is to ensure OEMs only bundle Google-approved Android for which Google charges licensing fees and which funnels users into Google services. If a phone won’t run your banking app, you probably won’t buy it.
deleted by creator
deleted by creator
RIP banking apps and Mc Donalds on GrapheneOS
Time to get downvoted to oblivion.
I see a lot of people questioning why Google would do this and the answer is pretty simple.
Google created a tool a long, long time ago which was meant to make sure traffic from a device was “legit”. This tool is 100% optional and app developers can use it if they would like. However, the tool was easy to bypass, so over the years Google has been making the tool harder and harder to bypass.
This article is just sharing news that Google is once again making this tool harder to bypass.
So why is Google doing this? They are doing this because they don’t want their tool to be bypassable. Their tool is worthless if it can be bypassed.
The tool in question here is the Play Integrity API (previously known as the SafetyNet Attestation API). This is a tool that is offered to app developers that app developers can take advantage of if they want. The selling point of the tool is if you have operation in your app that is critical, you can try to prevent some abuse by verifying that the app is running on a “trusted build of Android” and that the app itself has not been modified from the original. That’s all the tool does.
This isn’t a new API. This isn’t something Google is trying to force app developers to use. No. From Google’s point of view, they are just making sure their tool does it’s job properly.
As for why companies might choose to use this tool, a big reason is because Android is a huge target for fraud. Apple has locked all their stuff down so it is much harder to commit fraud on iOS (not impossible though). Although Apple offers something similar, there is generally less fraud coming from iOS devices vs Android. It’s the double-edged sword of having a more open platform.
Companies are obviously not going to be happy to be the target of fraud so they have to weigh their options. Either they block a small percentage of their users that are possibly legit by implementing Play Integrity API or they risk losing a % of their income to fraud.
Now you can disagree with the tool’s job, I’m not trying to argue whether the tool is good or bad. That is extremely subjective, but hopefully this answers why Google is making this change.
Yeah except that bot farms already use hardware that will pass the checks, unlike regular harmless users who will get hurt by this. Google comes after the good guys
Google’s updated Play Integrity API
How can these people talk about “integrity” when they break real existing phones?
I call this the opposite of integrity.
Bit hyperbolic, don’t you think? Rooted/Custom ROM users are so tiny, and they typically use security vulnerabilities to obtain root access. It’s not exactly surprising that Google closes those vulnerabilities when it can.
Google can’t exactly make root access and custom ROMs easier to use in 2025. It isn’t 2010 anymore - as soon as rooting becomes easy again, and people are bypassing security measures you know the big orgs, copyright holders and children’s apps will complain to the media and suddenly Google has a shitstorm to deal with.
Just wait until they find another vulnerability, lol.
Many devices, including Google’s own Pixel devices have user-unlockable bootloaders. No security vulnerabilities are involved in the process of gaining root access or installing a third-party Android distribution on those devices.
What’s going on here isn’t patching a vulnerability, but tightening remote attestation, a means by which a device can prove to a third party app that it is not modified. They’re selling it as “integrity” or proof that a device is “genuine”, but I see it as an invasion of user privacy.
Google can’t exactly make root access and custom ROMs easier to use in 2025.
Sure they can. They’re in a much stronger position to dictate terms to app developers than they were in 2010 when it was not yet clear there would be an Android/iOS duopoly.
They don’t want to though, because their remote attestation scheme means they can force OEMs to only bundle Google-approved Android builds that steer people to use Google services that make money for Google, and charge those OEMs licensing fees. A phone that doesn’t pass attestation isn’t commercially viable because enough important apps (often banking apps) use it.
Unlocked bootloader ≠ Root access.
Correct, but it is necessary to unlock the bootloader to gain root access without exploits.
deleted by creator
on devices running Android 13 or later.
Sounds easy then: stay on the latest Lineage that does not incorporate A13.
While I wouldn’t say Google is actively hostile towards these power users,
Author is obviously sold out. Are they even trustable?
I ain’t clicking on an android authority article. Does anyone know if/how this would effect Graphene?
Already does. Some apps just don’t work. It’ll notif. And say Google api failed to validate login to your Google account. Example app EBay.
deleted by creator
