APRSdroid vs APRS World — Choosing an Android APRS App in 2026

If you are an Android-using ham looking for an APRS client in 2026, two names show up most often: APRSdroid — the open-source, F-Droid-friendly app that has been the default for over a decade — and the newer APRS World mobile app that pairs a native UI with the same Tier-2 backbone that powers aprs.world in the browser. Both are good choices. Neither is "better" in the abstract; they are aimed at different workflows.

This guide is a neutral, respectful tour of how the two apps compare in 2026. APRSdroid is a beloved piece of amateur radio software, the work of many years of careful engineering by Georg Lukas (DO1GL), and we are not here to trash it. Our goal is to help you understand what each app is best at so you can pick the one that fits your operating style — or, as is increasingly common, install both and use them for different things.

TL;DR

Need	Pick
Maximum stability, minimal footprint, F-Droid friendly	APRSdroid
Native messaging UX with conversation threads	APRS World
11-language UI (English, Turkish, German, French, Spanish, Italian, Russian, Chinese, Japanese, Portuguese, Dutch)	APRS World
Long history, established community, time-tested codebase	APRSdroid
Modern Material Design dark theme	APRS World
Bluetooth KISS TNC with daily-driver Anytone/Yaesu coverage	Both
Audio-coupled AFSK / soft-modem	APRSdroid (mature)
Web + mobile parity (same map, same station pages, web bookmarks open in app)	APRS World
Premium-free, donation-funded forever	APRSdroid

Most operators end up installing both. APRSdroid for the lean F-Droid build that runs 24/7 in the background, APRS World for the moments when you want a polished visual experience or you are messaging an operator who is on the web visualizer.

APRSdroid — The Established Choice

APRSdroid was first released in 2010 by Georg Lukas (DO1GL) and has been actively maintained ever since. Its design priorities have remained remarkably consistent: do one thing (be an APRS client on Android) and do it reliably with the smallest reasonable footprint. It is open source under the GPL, with source and signed APK releases on GitHub for users who avoid Google Play, and has a small but dedicated upstream community.

What APRSdroid does well

Stability. Many users run APRSdroid 24/7 on an old Android handset wired to a TNC and never reboot it. The release cadence is slow and conservative; bugs are rare.
Audio AFSK / soft-modem. APRSdroid is one of the very few clients that can decode and transmit APRS using only the phone's microphone and speaker coupled to a radio. No TNC needed. Compatibility varies by phone audio hardware, but when it works, it is the cheapest possible APRS path.
Lean footprint. The APK is small, RAM usage is modest, and it runs on older Android versions other modern apps have dropped.
F-Droid availability. For operators who prefer fully libre stacks and no Google Play dependencies, F-Droid distribution is a significant advantage.
TX-capable iGate mode. APRSdroid can act as a personal iGate, gating its own RF receptions to APRS-IS.
Tasker / automation friendly. APRSdroid exposes Tasker intents and is easy to script into a wider home-automation setup.
Hardware coverage. Supports a wide range of Bluetooth and USB-serial KISS TNCs — Mobilinkd, Bluetooth-classic radios, USB-OTG cables to a TNC.

Where APRSdroid is showing its age in 2026

The UI is largely the same as it was several years ago — functional, but not styled to modern Material Design conventions. The map is OpenStreetMap-based via osmdroid and works well, but the visual polish lags 2026 expectations.
Conversation threading for messages is basic — you can read messages and reply, but the UI does not group multi-turn conversations the way modern messaging apps do.
Localisation is limited compared to multilingual modern apps; the primary UI is in English with community translations of varying completeness.

None of these are deal-breakers. They are tradeoffs that follow naturally from APRSdroid's "stable, minimal, do-one-thing" design philosophy.

APRS World Mobile — The Native Companion to the Web Visualizer

The APRS World mobile app is the native Android (and iOS) companion to the aprs.world web visualizer. It launched alongside the web app in 2026 and was designed from day one to share the same backend, the same map style, the same station pages, and the same data model as the browser experience. The goal was simple: if you bookmark a callsign in the browser, the same bookmark should open in the app, and vice versa.

What APRS World mobile does well

Modern UI. Material Design 3 dark theme by default, MapLibre vector tiles, smooth panning and zooming, animated marker transitions. The visual experience matches what 2026 users expect from a mobile mapping app.
Conversation-threaded messaging. Messages are grouped per-callsign into proper conversation threads, the way you would expect a messaging app to work. Sent / delivered / ACKed state is shown per-message.
11-language UI. English, Turkish, German, French, Spanish, Italian, Russian, Chinese, Japanese, Portuguese, Dutch — all bundled, all maintained. The web visualizer ships the same 11 locales, so the experience is the same in every supported language across both platforms.
Web + mobile parity. A station's permalink in the browser (/station/TA4OHN-9) opens directly to the same view in the app via deep linking. Search history syncs if you sign in.
Bluetooth KISS TNC support. Daily-driven with the Anytone AT-D578UV, AT-D878UV, and other modern radios that expose a Bluetooth-classic SPP profile. Wireless link, no USB-OTG cable, no dongle.
In-app live map. The same MapLibre vector tile stack as the web app, with marker clustering and a country-frequency overlay that pulls from the frequencies-by-country reference.
Premium tier (optional). A small set of advanced features (saved long-term alerts and similar) sits behind an optional Premium tier. Every core APRS-viewing function — map, station pages, messaging, search — is free for everyone.

Where APRS World mobile is still maturing

Younger codebase. It does not have APRSdroid's decade of in-the-field hours yet. Some edge cases — exotic TNC chipsets, rare AX.25 framings — are not as battle-tested.
No audio-coupled AFSK in stock builds. The soft-modem path is experimental and disabled in shipped releases; the supported transports are Bluetooth KISS and APRS-IS upload. Pure-audio operation will likely become viable later (see our roadmap notes).
iOS Bluetooth KISS is gated by Apple's MFi programme. On iPhone, the app is currently APRS-IS only; the Bluetooth KISS workflow is Android-only. This is an Apple constraint rather than a software gap.
Not on F-Droid. Shipped through Google Play and the App Store rather than F-Droid; the build artefacts target the commercial stores.

Feature-by-Feature Comparison

Feature	APRSdroid	APRS World mobile
Open source	Yes (GPL)	No
F-Droid	Yes	No
Play Store	Yes	Yes
App Store (iOS)	No (Android-only)	Yes
Bluetooth KISS TNC	Yes	Yes (Android)
USB-OTG serial TNC	Yes	Roadmap
Audio-coupled AFSK	Yes (mature)	Experimental, disabled in release
APRS-IS upload	Yes	Yes
Map style	OSM raster (osmdroid)	MapLibre vector tiles
Conversation-threaded messaging	Basic	Yes
Message ACK/RETRY UI	Yes	Yes
Station search	Yes	Yes
Multilingual UI	Limited	11 languages
Dark theme	Yes	Yes (default)
Web visualizer companion	No	Yes (aprs.world)
Deep linking from web	No	Yes
Personal iGate mode	Yes	Roadmap
Tasker integration	Yes	No
Premium tier	No (donation-supported)	Optional, small

This table is not "APRSdroid loses 3-7". Each row reflects a deliberate design choice. APRSdroid's strengths (F-Droid, AFSK, Tasker, longevity) come from a tight focus; APRS World's strengths (modern UI, multilingual, web parity, deep linking) come from being a recent rewrite paired with a web product.

Who Should Pick Which

Pick APRSdroid if:

You are an open-source purist and want an F-Droid-distributed app.
You want to do audio-coupled AFSK from a phone and a handheld with no extra hardware.
You run a phone as a 24/7 personal iGate and want a battle-tested codebase you can leave running for months.
You use Tasker or other Android automation tooling to integrate APRS with home automation.
You prefer the established choice and don't mind older UI styling.

Pick APRS World mobile if:

You use the aprs.world web visualizer and want a native app that shares its bookmarks, station pages, and messaging history.
You message APRS contacts often and want a proper conversation-thread UI.
You operate in a non-English language — Turkish, German, French, Spanish, Italian, Russian, Chinese, Japanese, Portuguese, Dutch — and want a fully localised app.
You have a modern Bluetooth-KISS-capable radio (Anytone AT-D578UV, AT-D878UV, etc.) and want a polished wireless workflow.
You are on iOS — APRSdroid is Android-only.

Pick both if:

You want APRSdroid's lean 24/7 iGate role on an older phone, and APRS World's polished UI on your daily-driver phone.
You want to be able to send and receive APRS messages while travelling, but also leave a long-running tracker app running at home.

There is no operational conflict in running both. They are clients of the same APRS-IS feed, and they don't interfere with each other.

A Note on Tone

We want to be explicit about something. APRSdroid is genuinely a great piece of software. It carried Android APRS users for over a decade when there were no good alternatives, and it remains the right tool for several specific workflows. The APRS World mobile app exists not to replace it, but to provide a complementary option for operators who want a modern UI, multilingual support, and tight integration with the aprs.world web visualizer.

We have no interest in framing this as a competition. The APRS community is small enough that "more good clients" is just good for everyone.