New Features

In-App Banner Notification Framework

• What - Introduced a new in-app banner notification framework for Android, providing a more scalable and consistent notification experience throughout the application. The new banner system supports priority-based presentation and enables notifications such as chat message alerts to be displayed directly within the app without disrupting active workflows. This foundation provides a more flexible notification architecture for future enhancements and additional notification types.
• Why - This enhancement improves user awareness of important events while minimizing workflow interruptions. By presenting notifications directly within the application using a standardized framework, responders can receive timely updates without relying solely on system-level notifications, creating a more consistent and controlled user experience.
• How
  • Continue using the application normally.
  • In-app notifications automatically appear as banner alerts when supported events occur.
  • Banner notifications display according to their priority level.
  • Chat message notifications and other supported alert types are presented within the application interface.
  • No additional configuration is required.
• Use Case - A responder actively reviewing incident information can receive a chat message notification through an in-app banner without leaving the current screen, allowing them to stay informed while maintaining focus on operational tasks.

Feature Enhancements

Pull-to-Refresh Support for Incident Details

• What - Added native pull-to-refresh functionality to the Android incident experience, allowing users to manually refresh incident information using a familiar swipe-down gesture. The refresh action reloads incident data, map information, and associated call notes, and functions consistently across both map and list views.
• Why - This enhancement provides responders with a quick and intuitive method for obtaining the latest incident information without navigating away from the current screen. Manual refresh capability improves confidence that users are viewing current operational data during active incidents.
• How
  • Navigate to the Incidents page.
  • Pull down from the top of the screen to initiate a refresh.
  • Wait for the refresh indicator to complete.
  • Incident details, map information, and call notes are automatically reloaded.
  • The gesture is available in both map and list views.
• Use Case - While responding to a rapidly evolving incident, a user can quickly pull down on the incident screen to retrieve the latest dispatch updates, notes, and map information without interrupting their workflow.

Fire Zone Display on Incident Details

• What - Enhanced the Android Incident Details screen to display Fire Zone information when provided by the CAD system. Fire Zone data is presented in a dedicated field above the Cross Street section, making the information readily accessible during incident review.
• Why - This enhancement improves situational awareness by providing additional location and response context directly within the incident workflow. Displaying Fire Zone information alongside other incident details helps responders quickly identify operational areas and jurisdictional information.
• How
  • Open an incident within the application.
  • Navigate to the Incident Details screen.
  • Review the Fire Zone field displayed above Cross Street when Fire Zone data is available.
  • The field appears automatically when supported data is received from CAD.
• Use Case - A responding crew reviewing dispatch information can immediately identify the associated Fire Zone and use that information to coordinate response activities, staging, or mutual aid operations.

Expanded Place Name Support in Incident Details

• What - Expanded Android support for displaying Place Name information within incident details when enabled through client configuration and available in the API response. Place Name values now appear more broadly throughout the incident workflow, providing additional context for dispatched locations.
• Why - This enhancement helps responders identify incidents more quickly by surfacing familiar facility names, landmarks, or commonly recognized locations in addition to standard address information.
• How
  • Ensure Place Name display is enabled within applicable configuration settings.
  • Open an incident that includes Place Name information.
  • Review the Place Name field within the incident details screen.
  • Place Name data appears automatically when provided by the CAD integration.
• Use Case - A responder receiving a dispatch to a well-known facility can immediately recognize the location by its Place Name, reducing ambiguity and improving response awareness before arrival.

Android Keep-Alive Improvements for Background Unit Tracking

• What - Enhanced Android background location tracking to align with iOS keep_alive behavior, helping units remain visible on responder maps while devices are screen locked. The update introduces a more resilient background tracking model using foreground service behavior and ongoing heartbeat updates to maintain location reporting during extended operational periods.
• Why - This enhancement improves location reliability and operational visibility by reducing instances where units disappear from maps when devices enter screen-locked states. Consistent location updates support better situational awareness for command staff and responders monitoring unit locations.
• How
  • Enable unit tracking as part of normal responder workflows.
  • Lock the device screen or allow the device to enter its normal locked state.
  • Background location updates continue automatically using keep-alive behavior.
  • Unit locations remain visible on responder maps when tracking is active.
• Use Case - A unit traveling to an incident with its MDT screen locked remains visible to command staff and other responders, allowing operational personnel to track apparatus movement and arrival progress in real time.

ArcGIS Last Known Position Retention

• What - Enhanced ArcGIS map behavior to retain the user’s last known location when GPS data becomes unavailable. When no retained location exists, the map now falls back to the configured department center location rather than displaying invalid coordinates.
• Why - This enhancement improves map reliability and user experience by preventing unexpected navigation to incorrect map locations when GPS connectivity is lost or temporarily unavailable.
• How
  • Open the ArcGIS map view.
  • If GPS connectivity is interrupted, the application automatically retains and displays the last known location.
  • When no previous location is available, the map centers on the configured department area.
  • No user action is required.
• Use Case - A responder operating in an area with poor cellular or GPS coverage can continue using the map based on their last known position rather than being redirected to an invalid location, improving navigation continuity.

Quick Route Coordinate Accuracy Improvements

• What - Enhanced Quick Route functionality to pass dispatch coordinates directly to external mapping applications when coordinates are available. This improves routing accuracy and aligns Android behavior with the existing iOS experience.
• Why - This enhancement reduces navigation errors that can occur when mapping applications rely solely on address matching, particularly in areas where addresses may be ambiguous or difficult to geocode accurately.
• How
  • Open an incident containing dispatch location information.
  • Select Quick Route.
  • The application automatically passes available dispatch coordinates to the selected external mapping application.
  • Routing begins using the most accurate available destination information.
• Use Case - A responder navigating to a rural incident location receives directions based on exact dispatch coordinates rather than address matching alone, improving routing accuracy and reducing travel delays.

Street View Availability Messaging Improvements

• What - Updated Street View availability handling to display a native in-app message when Street View imagery is unavailable for a selected location. The new experience replaces device-level toast messages and aligns Android behavior with the iOS implementation.
• Why - This enhancement provides clearer and more consistent user feedback when Street View content cannot be displayed, improving usability and reducing confusion during map-related workflows.
• How
  • Open a location that supports Street View access.
  • Attempt to launch Street View imagery.
  • If Street View is unavailable, an in-app message displays explaining the condition.
  • Continue using the map without leaving the application.
• Use Case - A responder attempting to view Street View imagery for a rural location immediately receives a clear in-app notification that imagery is unavailable, allowing them to continue planning their response without uncertainty.

Fixes

Incident Details Access After Map Popup Interaction

• What - Resolved a tablet-specific issue that could prevent users from opening Incident Details after interacting with a map popup. Users can now consistently navigate from map-based workflows to incident details without losing access to incident information.
• Why - This fix removes a workflow interruption that could prevent responders from accessing critical incident information after reviewing map-based content on tablet devices.
• How
  • Open an incident and interact with a map popup.
  • Select the incident details option.
  • Incident Details now open correctly without requiring navigation resets or application restarts.
  • No additional configuration is required.
• Use Case - A responder reviewing map information on a tablet can immediately transition to the Incident Details screen after interacting with a map marker, maintaining a smooth and uninterrupted workflow.