APRS Chat

Opening the app for the first time

The moment you install and open APRS Chat, you are greeted with a login screen that asks for your callsign and APRS-IS passcode. There is no guest mode. You must have a valid amateur radio license to proceed. This immediately signals that the app is built for licensed operators, not casual users. After entering your credentials, the home screen displays a conversation list, similar to WhatsApp or Signal. The layout is clean and modern, with a bottom navigation bar that includes tabs for "Chats", "Map", "Services", and "Settings". There is no tutorial, but the interface is intuitive enough that most users can start messaging immediately. Tapping on the "+" button allows you to start a new conversation by entering a callsign. The app does not automatically populate your contacts; you have to know the callsign of the person you want to message. This is a deliberate design choice that reflects the nature of APRS, where callsigns are the primary identifier.

The onboarding experience is minimal but functional. The app assumes you already know what APRS is and how it works. For a new ham, this could be overwhelming, but for experienced operators, it is exactly what they need: a quick way to send and receive messages without unnecessary clutter. The app does not ask for any permissions during setup. It only requests location permission when you try to use the station map, and storage permission when you try to save a log. This is a sensible approach that respects user privacy. The initial load time is around 2-3 seconds on a 4G connection, which is acceptable. The app does not crash on launch, which is a positive sign. The interface uses Material Design with a dark mode option, making it comfortable to use in low-light conditions. The color scheme is blue and white, which is clean and professional. The font sizes are readable. Overall, the first impression is that of a well-designed utility app that brings APRS messaging into the modern era.

How the Services Directory and ANSRVR group chat work together

The app's two most distinctive features are the Services Directory and ANSRVR group chat integration. On the surface, these seem separate: one lets you interact with APRS service bots, the other lets you join group conversations. But in practice, they are deeply connected. The Services Directory provides a list of APRS bots like REPEAT (for message relay and location queries), WXBOT (for weather forecasts), and WB4BOR-11 (for current conditions). Each bot has its own command syntax, but APRS Chat simplifies this by providing tap-able command chips. For example, tapping on REPEAT brings up options to query a location or relay a message. You do not have to memorise the syntax. This is a game-changer for new users who might otherwise be intimidated by the command-line nature of traditional APRS clients. The ANSRVR integration allows you to join group chats, such as the APRSThursday net or HOTG (Ham On The Go) sessions. The app auto-detects the group message format and routes replies to the correct thread. It also suppresses ACK expectations on outgoing group messages, since group messages are not acknowledged per-recipient. The interaction between these two features is powerful: you can use the Services Directory to get a weather forecast, then share that forecast with your ANSRVR group chat, all within the same app. This workflow is not described on the Play Store page, which only mentions messaging and position tracking. The app essentially turns APRS from a raw data stream into a conversational platform.

This integration is what sets APRS Chat apart from other APRS clients. Most clients treat APRS as a data protocol, not as a messaging platform. APRS Chat treats it as a messaging platform, with the Services Directory acting as a bridge between the user and the underlying protocol. The app also includes a quick-join floating action button for APRS Thursday events, so you do not have to manually remember when to join. This is a small but thoughtful touch that shows the developer understands the community's needs. The app's focus on usability does not come at the cost of functionality; you can still view raw APRS packets if you are an experimenter. But for most users, the app hides the complexity and presents a clean, modern interface.

Real-world performance and user-reported issues

The app has a small but growing user base, with over 100 installs according to AppBrain. The feedback so far has been positive, with users praising the modern UI and the automatic ACK tracking. However, there are some reported issues. One user on the SharkRF forum noted that APRS Chat does not send a message number, which can cause digipeaters to reject packets due to an inability to calculate duplicates. This is a significant issue because it affects the reliability of message delivery over RF. The developer has acknowledged the issue and is working on a fix. Another reported issue is that the app sometimes fails to load the services screen correctly, although this was fixed in the latest update. The app's performance on older devices is a concern, as the minimum Android version is 8.0, which excludes devices older than 2017. The app's size is only 4.77 MB, which is remarkably small for a modern messaging app. This is likely because the app does not include heavy graphics or animations. The app does not consume excessive battery or data, according to user reports. This is likely because it only fetches data when you actively open a conversation or refresh the map. The absence of background sync is a double-edged sword: it saves battery but means you have to manually check for new messages.

The app's crash rate is low, but not zero. The changelog mentions fixes for crashes affecting Android 12–16 users, which suggests that the app has had some stability issues. The app does not have a built-in feedback mechanism; you have to email the developer directly. This is a barrier to reporting issues, which could explain why some bugs persist. The developer, Hemna LLC, appears to be responsive, with regular updates since the app's launch in May 2026. The app's customer support is handled via email, and the developer's address is listed in Appomattox, Virginia. The app's performance is generally smooth, but there may be occasional lag when loading the station map, especially if there are many stations in your area. This is likely due to the app fetching data from the APRS-IS server each time you open the map. A caching mechanism could improve this, but the app does not appear to have one. The app's data encryption in transit is a positive security feature, but it does not compensate for the lack of offline mode. The app requires an active internet connection for APRS-IS mode, but it can work entirely on RF with a KISS TNC and a radio.

Permission requirements and what they mean for your device

The app requests location permission, which is understandable given its map-based station tracking feature. However, it does not use location to auto-detect your position for beaconing; you have to manually set your position. This makes the location permission somewhat redundant. The app also requests storage permission, presumably to cache map tiles or to store message logs. There is no request for camera or microphone, which is good for privacy. The storage permission is used to save your message history and logs, which is a useful feature for users who need to keep records. However, the app does not clearly explain why these permissions are needed, which could be a trust issue for users who are wary of data collection. The privacy policy is not explicitly stated, but the app does not collect any personal data beyond what is necessary for APRS operation. The app does not request any permissions that are out of the ordinary for a communication app, but the combination of location and storage with the lack of transparency raises questions about how user data is managed. The app's permission model is straightforward, but the execution of the messaging flow is where the real value lies. The app's minimal permissions are a plus for privacy, but the lack of information about data retention is a concern. The app does not use any third-party analytics or advertising SDKs, which is a plus for privacy. The app's permissions are minimal, which is a good practice for a communication tool. However, the app does not provide any information about how long it retains data or how users can request deletion, despite the Play Store stating that data can be deleted.