Features

Messaging

• One conversation per station, kept in order, whichever of its SSIDs writes. A reply goes to the SSID that wrote last, and you can pick another; Settings > Messages keeps each SSID in a conversation of its own instead. Five thread kinds: direct, service, bulletin, SMS, and net rooms.
• Six delivery states per message: queued, sent, digipeated, delivered, rejected, not delivered. Digipeated is confirmed off the air: the app matches its own packet coming back through a repeater, which is proof it was radiated.
• Automatic retries on a schedule you set. By default the first retry comes after 30 seconds and each one after waits 30 seconds longer, up to a five-minute ceiling, for six attempts, with up to 5 seconds added to each at random; the interval and the number of attempts are under Settings > Messages. Messages still in flight when the app is killed are picked up and resumed on relaunch.
• Where messages go: on every connected link at once (the default), on the radio first and then APRS-IS, on APRS-IS first and then the radio, or on one link only. The commands the APRS OTA bot only counts off the air always go on the radio.
• Failed messages show a retry button on the bubble itself, and the thread list flags the conversation.
• Retry when heard (Pro): a message that has run out of retries can wait for its station to be heard again, then try once more, up to three tries over two weeks, spaced out so they are not all spent in one evening. It watches for the exact callsign and SSID, reuses the same wire ID so a late acknowledgement still matches, and only the final failure notifies. The Retry button itself is free; Pro adds the automatic watch.
• A Waiting to be heard screen lists every message waiting for its station, with tries left, the date the watch lapses, and a Stop waiting button. It is reached from a banner on the message list or its tile in the drawer. The failure notification's own buttons (Retry now, Retry when heard, Stop waiting) act without opening the app.
• Stop sending a message mid-retry, and the app tells you what actually happened: stopped in time, a copy already went out, a digipeater repeated it, or it was already delivered.
• Retransmit any message. Pending ones reuse the same wire ID so a late acknowledgement still matches; answered ones go out as a new message.
• Incoming messages addressed to you are acknowledged automatically. Duplicate retransmissions are acknowledged again but don't re-notify.
• A live byte counter against the APRS 67-byte limit; longer text is split into parts automatically and sent in full before any part is retried, and a multi-part send reports the state of its least-delivered part.
• A web address in a message is a link that opens in the browser.
• Message templates in four groups (everyday, POTA/SOTA, nets, emergency).
• Search across every message ever stored, with matches highlighted and inbox and archive results separated.
• Thread list filters by kind, with counts; the selection persists across launches.
• Per-thread mute, archive, block, and delete. Muted threads keep their unread count, so a muted thread still shows what is unread without making a sound.
• Unread boundary line and day dividers in every thread; a jump-to-latest button when you've scrolled up.
• Thread headers show when the station was last heard and its distance and bearing from you, or "not heard yet", never a made-up value.
• SMS conversations can be named locally, and you can set the alias the gateway knows you by.
• Bulletins are collected into one room per group, with each one attributed to the station that sent it. You can post your own: a general bulletin, or one addressed to a group (WX, a club, an event).
• Ask any station where it is with the standard ?APRSP position query, straight from its page. The request is tracked like any message, and the answer arrives as a fresh position, not a chat bubble.
• The compose screen covers every network from one place: radio, plus each message gateway (SMS, email, Winlink, WhatsApp) with per-channel validation and recipient formats. Callsign suggestions come only from stations actually heard.
• Your other callsigns (Pro): messages sent to your other SSIDs, such as a digipeater on another box or the radio in the car, arrive on this device and can be answered from it, in conversations of their own or merged into your station's. Acknowledging them is a switch per callsign, off by default. Under Radio > Station identity.

Services

• A built-in directory of 22 APRS services, each presented as a guided screen: what it does, who runs it, and forms for each command, with no syntax to memorise.
• The exact packet each button will send can always be shown before sending (a settings toggle), and you can always type a command by hand instead.
• Nets & groups: #APRSThursday, the #APRSThursday logger (APRSPH), ANSRVR group messaging, MAIL mailboxes, IRC-style channel chat, and CQSRVR.
• Gateways: SMS text messages, Winlink email (APRSLink), the email gateway, a WhatsApp gateway, and ARRL NTS radiograms filed as a guided multi-message exchange.
• Missed messages: register with the QRX mailbox and messages sent while you were off the air wait for you. The app shows how many are waiting and pulls them down.
• Activations: APSPOT self-spotting to POTA, SOTA, WWFF and SiOTA, and APRS2SOTA for SOTAwatch spots.
• Weather: WXBOT forecasts (by your beaconed position, city, ZIP, grid, or callsign) and WXNOW current conditions from the nearest weather stations.
• Utilities: WHO-IS callsign lookup, the MPAD multi-purpose bot, the REPEAT repeater finder, the 9M2PJU-4 all-in-one bot, and JOKE, which sends a joke to your radio.
• WHO-IS, REPEAT, WXNOW, and APRS OTA get purpose-built screens rather than generic forms.
• Replies from a service thread back like any conversation, with the same delivery tracking.
• A reachability note warns when a service appears to be RF-only or offline and a reply may not come. It warns; it doesn't block.
• Services that haven't been verified against the live bot are labelled as unconfirmed in the directory.
• The directory is data, not code: export it as JSON, edit or add services, and import, with a preview of exactly what will change and a one-tap reset to the built-in set.

Groups & nets

• A directory of ANSRVR groups: browse what exists, what each is for, and which you've joined.
• Joining a group turns it into a net room: everyone's traffic collected into one conversation instead of a thread per stranger, with your check-in status and time remaining shown at the top.
• Check in, renew, post to the group, and leave from one screen; a roster shows the operators heard in the net.
• A net room says how many are on the net right now, with the count's age, and who has spoken tonight. Where a net asks for a locator in the check-in, the room shows it.
• #APRSThursday is wired in as the weekly net it is, including logging a check-in without relaying it to the whole group.
• A weekly #APRSThursday reminder, turned on from Settings or from the net room. You pick the time; the app picks the local day on which that time falls inside the UTC Thursday, and shows the date of the next one.

APRS OTA

• Host an op from anywhere: one tap announces you on the air through the aprsota.org bot.
• Callers arrive as cards with their message and location; confirming a contact is one tap plus an optional note, and the screen shows your QSL count and time remaining, with a button to extend. A confirmed contact shows what you and the chaser said.
• The op clock counts the QSLs the bot answered, and the wrap-up shows how many of your calls it left unanswered.
• Chase from the same screen: one tap sends CQ to ask the bot who is on the air right now, hosts you've already worked are check-marked, and the default chase message is yours to edit.
• The chase list can come from the internet instead of the bot: the ops listed on aprsota.org, with each op's number, start time and a live countdown, refreshed once a minute. A host who has started a new op is no longer shown as already worked.
• Each op has a map of its stations, at the positions the server reports, with the distance to each.
• The host and chase screens have a BLAST box for a message to everyone in the op.
• A beacon button in the APRSOTA conversation sends your position without leaving it.
• The exact packet each action will transmit is shown on the button.
• Works entirely over RF: the phone talks to the radio, the radio carries the rest. Chasing also works over APRS-IS without Pro; hosting needs a radio, because the bot only counts a HOST it heard on the air.

Radio & connectivity

• APRS-IS is free; the radio channels are Pro. Every radio type is still listed on the Add channel sheet without Pro, and choosing one opens the plans. When Pro lapses, a radio channel stops being brought up and its row says why; APRS-IS stays connected and nothing is deleted.
• Several radios at once, as named channels. Each connection is a channel: name it "Truck" or "Shack Direwolf", give it a type, switch it on. Local links (Bluetooth, BLE, USB, audio) run one of each; network links run in any number, including more than one APRS-IS session. Every frame in the packet log is tagged with the link that carried it.
• Bluetooth Classic KISS TNCs: paired devices listed with likely TNCs sorted first.
• Bluetooth Low Energy KISS TNCs: a Mobilinkd TNC4 in LE mode, a B.B. Link, a Tidradio TD-H9 (iPhone and Windows for now), or anything speaking the published BLE KISS profile. A live scan rather than a paired list, because a BLE TNC never appears in Android's own Bluetooth settings; devices advertising the KISS service are flagged as likely TNCs.
• LoRa APRS trackers (iPhone for now): a tracker running CA2RXU's firmware connects over Bluetooth LE as the radio, in KISS or plain text, and a LoRa iGate's text feed can be heard through a Network TNC channel.
• USB serial KISS TNCs over a USB cable: a TNC4's USB-C port, a TH-D74/D75 in USB KISS mode, TNC-X and TNC-Pi boards, Direwolf boxes, and homebrew serial TNCs. The DTR line is remembered per device, because radios differ on whether they need it, and the baud rate is picked from a list, because a mistyped rate still connects and then delivers unreadable data.
• A Mobilinkd TNC's battery is shown on the Radio screen and on the RF chip, as a percentage beside the voltage the TNC reported, with a notification when it runs low. Only a channel whose device is a Mobilinkd is asked.
• An audio modem, with no TNC at all. A built-in software AFSK 1200 modem: cable the phone's audio to any radio and the app decodes and generates the packet tones itself. Transmit keys the radio by VOX or by wired PTT through a USB serial adapter, with a stuck-transmitter watchdog. It waits for a clear channel before keying, detecting other packet traffic by its framing so an open squelch doesn't read as busy. If Android routes audio to the built-in microphone instead of the cable, the screen says so.
• KISS over TCP for Direwolf or a network TNC. Every KISS channel has a KISS port, so a TNC that serves two radios over one connection becomes two channels, each hearing and transmitting through its own radio.
• IGate (Pro): the phone passes traffic between the radio and APRS-IS. Radio to internet costs no airtime and can be narrowed to packets heard direct. Internet to radio transmits only for stations the radio has actually heard, so a gate in a quiet area never floods the channel with the whole world's traffic. The two directions are separate switches.
• Digipeater (Pro): the phone repeats what the radio hears back onto the air, as a fill-in or a wide-area digipeater. A fill-in waits five seconds and stays quiet if another digipeater repeated the packet first, so it fills gaps in coverage rather than repeating what a nearby digipeater already carried. Runs alongside the IGate, or without it.
• APRS-IS over the network: regional Tier-2 server presets or any host you type, with the receive filter shown and editable. The passcode is derived, so you never type one.
• A true receive-only APRS-IS mode: with transmit off, the app logs in read-only and refuses to send, rather than letting the server silently discard.
• An APRS-IS server lets one connection at a time use a callsign and SSID. When another device or program with the same one keeps pushing the app off, the Radio screen says so.
• RF and internet status are shown as two separate indicators on Messages, Map, Stations and Packets, with connected and connecting visually distinct.
• Beacons decide where they go, buttons decide when: each beacon routes to any set of channels (the truck's beacon to the truck's radio, everything to APRS-IS), and each channel row has its own BEACON button that sends the beacons routed through it, over it alone. The log records which links carried each message you send.
• Background reception on Android, behind a visible foreground notification. A connection that claims to be up but has gone silent is detected and restarted, including an APRS-IS connection while a radio is also connected.
• When reception was interrupted, the packet log marks the gap: how long, and why.
• The radio screen distinguishes intent from reality: a switched-on transport that isn't actually working says so, in words, with the reason.
• Diagnostics on every channel: a record of each connection and disconnection and every packet received and sent on it, which the bottom of the channel's settings sends to support as a file.
• On Android, the battery-optimization state is read from the system and shown, with a shortcut to change it. The screen also states that background reception costs battery and doesn't survive swiping the app away.

Beaconing

• Multiple independent beacons: your station beacon plus any number of extra position or object beacons, each with its own symbol, comment, path, rate, and routing, including transmitting as a different callsign (a club call, an event object). The station beacon is free; the extra profiles are Pro.
• Smart beaconing by default: the interval scales with speed (90 seconds at highway speed to 30 minutes parked, by default), and corner pegging beacons on real heading changes while ignoring compass jitter when stationary. Every parameter is editable.
• Or a fixed interval: 1, 5, 10, 30 minutes, or any custom value.
• Position ambiguity per beacon, five levels from exact down to a ~70-mile cell. The digits are removed before the packet is built, and reduced precision is flagged in the beacon summary so it can't stay on by accident.
• A stale GPS position is not re-sent as current: a station last seen stopped keeps beaconing its position, but one last seen moving goes silent rather than re-sending a place it has left.
• Position from GPS or a fixed location; long-press the map to place a beacon or object at an exact point.
• A searchable symbol picker covering the full APRS symbol set (~190 symbols, by name: type "4x4", get the jeep).
• Advertise your voice frequency in spec format (with tone and offset) so radios like a TH-D75 can tune straight to it, with a live preview of what goes on air; a PHG field decodes itself into watts, height, and antenna as you type.
• Beaconing continues in the background, keeping its access to GPS, and a fresh install transmits nothing until you turn beaconing on.
• Beaconing is something you consent to, on the station step of setup, and the home screen says plainly when it is off. If the phone's location is switched off, the beacon says so.
• Position comes from Android's own location services on a phone without Google Play services, so a de-Googled phone beacons too.
• Each beacon reports its own status: how many sent, how long ago, or the exact problem keeping it off the air.
• Per-beacon packet format: standard readable text, or Mic-E, which is about half the bytes and the only format that carries a one-word status code other radios display beside your callsign. The trade-offs are stated on the switch itself.
• Answering the ?APRSP position query is opt-in and off by default. Turned on, an asking station gets one ordinary beacon (position blur included), rate-limited per asker.
• Status, route and IGate queries (?APRSS, ?APRST, ?IGATE) are answered with one packet each, rate-limited, and can be switched off. The screen logs every query heard and what became of it.

Map

• A vector basemap rendered on the device, served from our own tile host. Every tile you view is cached, capped at a size you choose up to 10 GB, and redraws with no connection.
• The map has its own theme: match the app, light, or dark, so a dark app can sit over a daylight map.
• Offline regions (Pro): download the complete map of a whole area in North America or Europe ahead of a trip, with its size shown before you start and an update offered when newer map data is available, or add a map file of your own. A stored region draws in full with no signal at all. Regions already on the phone are kept while Pro is off, but not drawn.
• Rest of the world (Pro): every station our server hears on APRS-IS, anywhere in the world, on the map beside what your phone heard, drawn as counts where an area is busy. Tap one for its details, which say they were heard by our server, not by your phone.
• Stations, objects, and beacons drawn with their real APRS symbols, including overlay characters. Overlapping markers open a picker instead of guessing.
• Trails show where stations have been, following the same time window as the rest of the app; tap any point on a trail for the exact time, position, speed, and the packet behind it. Position history is kept for a window you set, separately from the packet log (7 days by default), and clearing the log does not clear the trails.
• Track export (Pro): save any station's trail as GPX 1.1 for Garmin, OsmAnd, Strava and anything with an import menu, or as KML for Google Earth with the times attached so it plays back on the slider. The file says plainly what it is, the beacons that reached you rather than a GPS recording, and a stretch faster than the station has ever reported travelling is broken rather than drawn across.
• A weather radar layer (NEXRAD, US only; Pro), off by default and labelled with what it costs in data.
• A station reporting reduced position precision is drawn with its uncertainty as a real box on the map, with the size named in words.
• A station that hasn't moved says "hasn't moved · N reports" instead of drawing a line out of GPS jitter.
• Follow-me mode that only uses GPS while the map is actually open, and says which position source it's following.
• Station labels appear at closer zooms to keep wide views readable; a reset-north button appears only when the map is rotated.
• "Find on map" from any station page centres the map on it and opens its card. A marker's card is the same tabbed view as the station page, and on a phone it pulls up to full screen.
• A marker rings the moment its packet lands. Toggleable in the Layers panel.
• Select a station and the map animates the path its packets actually took, hop by hop through the digipeaters that repeated them, all the way to the station that heard each one. Every route found in its last 30 packets is drawn.
• Digipeater coverage (Pro): a heat map of the places a transmitter has provably reached a digipeater from. Choose only you, built from your own beacons coming back with a digipeater's mark on them; everyone this app has heard; or one digipeater's own footprint, chosen from its marker. Every copy of a packet counts, including one a second digipeater repeated after the first. The coverage is recorded whether or not you have Pro, and outlives the packet log.

Stations

• One list of everything heard, stations and objects, sorted nearest first when your position is known, newest first otherwise, and the header says which.
• Filter chips (all / stations / objects / on frequency) plus free-text search across callsign, comment, status, frequency, and device model.
• Every row and screen carries a provenance badge: heard over RF, via the internet, or both.
• Station detail is in tabs: Overview, then Track, Weather, Telemetry, Messages and Raw where the station has them. It shows the decoded picture: device model identified from its beacon (including radios that identify themselves in Mic-E comment bytes, which are decoded and stripped rather than shown as garbage), path, position with a reverse-geocoded place name, course and speed, altitude, Mic-E status, first heard, and packet counts.
• Other SSIDs of the same operator are listed and linked.
• Pinned stations: tap the star on a station's page and it sorts to the top of the list, whichever order the list is in. While you are on APRS-IS its packets reach you wherever it goes, without it having to be inside your range filter. A pin never notifies and does nothing in the background. It changes where a station sorts, not whether it has been heard.
• Mobiles nearby (Pro): a notification when a station on the move comes close enough to work, either already inside the range you set or heading into it, with an option to only count stations advertising a voice frequency. On its own Android notification channel, so it can be silenced separately.
• Grid squares: your own six-character Maidenhead locator, with a copy button and the place it covers, and the distance and bearing from it to any other locator or callsign, worked out on the phone with no connection.
• The ISS (Pro): whether the space station is above your horizon right now, where it is, and its next passes over you, computed on the phone from its published orbit; a map layer with its position, footprint and next orbit; a one-tap beacon profile with the ARISS path and rate that can send itself whenever the station is heard; as many reminders before a pass as you choose; and a list of every station heard through its digipeater, with a link to spaceaprs.com. The VIA ISS tag on those packets in the log is free.
• Weather stations get inline history charts of every measure they actually report, built from the packets on file. An implausible reading from a broken sensor is recorded as absent rather than allowed to rescale a week of real data.
• WHO-IS lookups are cached: revisit a station and the answer is already there, with its age, and one tap to refresh over the air.
• External lookups per station: qrz.com, aprs.fi, and aprs.to, shown only where they make sense (no QRZ link on an object or a weather-network ID).
• A shared view filter across map, stations, and packets: age window, RF/internet origin, which of your channels heard it (offered once you run more than one), station kind (digis, igates, weather, mobile, fixed), and pinned only. Set once, applies everywhere, persists.

Packet log

• Every frame received is stored and shown live, each tagged with the channel that carried it, with the rate per minute, or the reason nothing is arriving when a connection has gone stale, is reconnecting or is off.
• Quick filters (all / RF only / mine / errors) plus free-text filtering of the raw line.
• Packets that fail to decode are flagged and kept, never hidden. Real APRS traffic contains malformed packets.
• Every copy is kept. A packet heard more than once, through a second digipeater or as an IGated copy, is marked with how many times it was heard, and an Every copy chip lists each copy with its own path, link and time.
• The packet inspector decodes field by field: source, device from the destination call, the path with used digipeats drawn as a graph (and internet routing marked as not a digipeat), type, position, symbol, message IDs, object names, Mic-E status, course, speed and altitude, PHG, weather, and telemetry scaled by the station's own definitions, plus a copyable hex dump of the whole frame.
• From the inspector, callsigns open their station page, a position report opens on the map (and back returns to the packet), a message opens its conversation, and the same station's older and newer packets are a tap away.
• Reception gaps appear inline in the log: how long reception was down and why.
• Retention you set: how long packets are kept and how long trail points are kept, as two separate windows, or ALL to keep everything until you clear it. Older entries go on their own at start-up and about once an hour; messages, stations and settings are never touched by these windows.
• Export exactly what's on screen, filters applied, or save the entire log as a standard capture file, one packet per line with timestamps. Exporting is free.
• Import and replay captures (Pro): file them silently at their original times, or replay at 1×, 10×, or 60× with gaps preserved. Replayed traffic is marked as such and never transmits.

Backup & data

• Everything lives in a database on the phone; the app is fully usable with no connection.
• An optional account, signed in with a password or an emailed link, with two-step verification if you want it. Nothing in the app needs one.
• Sync between your devices (Pro, with an account): messages, conversations, pinned stations, the blocked list, coverage and settings stay the same on every device signed in, updating live while the app is open. You choose what each device sends and receives.
• With Pro, when two of your signed-in devices share a callsign and SSID, only one of them beacons and acknowledges at a time, so the map never shows your station in two places. Take over moves it to the device in your hand.
• Export a JSON backup of settings, conversations (with delivery state and read state), and your blocked list, with sections individually selectable, saved to a folder or shared to another app.
• Import as a merge (adds what's missing, deletes nothing, safe to run twice) or a restore (replaces, and the button says so in red).
• Every import shows a preview first: file age, app version, and exactly what will be added, changed, or skipped and why. A file that can't be imported is refused whole, with every problem listed.
• Block stations by callsign, per-SSID, with your own notes. Blocking stops threads, notifications, and acks. The screen states that packets from a blocked station still arrive and still appear on the map and in the log.
• Clearing data is deliberately hard: two-tap confirmations that state exact counts before anything is deleted.
• Your data leaves with you: the backup export works even after a trial or subscription has ended, from the very screen that says so.

On Windows

• The same app as a Windows program, downloaded from this site, for Windows 10 and Windows 11 (64-bit).
• Everything over APRS-IS: messaging, services, nets, APRS OTA, the map, stations, the packet log, beaconing and backup, as on a phone. It connects to the APRS-IS servers itself, so your own server, port and filter work.
• USB serial KISS TNCs (Pro). The app lists the serial ports itself and reconnects when the TNC is plugged in again.
• Bluetooth KISS TNCs (Pro). Pair the radio or TNC in Windows Bluetooth settings, and the app connects through the serial port Windows gives it.
• Bluetooth LE KISS TNCs and LoRa APRS trackers (Pro). The app scans for them, and reconnects by itself.
• KISS over TCP (Pro), for Direwolf or another TNC on your network.
• It keeps running when you close the window. The app stays in the system tray, still receiving, beaconing and notifying, until you choose Quit there. It starts with Windows, in the tray, unless you turn that off.
• A GPS receiver on USB, a serial port or Bluetooth, the location Windows reports, or a fixed position for a station that stays put.
• Windows notifications for messages and alerts, and reminders for an ISS pass or #APRSThursday, while the app is running, with its window open or closed.
• Offline map regions (Pro) are kept on the computer, and you can import a map file of your own.
• The database is encrypted on disk with a key held by your Windows account. A backup export is how your data leaves it.
• It updates itself. The app checks for a new version, downloads it in the background, and applies it the next time the app starts, or sooner while its window is closed and no radio is connected. An update never drops a radio link.
• Pro on Windows belongs to your account. Subscribe from the app, which takes the payment on aprsconnect.com, or sign in to an account that already has Pro from Android or iPhone.

In a browser

• The same app at app.aprsconnect.com, with nothing to install: on a computer, a tablet or a phone, in a current Chrome, Edge, Firefox or Safari. It fills the window it is in.
• Everything over APRS-IS: messaging, services, nets, APRS OTA, the map, stations, the packet log, beaconing and backup, as on a phone. The connection goes through aprsconnect.com to the public APRS-IS servers, because a web page cannot open one itself.
• USB serial KISS TNCs (Pro) in Chrome or Edge on a computer. You choose the TNC once from the browser's own list, and it reconnects by itself after that.
• Bluetooth LE KISS TNCs and LoRa APRS trackers (Pro) in Chrome or Edge on a computer. The browser asks you to choose the device each time the channel connects.
• A USB GPS receiver in Chrome or Edge on a computer, for a position better than the browser's own. A fixed location is offered too, which suits a computer that stays put.
• Install it as an app from the address bar in Chrome or Edge, with its own icon and window.
• Your Pro and your messages come with your account. Sign in and the browser has the Pro you subscribed to on Android or iPhone, and with it your conversations, pinned stations and settings. Without a subscription yet, the browser's own Pro screen takes you to the payment page on aprsconnect.com.
• Notifications for messages and alerts while the tab is open in the background.
• The map keeps the tiles you have viewed, up to a size you set, and with Pro whole offline regions are stored in the browser.
• Right-click opens the menus a long press opens on a phone, and files save to the computer.
• It updates itself: a tab left in the background reloads onto a new version when no radio is connected and nothing is being sent.
• What a browser cannot do: it runs only while its tab is open, in one tab at a time, so closing the tab stops receiving and beaconing. The audio modem, Bluetooth Classic TNCs, KISS over TCP and the Tidradio TD-H9 need the Android or iPhone app. All four are in the Windows app too.
• Your data is kept by the browser, for this site only. Clearing the site's data removes it, so keep a backup or sign in.

General

• Free over APRS-IS. Messaging, services, nets, the map, stations, the packet log, the station beacon and backup all work without needing APRS Connect Pro. APRS Connect Pro ($3.99/month or $29.99/year, billed through Google Play on Android or the App Store on iPhone, with a 7-day free trial where the store offers one) switches on the radio channels, offline region downloads, the radar layer, track export, extra beacon profiles, capture replay, retry when heard, mobiles nearby, the digipeater coverage map, the IGate, the digipeater, the Rest of the world map layer, sync between your devices, and your other callsigns. Let it lapse and nothing is deleted and nothing goes off the air: APRS-IS stays connected and the station beacon keeps running.
• Pro features show a lock, so you can see which need Pro before you tap one.
• Nine languages: English, German, Spanish, French, Italian, Japanese, Brazilian Portuguese, Turkish and Malay, on every screen. The app follows the phone's language, or you pin one. Protocol words stay in English in every language, so a term you quote to another operator reads the same on their screen.
• Packets from the app go out under its own APRS device identifiers, APSTKA on Android, APSTKI on iOS, APSTKW on Windows and APSTKB in a browser, so a station heard from APRS Connect is attributable.
• Callsign + SSID identity with guidance on conventional SSIDs; additional SSIDs and club calls are just more beacons.
• A device-ID database identifies the hardware behind each station heard (updated weekly if you allow it, ~40 KB, from the APRS Foundation's public list).
• Message notifications on a dedicated Android channel, so APRS can be silenced independently of everything else. Delivery failures notify too, with tap-to-retry, and a thread's notifications clear when you open it.
• Settings is grouped by topic, one card per section.
• Works with TalkBack and VoiceOver: buttons have names, station symbols are read by name, and an open conversation reads new messages aloud as they arrive.
• After an update, a What's new sheet says once what changed, and the same list stays under About.
• The screen can stay on: never, only while the map is open, or always. One setting, not one per screen.
• A tab bar you arrange. Swipe up on the bar for a drawer of every screen in the app, the IGate and the digipeater included, with the six on the bar as its top row. Drag any tile onto another and the two swap; whatever is in the first cell is the screen the app opens on.
• A message's detail lists every copy that went out, over which channel, and when.
• An emergency screen with guard rails: activating takes a three-second hold and a confirmation, so it cannot be set off by accident, and a false alarm on amateur radio is a serious matter. It transmits your position with the Mic-E emergency status, and while active it reports plainly what has gone out and when, and when nothing has. It will not arm while the station callsign is still the placeholder N0CALL, and says so first.
• Hearing another station switch into Mic-E emergency raises an alert on its own notification channel, with one tap to see where they are. The alert fires on the transition, so a beacon repeating every few seconds doesn't buzz you every few seconds.
• US or metric units: one setting, applied everywhere.
• Monospace type for callsigns and packets throughout, chosen so 0/O and 1/l can't be confused.
• 12- or 24-hour clock for display; times on the air stay UTC.
• App updates arrive over the air and apply on the next start, or immediately if you choose to restart. The About screen states exactly which build is running, including the ID of any over-the-air update.
• Usage statistics are a single switch in settings; reports never include callsigns, yours or anyone else's.
• Feedback opens a conversation with the developer inside the app, so a report can be answered.
• Support conversations and release news arrive as their own threads in the app, carried over HTTPS and deliberately not over APRS, because app traffic does not belong on amateur spectrum.

Missing something you'd expect? Say so on the support page. The list of what's still ahead is on the status page.