DX Reminder on iPhone: How the Alerts Reach Your Phone

An Android phone or a computer can sit quietly in the background, ask the DX clusters every few minutes whether your wanted callsign has appeared, and ring when it has. An iPhone cannot. This difference is the reason why DX Reminder on iPhone works in a slightly different way from the other versions of the LY4A app, and understanding it explains both the strengths and the few limits of the iPhone version. This article follows an alert from the moment a spotter reports a station to the moment your phone shows it, describes exactly what the app and the LY4A site exchange, and lists the settings on the phone that decide whether the alert arrives when you need it.

Why the iPhone Needs Help

The iOS system is strict about what an app may do when it is not in front of you. An app that was closed or sent to the background is soon suspended, and it cannot keep a connection open or wake itself every minute to check a website. This protects the battery and is a sensible policy for most apps, but it is a problem for a tool whose whole purpose is to wake you when an event happens at an unknown moment. The Android, Windows and Mac versions of DX Reminder have no such problem and do the watching themselves, so those versions need no server of their own.

For the iPhone the LY4A site does the watching. The privacy page of the app puts it plainly: the iPhone app uses the site to watch the clusters for you, because the iPhone does not let an app do that itself. Your phone is therefore not the one asking the clusters; the site asks, and when it finds a match it asks Apple to deliver a message to your phone. Apple’s push service is the one channel that iOS does allow to reach a phone at any time, and it is the same channel that messaging and mail apps use.

From Spot to Screen: The Path of an Alert

The chain has five links, and it helps to know them if one day an alert is late. First, a station is spotted. A person reports it to a DX cluster, or a receiver reports it automatically, as described in our articles on automating DX spot alerts and on the Reverse Beacon Network. Second, the LY4A site checks the clusters every minute for the callsigns that its users are waiting for. Third, when a spot matches a callsign, a band and a mode that you have ticked, the site prepares an alarm for your device. Fourth, the alarm is sent through Apple’s push notification service to the token that identifies your phone. Fifth, iOS shows the notification on the screen according to your settings.

The once-a-minute check means that the delay between a spot and the alert is made of a short wait of up to a minute, the time the cluster itself needs to publish the spot, and the delivery time of Apple’s service, which is usually a few seconds. For a rare DX station that stays on the air for hours, or even for a pileup that lasts thirty minutes, this is well within the time that you need. The matched spots are kept on the site, so that the app can show you a list of them when you open it, and this list is useful when you were away and want to see what appeared.

What the App Sends to the Site

Because a server does the watching, the server must know what to look for, and the privacy page lists everything that is sent. It is an anonymous device identifier issued when the app first starts, the notification token that Apple assigns to the phone, the language of the app, the callsigns you watch with their bands and modes, and your alarm settings. That is all. The page states that none of it identifies you, because there is no e-mail address, no name and no account. The Android, Windows and Mac versions, in contrast, keep their data only on the device and send nothing to the site.

A practical consequence follows. Since there is no account, there is nothing to log in to and nothing to recover if you change phones. The reminders you set live with the app and the anonymous identifier, so if you install the app on a new iPhone you will have to enter the callsigns again. This is the price of not having an account, and for most radio amateurs, who watch a handful of callsigns, it takes a minute.

How Long the Site Remembers a Phone

The record of a phone that the site has not seen for six months is deleted automatically. So is the record of a phone whose token Apple reports as no longer valid, which happens when the app is deleted. Deleting the app makes the token invalid, so that no more alarms can be sent, and the record on the site is then removed automatically or at once on request. If you want to stop the alerts for a while without deleting anything, the simplest way is to switch off the reminders you do not need, or to turn off the notifications of the app in the iOS settings.

Settings on the Phone That Decide Everything

The app can send an alarm, but it is iOS that decides how and whether to show it, and a few settings deserve a look when you install the app. Allow notifications at the first start, because without permission iOS does not show anything. In the notification settings of the app, enable the lock screen, the banner and the sound. If you use Focus modes such as Sleep or Do Not Disturb, add DX Reminder to the apps that are allowed to interrupt, or the alert you set for the night will arrive silently. Check Low Power Mode too: it does not stop push messages, but it can delay background work for other apps and make the phone feel slower to react.

Also remember that the iPhone has a ring/silent switch and a volume that apply to notification sounds. A notification sound that is allowed in a Focus mode still follows the normal rules of sound for notifications, so test the alert once with the phone in the condition in which you expect to use it, for example on the bedside table with the screen off and the Sleep Focus active. The Android version has a stronger tool for silent phones, an alarm channel and a full-screen alarm, which we describe in the article on the silent phone and Android settings, and the iPhone relies on the rules of iOS notifications.

Bands, Modes and the Same Table

The reminders are set in a table: thirteen bands, from 160 metres to 70 centimetres including 60 metres, against five modes, which are CW, SSB, FT8, FT4 and RTTY. The changelog notes that the Android version has had the same table as the iPhone since version 4.4. A cell that is ticked is a separate promise: 20 m CW is independent from 20 m FT8, and the CW option means real CW only. The more precisely you fill in the table, the fewer alerts you receive that you did not want, and that matters even more on a phone that you carry everywhere.

The same site-side watching also works with the way the app is built: because the alerts come from the server, the app does not need to run in the background, and it does not drain the battery with frequent checks. This is an advantage over a phone app that polls, and the reason why the iPhone version can be quite economical. If you want to understand the sources and their delay, read our overview of PSK Reporter and of DX cluster spotting.

If an Alert Is Late or Missing

Work through the chain from the end. Is the notification permission still on, and is the app allowed in the active Focus mode? Does the phone have a data connection? Is the band and mode cell ticked for that callsign? A common reason for a missing alert is that the spot was for a different mode, for example the station was on 17 metres FT8 while the reminder was ticked for 17 metres CW. Was the callsign typed exactly as the DX station uses it, including a portable suffix? A station that operates as a special call or with a prefix may appear under a different string from the one you expect. The article on portable call sign suffixes shows how they look.

If everything on the phone is right and the station was clearly spotted, check whether you were chasing the right moment. The site looks for spots that are new; a station that was spotted an hour ago and has not been spotted again will not raise a fresh alarm. This is deliberate. A single appearance on the air is reported by many spotters, and the app is designed to give one alarm for the newest of them, with an interval of your choice before the same combination rings again.

Why a Once-a-Minute Check Is Enough

It is natural to ask whether a minute is too slow for a hobby in which seconds sometimes count. The answer depends on the kind of chase. A new DXCC entity on a DXpedition is normally on the air for days or weeks, and even the busiest pileup on a single band lasts many minutes, so an alert that arrives within a minute or two of the first spot leaves you plenty of time to sit down, tune the radio and make the call. The cases where seconds decide, such as a brief opening on 6 metres or a rare station that appears for a short test, are those where you are probably at the radio already. For everything else the point of the alert is to free you from watching a screen, and a delay of a minute does not change that.

It also helps to remember that the delay of the cluster itself is often larger than the delay of the app. A human spotter may need a minute or more to notice a new station and type the spot, and automatic receivers publish their reports in their own rhythm. The alert from the phone therefore reaches you close to the moment when the information first becomes public, which is the best that any alerting tool can do.

A Practical Setup in Five Minutes

Install the app from the App Store, which requires iOS 16 or newer, and start it. Allow notifications. Add the callsign you are waiting for, then fill in the table for the bands and modes where you expect it, and leave the rest empty. Choose the alarm interval that suits the way you chase: a short interval for a rare new one, a longer one for a station that will be on the air for days. Test with a callsign that is active right now, so that you see a real alert. Then go about your day, because the point of the whole exercise is that you no longer have to look at a cluster page.

The Bottom Line

DX Reminder on iPhone relies on the LY4A site to watch the clusters every minute, because iOS does not let an app do this in the background. When a spot matches a callsign, band and mode that you ticked, the site sends the alarm through Apple’s push service. The app sends only an anonymous device identifier, the notification token, the language, your callsigns with bands and modes and your alarm settings, with no account, e-mail or name, and a record unused for six months is removed. The notification and Focus settings of iOS decide how the alert looks and sounds, so set them once and test them.

Frequently Asked Questions

Why does DX Reminder on iPhone use a server?

iOS does not allow an app to keep watching in the background. The LY4A site checks the clusters for you every minute and sends a push notification when your callsign appears.

Do I need an account to use it on iPhone?

No. The app uses an anonymous device identifier, and there is no e-mail address, name or account.

What does the app send to the site?

The anonymous identifier, the Apple notification token, the language, the callsigns with their bands and modes, and your alarm settings.

What happens to my data if I delete the app?

The notification token becomes invalid, no more alarms can be sent, and the record on the site is removed automatically, or at once on request.

Which iOS version does it need?

The App Store listing for the app asks for iOS 16 or newer, and it runs on iPhone and iPad.

Why did I not get an alert for a station that was spotted?

Check the permission and the Focus mode first, then whether the exact band and mode cell is ticked and the callsign is typed as the station uses it.