Can You Actually Live on an Open-Source Phone? We Tested the Apps You Can't Imagine Losing
Photo: Explain That Stuff, CC BY-SA 2.0, via Wikimedia Commons
Let's be honest with each other for a second. The ideals behind open-source mobile are genuinely compelling — you own your device, your data isn't being harvested for ad targeting, and you're not locked into an ecosystem designed to keep you spending. But ideals don't deposit your paycheck or let you check in for your flight. Apps do.
So we decided to skip the philosophy and get practical. We spent several weeks testing the categories of apps that most US users consider non-negotiable, running them against QtMoko and comparable open-source platforms. The results are more nuanced than the "it just works" crowd admits — and more promising than the skeptics expect.
Banking Apps: The Toughest Nut to Crack
This is where open-source mobile hits its most frustrating wall, and we're not going to sugarcoat it. Major US banking apps — Chase, Bank of America, Wells Fargo, and most credit union apps — rely heavily on Google Play Integrity API (formerly SafetyNet) to verify that your device hasn't been tampered with. From their perspective, a rooted or non-certified device looks like a security risk, so they simply refuse to launch.
The workaround situation is real but imperfect. Tools like Magisk's DenyList can sometimes fool these checks, and certain custom builds include microG, an open-source reimplementation of Google's core services that passes basic attestation on some apps. Results vary wildly by bank and app version, and what works today might break after the next update.
The genuinely good news: most banking websites are fully functional through a modern mobile browser. Depositing checks via the web interface is available at many major institutions, and for day-to-day balance checks and transfers, the browser experience is honestly fine. Credit unions that offer progressive web apps (PWAs) are your best friends here. If you're willing to do your mobile banking through a browser tab, this barrier shrinks considerably.
Verdict: Workable with adjustments, but expect friction. If your bank's app is your financial lifeline, test it before you fully commit to switching.
Communication: Surprisingly Strong Territory
This is where open-source mobile genuinely shines, and it's not a coincidence — privacy-first communication tools were practically built alongside this movement.
Signal works flawlessly. Element (Matrix protocol) runs smoothly. Telegram functions without a hitch. For video calls, Jitsi Meet is available as a standalone app and delivers reliable performance for most calls. Even WhatsApp, which requires Google Play Services in some configurations, can often be sideloaded and coaxed into working through microG implementations.
The trickier spots are proprietary enterprise tools. Microsoft Teams and Zoom have Android apps that range from "mostly functional" to "frustratingly buggy" depending on your build. For Zoom specifically, the web client through Firefox or Chromium-based browsers on QtMoko handles standard meetings well — screen sharing is the main casualty. Teams is more stubborn, though the web version covers most use cases for non-corporate accounts.
For anyone willing to nudge their contacts toward open alternatives, this category becomes a strength rather than a weakness. XMPP clients like Conversations, Matrix clients, and even good old email via FairEmail or K-9 Mail are polished, fast, and genuinely pleasant to use.
Verdict: Strong, especially if you're already leaning toward privacy-respecting communication tools.
Productivity: Better Than You'd Think
Google Docs, Sheets, and Drive — the productivity holy trinity for a huge chunk of American workers — function through the browser with surprising competence. Editing a shared document on the go isn't the nightmare you might expect. Offline access is trickier, but Nextcloud with its Android client (available via F-Droid, the open-source app store) provides a genuinely excellent self-hosted or third-party-hosted alternative for file sync and office documents.
OnlyOffice and Collabora (based on LibreOffice) both have solid Android builds that handle .docx and .xlsx files without the formatting disasters that plagued earlier open-source office suites. For task management, apps like Tasks.org (syncs with CalDAV and various open protocols) and Orgzly for the Org-mode devotees among you are legitimately excellent.
Calendar and contacts sync through DAVx5 is smooth and well-documented. Once it's set up, it genuinely gets out of your way.
Verdict: Solid, with a small setup investment upfront that pays off quickly.
Navigation and Transit: A Mixed Bag
Google Maps is unavailable natively, but here's where the open-source world has quietly built something impressive. OsmAnd, based on OpenStreetMap data, handles turn-by-turn navigation and offline maps with a feature set that rivals Google Maps for most everyday routing. It's not as pretty, and real-time traffic data is less comprehensive, but for getting from A to B across the US, it works.
Organic Maps is a leaner, faster alternative for users who primarily need walking and cycling directions. For public transit in major US cities, Transportr aggregates GTFS data and covers most metro areas reasonably well — though smaller cities can be hit or miss.
Rideshare apps (Uber, Lyft) can sometimes be sideloaded with microG handling the background services, but this is one of the less reliable compatibility stories. If ridesharing is a daily necessity rather than an occasional convenience, factor that in.
Verdict: Navigation is genuinely solved. Rideshare apps remain a gamble.
The Honest Bottom Line
Switching to an open-source mobile platform in 2024 is feasible for a lot of people — but not for everyone, and not without some deliberate adjustment. The users who thrive are those willing to swap a handful of familiar apps for open-source equivalents, lean on browser-based versions of holdout services, and accept that a small number of apps may simply never cooperate.
The users who struggle are those with hard dependencies on specific banking apps, enterprise communication platforms, or niche regional services built on Google's infrastructure.
The honest framing isn't "open-source phones can do everything your current phone does." It's closer to: "Open-source phones can do most of what matters, differently, and with more transparency about what's happening under the hood." For a growing number of Americans, that tradeoff is starting to make a lot of sense.
Start with F-Droid. Explore microG if your must-have apps require Play Services. And before you make the full leap, spend a week cataloging which apps you actually open versus the ones just sitting on your home screen taking up space. You might be surprised how short that first list really is.