Messaging Apps That Work Without Google Play Services
A messaging app without Google Play Services keeps working on de-Googled phones. Here's why most apps need FCM, which ones don't, and how they notify you.
By The PrivacyPortal Team
Yes, you can run a capable messaging app without Google Play Services, but the choice is narrower than it looks. Most mainstream apps lean on Google's push system for notifications, so on a de-Googled phone many of them either fall silent, drain your battery, or refuse to work at all. This guide explains why that happens and which apps are actually built to work without Google.
Why most messaging apps depend on Google Play Services
When someone sends you a message, your phone has to find out about it. On stock Android, apps almost never keep their own always-on connection open. Instead they register with Firebase Cloud Messaging (FCM), a component of Google Play Services. Google keeps one connection alive to your device, and every app piggybacks on it. When a message is waiting, the app's server tells Google, Google wakes the app, and the app fetches the message.
This design saves battery and is convenient for developers, but it has a cost: your notifications flow through Google's infrastructure, and the app simply stops delivering them if Play Services is missing. Even metadata like which app woke up, and when, passes through Google.
That is the crux of the problem for privacy-focused users. If you have deliberately removed Google from your phone, an app that depends on FCM has no way to reach you in the background.
The problem on de-Googled phones
De-Googled operating systems, GrapheneOS, /e/OS, CalyxOS, LineageOS without GApps, and similar ROMs, ship without Google Play Services by design. That is the entire point: no Google account, no Google telemetry, no Google push.
On these systems, an app that only knows how to receive notifications through FCM behaves in one of a few ways:
- It never notifies you until you open it manually.
- It nags you to install Google services.
- It silently fails to register and misses messages entirely.
Some ROMs offer compatibility layers (such as microG, which reimplements parts of Google's APIs), and that can revive FCM-style push for apps that insist on it. But relying on a Google-compatible shim is a compromise, not independence. The cleaner answer is an app that was never tied to Google in the first place.
How apps deliver messages without FCM
Apps that work without Google Play Services generally use one of three approaches:
- A persistent connection (foreground/background socket). The app keeps its own connection open to its server and receives messages directly. This is reliable and Google-free, at a modest, tunable battery cost.
- UnifiedPush. An open standard where you run (or choose) a distributor app that keeps a single connection alive, similar in spirit to FCM but self-hostable and not owned by Google.
- Periodic polling. The app checks for new messages on an interval. Simple and private, but notifications can be slightly delayed.
None of these require Google. The trade-off is usually a little more battery for a lot more independence and privacy.
Messaging apps that work without Google Play Services
Here is an honest, fair comparison of well-known options. "Runs without Play Services" means the app can send and receive in the background on a de-Googled phone, not just launch.
| App | Phone number required? | Runs without Play Services? | Notes |
|---|---|---|---|
| Signal | Yes | Yes | E2EE by default, open-source; falls back to its own connection when Google push is absent. Usernames can hide your number from other users; it still requires a number to register. |
| Session | No | Yes | Onion-routed, open-source, no phone number. |
| Threema | No | Yes | Paid, Swiss, open-source clients; offers a Google-free build. |
| Telegram | Yes | Yes | Requires a phone number. Cloud chats are not end-to-end encrypted; only opt-in one-to-one Secret Chats are E2EE. |
| Yes | Not designed for it | Meta-owned, ties you to a phone number, and is built around Google/Apple push. Message content is E2EE, but backups are not E2E unless you enable encrypted backups. | |
| Graphite | No | Yes | No phone number, no email; sideloaded APK with bundled Tor. |
A note on discontinued options: the consumer app Wickr Me was shut down by AWS at the end of 2023, so it is no longer a choice for individuals (AWS Wickr continues as a separate enterprise product).
If you want to go deeper on picking a private messenger overall, see our pillar guide to the encrypted messenger landscape. For phone-specific advice, our roundups of the best encrypted messenger for GrapheneOS and the best private apps for a de-Googled phone go further.
How Graphite handles messaging without Google
Graphite was built for exactly this environment. The Android app is a sideloaded APK that runs on GrapheneOS and other de-Googled phones with no Google Play Services present, and there is nothing to sign into with Google.
A few things make it fit the no-Google world cleanly:
- No phone number, no email. Your identity is a 12-word recovery phrase generated on your device. There is no account sitting on the server to tie to a Google profile.
- Its own network path. Graphite routes traffic over bundled Tor by default, fail-closed, to a hidden-service relay. Because it maintains that connection itself, it does not hand your notifications to Google's push system, and Tor hides your IP and network.
- Strong encryption. Messages are end-to-end encrypted with NaCl/libsodium sealed boxes, wrapped in a hybrid post-quantum layer (ML-KEM-768), with forward secrecy from a Signal-style double ratchet.
- A no-logs relay. The relay stores only sealed ciphertext with a 7-day maximum lifetime, deleted after delivery. It never sees your plaintext, your keys, or your recovery phrase.
Beyond text, Graphite handles encrypted group chats, file sharing, and encrypted voice and video calls (DTLS-SRTP). Call signaling travels over Tor, while the real-time call media connects peer-to-peer; on mobile, calls are routed so the other person does not see your IP. And because message search runs on your device, nothing is uploaded to search your history.
The result is a messenger that behaves the same whether or not Google is on your phone, which is the whole point of a de-Googled device.
The bottom line
If you are choosing a messaging app without Google Play Services, look past the app's marketing and ask one question: how does it reach you in the background? Apps that keep their own connection, or use an open push standard, will work on a de-Googled phone. Apps welded to FCM will not, at least not without a Google-compatibility shim. Signal, Session, and Threema are solid Google-free choices; Graphite goes a step further by dropping the phone number and routing everything over Tor.
Graphite is free and in public beta (v1.13.25), available on Windows, Android, and the web, with no phone number, no email, and no logs. Try it at graphite.chat.