WoAD

Review by eFreeware

WoAD is an Android app from Sumus Technology Ltd that turns a phone or tablet into a client for the Winlink global radio email system, the network amateur radio operators use to pass messages over the air. It also connects directly to a peer-to-peer capable client. The main reason to consider it is simple: if you already run Winlink on a computer and want the same capability in a device you carry, this is built for exactly that job.

It sits in the Communication category and has been on Google Play since April 2024, with an update in late August 2026. The install base is modest at over 5,000, and the rating sits at 4.2 from a small pool of 12 ratings. That is a narrow audience by design, because the app is written for licensed amateur radio operators rather than a general messaging crowd.

The developer is upfront that this is technical territory. WoAD is described as highly technical, in the same way much of ham radio is, and the learning curve for anyone new to packet radio or Winlink is called steep and potentially frustrating. That framing matters more than any feature list here, because it tells you what kind of person gets value from the app and what kind of person bounces off it.

Radio email as the core of the app

Its main job is to connect to the Winlink radio email network. In practice that means composing and handling messages that travel through the Winlink network rather than a conventional email provider. The developer's own summary puts it as bringing Winlink functionality to an Android device, and the rest of the app is organized around that single purpose.

There are two ways it reaches the network. One is over the internet, which is the path most people will recognize from ordinary messaging apps. The other is a VHF/UHF AX.25 packet connection, the radio route that gives the app its reason to exist for operators working away from reliable data coverage. Which one you use depends on your station and your license privileges.

The app can also connect directly to a peer-to-peer capable client. That is a different mode from going through the Winlink system, and it matters for operators who want a direct link between two stations rather than a message handed into a network. Between the internet path, the packet path and the peer-to-peer path, the developer has covered the main ways a ham would want to move traffic from a handheld device.

What appeals to me about this structure is that it does not try to be a general-purpose messenger with radio bolted on. It is a Winlink client first, and the connection options are the ones the Winlink world actually uses. If you are already comfortable with that world, the shape of the app will feel familiar rather than novel.

Support channels and recent fixes

Around the core function, the developer has put together a set of resources for when something goes wrong. There is documentation, which is described as always expanding, a support group where other WoAD users may be able to help, a bug report page, and a feature request page for when the app is missing something useful or doing something irritating. That last one is a refreshingly blunt way to frame feedback.

The support group is worth noting because it is a community of users rather than a formal help desk. For a niche radio app, that kind of peer knowledge is often where the real answers live, particularly for questions about station setup and connection troubleshooting. The bug report page is aimed at problems with WoAD itself, and the developer asks people to submit reports even for small things like a typo, on the grounds that everyone benefits.

The most recent update shows the app is still being worked on. It fixes Bluetooth permissions for Android 11 and earlier, and adds a notification when Bluetooth is not switched on at the point where you select a Bluetooth TNC. Both are small, specific changes, but they point at the kind of friction that matters in this app: getting the radio link to a terminal node controller working before anything else can happen.

I would treat the documentation as part of the app rather than an optional extra. The developer strongly encourages reading it before use, and given how the connection paths work, that advice is not boilerplate. Going in cold with a packet setup is likely to be a poor first experience.

What WoAD asks of you

The first requirement is a license. You need an amateur radio license, or one from a government service that takes part. Three license types are excluded: ship station, marine and general radiotelephone. This is not a formality you can work around later; it is the condition for using the app at all, and the developer asks people not to install or download it without one.

The second requirement is money. WoAD is a paid app at $8.49, with no ads and no in-app purchases. That is a straightforward arrangement: you pay once for the app and there is nothing further to buy inside it. For a tool aimed at a licensed technical hobby, a single up-front price is easier to reason about than a subscription, and it matches how most radio software is sold.

There is also a free route. The developer offers an APK file on its own site that you can install at no cost. That is worth knowing, though it means stepping outside Google Play for the install. The paid listing remains the ordinary path for most people.

The third requirement is patience. The developer describes the app as highly technical and warns that the learning curve may be steep and frustrating for those unfamiliar with packet radio or Winlink. That is not a disclaimer tacked onto the bottom of a store page; it is an honest description of what the app demands from the person using it.

Getting started without the frustration

The practical advice the developer gives is to read the documentation before use, and to treat it as the first place to look when something does not work. For an app with multiple connection paths and radio hardware in the loop, that order makes sense. Understanding what the app expects from your station before you start configuring anything will save a lot of guesswork.

If you do hit a wall, the escalation path is laid out. Documentation first, then the support group of fellow users, then a bug report if the problem is with WoAD itself, and a feature request if the app is getting in your way. Knowing which channel to use keeps you from filing a bug report about a station configuration issue, which helps you and helps the developer.

Because the app talks to radio equipment, the Bluetooth side deserves attention. The recent change that notifies you when Bluetooth is off at the moment you pick a Bluetooth TNC is exactly the kind of prompt that prevents a confusing dead end. If you are on Android 11 or earlier, the permission fix in the same update is relevant.

The realistic picture is that WoAD rewards preparation. Operators who already know their way around packet radio and Winlink will find the app slots into habits they have. Those coming to it fresh should expect to spend time with the documentation and the support group before the app feels natural. The developer's own warning supports that expectation rather than contradicting it.

A tool for licensed operators who already know the territory

WoAD is a focused app with a clear audience. The developer's documentation, support group, bug report and feature request pages round out the package for people who need help along the way.

The fit is narrow and honest about it. The developer calls the app highly technical and warns that newcomers to packet radio or Winlink may find the learning curve steep and frustrating. Anyone without that background should weigh that warning carefully before paying.

For a licensed operator who already works with Winlink and wants it on a device that goes where the radio goes, the app does what it says. The small install base and the modest rating count reflect a specialist tool rather than a mainstream one, and the recent update suggests the developer is still tending to the details. My recommendation is for ham operators who know the Winlink workflow and want a mobile client for it; everyone else is better served getting licensed and learning the system first.

What's new in version 1.6.15

Fix Bluetooth permissions for Android 11 (API 30) and earlier Add support for notifying user if Bluetooth is not switched on when selecting Bluetooth TNC