De-Googling Android is possible, but Revolut and Play Services block the exit

A user attempting to fully de-Google a Pixel 7a found the project stalled by banking and app compatibility, most notably Revolut requiring Play Store installs. The report, posted to r/degoogle and discussed on privsec.dev, shows that removing Google Play Services still breaks day to day banking for many Europeans.

Before this thread emerged, advocates of GrapheneOS and other non-Google Android builds framed de-Googling as a realistic privacy upgrade for power users. Projects such as GrapheneOS, app stores like F-Droid, and alternative front ends such as Aurora Store promised a Google-free experience, provided the apps you need are available without Play Services. That promise now collides with commercial realities, where major finance apps intentionally require Play Store installation or rely on Google Play Services for functionality and security checks.

Banking Blocks the Exit

The concrete technical blocker is not Android itself, it is the app ecosystem. The poster tried to run a Pixel 7a without Google Play Services, then discovered key apps either refuse to run or demand a Play Store install. Revolut is the clearest example, with error paths that read "requires installation through the Play Store" and runtime checks tied to Google Play Services. That pattern repeats in a number of mainstream apps, turning a privacy project into an operational liability for anyone who needs mobile banking on a single device.

The implication is binary for many users. If you rely on Revolut for daily payments, subscriptions, or business expenses, you will either lose access to those functions or carry a second device with Google Mobile Services. The user in the thread explicitly rejected a two phone workflow. This makes a full switch impractical for most professionals.

Workarounds and the trade-offs

There are three realistic paths forward today, each with clear trade-offs. First, accept a compromise and keep Google Play Services sandboxed or use a microG replacement, knowing this reintroduces attack surface and vendor dependency. Second, use alternative hardware that ships without Google services such as FairPhone or a ShiftPhone, then vet every essential app for compatibility, which requires time and technical capacity. Third, press app vendors to support non-GMS environments, a long term policy and procurement task that will not deliver immediate relief.

Tools like F-Droid and Aurora Store reduce friction but do not solve server side checks or Play Store based installation requirements. The compatibility report mentioned in the thread included a comment dated "one month ago" documenting similar failures, which shows this is an ongoing, not a one off, problem.

Why This Matters

For European IT and security teams, this is a practical constraint, not a philosophical one. If your staff uses Revolut, or banking apps that require Google Play Services, you should not mandate a Google-free phone without a remediation plan. Teams choosing GrapheneOS or FairPhone must catalogue every critical app and either accept a secondary device, select alternative banking providers, or fund vendor changes. Any compliance or procurement lead planning a mass migration away from Google should now treat banking compatibility as a blocker, not a feature request.

Sources

https://www.reddit.com/r/degoogle/comments/1ripyfo/possible_to_actually_degoogle_a_phone_without/

https://privsec.dev

https://www.reddit.com/r/europrivacy/comments/1rf8qpb/european_parliament_blocks_ai_on_lawmakers/

https://tech.eu/2026/02/24/the-new-era-of-shopping-raises-14m-pre-seed-to-help-brands-win-in-the-age-of-agentic-commerce/

https://tech.eu/2026/03/03/from-mac-utilities-to-ai-ecosystem-macpaws-next-act/