Timeline

Work on the app began four days before the repository existed, under the name APRS One.

It was built around messaging. Most APRS clients treat messages as secondary to position reporting and show them as individual packets rather than conversations; this one keeps a thread per station, with a delivery state on each message.

By the time the code moved into its own repository it already ran: message threads, a map with stations, objects and trails, the packet log, and the first of the service screens.

APRS One is renamed APRS Connect and moved into a repository of its own. The first commit is 513 files and 63,000 lines, because the app was already working; the commit is a move, not a starting point. Everything below this entry is public history.

Version code 1 clears review two days after the repository was created. Nothing was on sale yet. The listing was submitted early because store review takes days that cannot be recovered later.

The APRS OTA handbook lists APRS Connect under software with APRS OTA specific features: hosting an operation, every chaser on one screen, and the countdown timer.

aprsconnect.com had been a single page since 20 August. It gains a documentation section written against the app as built, with every label checked against the screen it describes, and a blog published from the same deploy.

Built and uploaded the same day as 1.5.0.

"APRS Connect: A Messaging-First APRS Client for Android, Free Over APRS-IS"

The French amateur radio news site f8bdx.free.fr covers the app under "une nouvelle application APRS pour Android", describing station tracking, use with a transceiver, and the IGate and digipeater.

The same app in a web browser, with nothing to install.