Cadpage

Inside the Dispatch Workflow: From SMS to Scene

The firefighter's phone buzzes with an incoming text message. But this is not a standard SMS alert. The Cadpage app intercepts that message, parses the raw data, and transforms it into a structured incident report. The screen shows the address, the type of emergency, and the responding units. A single tap opens the location in Google Maps with turn-by-turn directions. This is the core workflow of Cadpage. It takes the chaotic stream of dispatch texts and turns them into actionable information. The app reads the SMS from the central dispatch service, extracts the relevant details, and presents them in a clear, readable format. It works only if the user already receives these dispatch texts. Without that existing SMS feed, the app has no data to process. This limitation is stated plainly on the Google Play page: "It will not work if you not already receiving these text messages."

The workflow is designed for speed. Every second counts in an emergency response. Cadpage eliminates the need to read through a long, jargon-filled text message. It pulls out the critical information — the location, the nature of the call, the time — and displays it prominently. The user can then tap the map button to see the incident location and get directions. This integration of SMS parsing, incident display, and navigation is the app's defining feature. It is not a general-purpose communication tool. It is a purpose-built piece of software for firefighters and EMS personnel who receive dispatch alerts via SMS.

Comparing Cadpage to a Generic Messaging App

A generic messaging app like WhatsApp or the default SMS client could theoretically receive dispatch texts. But those apps do not parse the content. They display the raw message as a block of text. The user would have to read through the entire message, manually extract the address, and then open a separate maps app to find the location. This process is slow and error-prone. Cadpage automates these steps. It parses the message, extracts the address, and provides a direct link to maps. This is a significant advantage in an emergency situation.

Another difference is the customisation. Cadpage allows users to set custom ringtones for dispatches. This ensures that the user knows immediately when a dispatch alert arrives, even if their phone is on silent. The app also provides a separate dashboard for dispatches, organising them by time and type. This makes it easier to review past incidents and track response history. The generic messaging app does not offer these features. It treats dispatch texts like any other message, mixing them with personal conversations and making them harder to find.

Version History and What Actually Changed

The current version is 2.2.13-25, released on July 20, 2026. The changelog is specific and actionable: "New Locations: Boyd County, KY Lincoln County, MN Wayne County, WV Location Fixes: Jefferson County, GA McDuffie County, GA Putname County, NY Crawford County, PA". This is not the generic "bug fixes and improvements" that plagues many app updates. It is a clear list of new counties supported and locations where parsing fixes have been applied. This level of detail is rare for a free app. It shows that the developer, Ken Corbin, is actively maintaining the app and responding to the needs of specific emergency response agencies.

The APKPure version, 2.2.13-23G, shows a similar pattern: "Location Fixes: Putnam County, NY Tinker AFB, OK Marion County, OR Vancouver Island, BC". These updates are geographically targeted. They add support for new dispatch centres and fix parsing errors for existing ones. This suggests that the app's parsing logic is highly dependent on the specific format used by each dispatch centre. A change in one county's dispatch system could break the app for that county. The developer addresses these issues on a case-by-case basis, releasing updates as needed. This is a sustainable model for a niche app, but it also means that users in unsupported counties may not get a working experience.

The Niche Use-Case: Open Source and Community Support

Cadpage is not just a closed-source app. The developer has published the source code on GitHub under the cadpage organisation. The repositories include cadpage-parsers, cadpage-android, and CadpageMsgSupport. This is unusual for a free app with a donation model. It suggests a commitment to transparency and community involvement. Other developers can contribute to the parsing library, add support for new dispatch formats, or fork the project for their own use. This open-source approach also provides a level of trust. Users can inspect the code to understand how their data is handled. The app does not encrypt data in transit, according to the Google Play data safety section. This is a concern for some users. However, the open-source nature of the app allows security researchers to audit the code and identify potential vulnerabilities.

The support app, CadpageMsgSupport, is described as taking over functions that are no longer permitted for the real Cadpage app. This suggests that changes in Android's permissions or policies have forced the developer to create a separate app to handle certain tasks. This is a common workaround for apps that rely on SMS reading, a permission that has become more restricted in recent Android versions. The existence of this support app adds complexity to the installation and setup process. Users may need to install two apps to get the full functionality. This is not ideal, but it reflects the reality of developing for a platform that is constantly changing.