Android Mobile App Version 7.1.5

New Features

Mobile Session Timeout (Android)

• What - Introduced a configurable mobile session timeout for Android devices to support compliance requirements by automatically locking or logging out users after a defined period of inactivity. The feature includes an idle timer that resets on user interaction, excludes active Response workflows such as Incident Command, Preplans, and Hydrants from timeout enforcement, and presents a warning modal with a countdown prior to session expiration. Timeout behavior dynamically adjusts based on configured duration, and upon expiration, standard users are locked while SSO users are logged out. The functionality operates consistently across foreground and background states, supports both online and offline scenarios, and includes WCAG 2.1 AA–compliant accessibility support along with analytics tracking for timeout events and user interactions.

• Why - This enhancement was implemented to strengthen security and ensure compliance with industry standards by reducing the risk of unauthorized access from unattended devices. It also provides a balanced user experience by preventing interruptions during critical response workflows while still enforcing session controls elsewhere, and improves visibility into user behavior through analytics tracking of timeout-related events.

• How -

  • This feature will need to be configured via SuperAdmin and is a global setting. Please contact your CSM to activate and configure this feature.

  • Note:

    • Timeout does not occur while actively using Incident Command, Preplans, or Hydrants

    • Warning timing varies based on the selected timeout duration

    • SSO users will be fully logged out upon timeout, requiring re-authentication

• Use Case - A responder steps away from their device after reviewing incident details without manually locking the app. After the configured period of inactivity, the system displays a warning countdown, and if no action is taken, the session is automatically secured—either by locking or logging out—ensuring sensitive operational data remains protected while still allowing uninterrupted access during active emergency workflows.Responder Map Zoom Level Indicator and User-Friendly Zoom Names

Responder Map Zoom Level Indicator and User-Friendly Zoom Names

• What - The mobile app now includes a zoom level indicator on the Responder map that appears during zoom interactions to show the current map scale in a more understandable way. Numeric zoom values have been replaced with user-friendly labels such as Street View, Block View, Neighborhood, City, and Region, making it easier to understand how closely the map is focused. When users zoom beyond the highest configured level, the indicator displays Overview to clearly reflect a broader map perspective. The tooltip appears automatically when the zoom level changes and dismisses after a few seconds so the map remains clean and uncluttered.

• Why - This improvement makes the map easier to interpret during active use, especially when users need to quickly understand the scale of what they are viewing while monitoring incidents, personnel, or apparatus locations. Replacing technical zoom values with descriptive labels improves usability, reduces guesswork, and creates a more intuitive map experience for users working in fast-paced environments.

• How

  • Open the Responder Map in the mobile app.

  • Pinch to zoom in or out on the map.

  • View the temporary zoom tooltip that appears on screen during the zoom action.

  • Reference the displayed label, such as Street View or City, to understand the current map scale.

  • Continue using the map normally after the tooltip automatically disappears.

  • Additional note: If the map is zoomed farther out than the highest configured level, the indicator will display Overview.

• Use Case - A responder using the mobile map during an active incident can quickly tell whether they are viewing a specific street, a neighborhood, or a wider regional area without interpreting a numeric zoom value. This makes it easier to adjust map scale appropriately when checking nearby units, reviewing incident proximity, or gaining broader situational awareness.

Time Card Added to the Scheduling Menu

• What - The mobile app now includes a Time Card option within the Scheduling section of the app menu. Users with the appropriate permissions can open Time Card directly from their mobile device, with the option appearing below Time Off. Selecting the menu item opens the Time Card page inside the app webview so users can manage time card activities without leaving the mobile experience.

• Why - Adding Time Card to the mobile navigation improves accessibility for scheduling-related tasks and reduces the steps required to reach time management tools. This gives users a more direct and convenient path to important scheduling functionality while supporting consistent access from both desktop and mobile workflows.

• How

  • Open the mobile app menu.

  • Navigate to Scheduling.

  • Select Time Card.

  • Use the Time Card page that opens in the in-app webview to manage time card activities.

  • Additional note: The Time Card option only appears for users who have the required permission to access this feature.

• Use Case - A user who needs to review or manage time card activity while away from a workstation can open the mobile app, go to Scheduling, and launch Time Card directly from the menu. This allows scheduling tasks to be completed more efficiently from the field or while moving between assignments.

Feature Enhancements

Expandable Chat Text Input

• What - The chat experience has been enhanced with an expandable text input field that grows vertically as users type longer messages. Instead of remaining a single-line field, the input now expands to show multiple lines of content during message composition, making it easier to review and edit longer messages before sending. After the message is sent, the field automatically collapses back to a single line. This update also aligns Android behavior more closely with the iOS messaging experience.

• Why - This enhancement improves message composition by giving users better visibility into longer responses, reducing the need to scroll within a cramped input field and making conversations easier to manage. It also creates a more consistent experience across mobile platforms, helping users move between devices with more predictable messaging behavior.

• How

  • Open any conversation in Messaging.

  • Tap into the chat input field at the bottom of the screen.

  • Begin typing a message.

  • Continue typing as needed and the input field will automatically expand to display additional lines.

  • Send the message as normal.

  • Additional note: After sending, the input field will automatically return to its default single-line size.

• Use Case - A user sending a detailed operational update, follow-up instructions, or a longer coordination message can now see more of the message while typing, making it easier to catch mistakes, confirm wording, and send complete information without feeling constrained by the input area.

ArcGIS Address Tags Layer Toggle

• What - Added full support for the Address Tags layer toggle when the app is using the ArcGIS map provider, ensuring users can display or hide address tags just as they can with other supported map providers. This enhancement also preserves the user’s Address Tags preference across sessions and account switching, while maintaining proper layer visibility behavior based on map zoom level and configured map layers.

• Why - This change improves consistency across platforms and map providers so users have a more predictable mapping experience regardless of which provider is active. It also reduces confusion for personnel who rely on map overlays during incident response by ensuring the same core layer controls are available and behave consistently throughout the application.

• How

  • Navigate to Map View in the mobile app.

  • Open the Map Layers or Map Options controls.

  • Locate the Address Tags toggle.

  • Turn Address Tags on to display address labels on the map, or off to hide them.

  • When using ArcGIS, the toggle now behaves consistently with other supported map providers.

  • User preference for this setting is retained across future sessions and account changes where supported.

• Use Case - A responder reviewing incident locations in a dense service area can enable Address Tags to quickly identify nearby addresses and landmarks without switching tools or platforms. When the same user returns to the app later, their preferred map layer setting remains in place, helping them resume work faster during active response conditions.

Incident View Time Display Improvements

• What - Updated the incident view to use more consistent timestamp formatting throughout the interface, renamed Dispatch Stored Time to Last Updated, and moved that label to a more prominent position for better visibility. The app also now defaults to 24-hour time when no user-specific time preference has been set, improving consistency in how incident timing information is presented.

• Why - Time information is critical during dispatch and incident response, and inconsistent labels or formatting can slow interpretation when users need to act quickly. These updates make timestamps easier to understand at a glance, reduce cognitive effort, and provide clearer context around the most recent incident update.

• How

  • Open an incident from Incident List, a notification, or another supported entry point.

  • Review the timestamps shown in Incident Details.

  • Locate the updated Last Updated label in its new, more visible position.

  • If no personal time preference has been configured, the app will automatically display time in 24-hour format.

  • No additional setup is required for this improvement to take effect.

• Use Case - A user responding to a rapidly changing event can open Incident Details and immediately identify when the record was most recently updated without needing to interpret unclear labels. This helps them confirm whether dispatch information is current before acting on route changes, scene updates, or resource movement.

Events & Activities Menu Consolidation

• What - Replaced the previous Activities menu structure with a new Events & Activities navigation model that consolidates access under a clearer organizational framework. This update introduces Daily Operations as the primary submenu, removes older legacy menu items, and ensures supported access paths remain consistent across the app menu and bottom navigation while still respecting user permissions.

• Why - The previous menu structure created unnecessary complexity and made it harder for users to quickly find related workflow areas. Consolidating these items into a more intuitive navigation model improves usability, reduces friction, and supports a cleaner experience that is better aligned with the rest of the mobile application.

• How

  • Open the app Menu or use the Bottom Navigation where applicable.

  • Select Events & Activities instead of the previous Activities menu.

  • Open Daily Operations to access the primary related workflow area.

  • Legacy items such as older activity-specific menu paths are no longer shown.

  • Visibility of Events & Activities continues to depend on the user having the required permissions.

• Use Case - A field user who needs to move between operational activities and event-related workflows can now find those areas under a single, clearer menu path instead of checking multiple older navigation points. This saves time and reduces navigation errors during busy shifts or multi-incident periods.

Fixes

Android OS Version Now Displays in User-Friendly Format

• What - The mobile app now displays the Android operating system version in a user-friendly format, such as Android 16, instead of showing the internal API or SDK level, such as 36, in unit information views. This correction applies across map unit details, firefighter location sharing, client data sharing, and related web responder views so the displayed version information is clearer and more consistent wherever tracked unit details are shown.

• Why - Showing the user-facing Android version reduces confusion and makes device information easier to understand for users who expect the version shown in the app to match what they see in their device settings. It also improves consistency across platforms and helps users interpret shared unit details more confidently.

• How

  • Open a unit information view in the mobile app or related responder interface.

  • Review the device operating system information shown for the unit.

  • Confirm that the version now appears in a user-friendly format, such as Android 16.

  • Additional note: This improvement applies to supported views where tracked Android unit details are displayed.

• Use Case - When reviewing unit details during troubleshooting or device validation, a user can now immediately recognize the Android version without translating an API number. This makes it easier to confirm device compatibility, compare units, or communicate device details accurately.

Status Log Responder Names Are Easier to Read

• What - Responder names in the Incident Status Log now truncate with an ellipsis instead of scrolling horizontally when the display name exceeds the available space. The visible name length has also been improved to better use the available area while preserving other important elements such as response indicators, badges, timestamps, and status colors. This update brings Android behavior in line with iOS for a more consistent cross-platform presentation.

• Why - Horizontal scrolling made long names harder to read quickly and could distract from the surrounding status information. Truncating names creates a cleaner layout, improves readability, and helps users scan status entries more efficiently while maintaining the visual structure of the log.

• How

  • Open an incident and navigate to the Status Log.

  • Review entries that contain longer responder names.

  • Confirm that names now remain fixed in place and truncate with an ellipsis when necessary.

  • Additional note: Supporting indicators, badges, timestamps, and status colors continue to display as expected.

• Use Case - A user reviewing multiple status changes during an incident can now scan responder names more easily without waiting for text to scroll. This helps the user quickly identify who changed status while keeping attention on the full activity timeline.

Messaging Menu Now Opens the Full Message List

• What - Selecting Messaging from the app menu now correctly opens the full Messaging list view instead of displaying a popup. Accessing Messaging from the menu, shortcuts, or navigation bar now consistently loads the expected conversation list screen so users can immediately view all available conversations.

• Why - This fix corrects inconsistent navigation behavior and ensures users are taken directly to the main messaging area rather than an unexpected or incomplete view. It improves reliability across entry points and reduces confusion when launching Messaging from different parts of the app.

• How

  • Open the app menu, shortcut, or navigation entry for Messaging.

  • Select Messaging.

  • Confirm that the app opens the full Messaging list view.

  • Additional note: This corrected behavior applies across supported entry points, including menu access and other messaging shortcuts.

• Use Case - A user opening Messaging to check active conversations can now move directly into the full message list regardless of how they entered the module, making it easier to find the right thread and begin responding without extra navigation.

Dispatch Auto-Updates Now Preserve Scroll Position

• What - Automatic dispatch updates no longer reset the scroll position to the top of the screen while users are viewing dispatch details. Updates such as new call notes, unit changes, and incident updates now refresh in place so users can continue reviewing information without losing their place in the page. Manual refresh behavior remains unchanged when the user intentionally refreshes the view.

• Why - Resetting the screen position during automatic updates was disruptive, especially when users were reading long dispatch details or reviewing call notes. Preserving scroll position allows users to stay focused on the content they are viewing while still receiving updated information as it arrives.

• How

  • Open an incident or dispatch details view.

  • Scroll to the portion of the page you want to review.

  • Keep the page open while automatic updates are received.

  • Confirm that new dispatch information refreshes without forcing the page back to the top.

  • Additional note: Manual refresh actions still behave as designed and may reload the page view.

• Use Case - A user reading detailed call notes during a changing incident can continue reviewing the relevant section of the page even as new updates arrive. This prevents repeated scrolling and helps the user stay oriented during time-sensitive event monitoring.

All Calls Toggle Now Persists After App Restart

• What - The All Calls toggle in the Incident List now remains in its selected state after the app is closed, restarted, or the device is rebooted. The app preserves the setting until the user logs out or manually changes it, bringing Android behavior in line with iOS and making the selected filter more reliable across sessions.

• Why - Users expect filter preferences to remain consistent between sessions, especially when they regularly work with the same incident list view. Persisting the All Calls setting removes the need to repeatedly re-enable it and creates a more dependable experience for users who rely on that filter.

• How

  • Open the Incident List.

  • Turn the All Calls toggle on or off based on your preference.

  • Close and reopen the app, or restart the device.

  • Return to the Incident List and confirm the toggle remains in the previously selected state.

  • Additional note: The setting will remain in place until you log out or manually change it.

• Use Case - A user who prefers to monitor all calls can enable the All Calls toggle once and continue working without having to reset the filter every time the app is reopened. This saves time and helps maintain a consistent operational view.

Newly Added Group Members Can Now See Existing Chat History

• What - Newly added or re-added users in Firebase-based chat environments can now view existing group chat history when entering a conversation. The Android chat workflow was updated to load historical messages first and then continue listening for new messages in real time, ensuring the conversation appears complete when the user opens the group. This behavior now aligns with iOS for supported Firebase-based accounts, while no changes were needed for environments where current behavior was already consistent.

• Why - Users added to an existing chat need access to prior conversation context in order to understand ongoing coordination, instructions, and updates. Without that history, newly added members could miss important information and enter the conversation without the context needed to respond effectively. This fix improves continuity and consistency across platforms.

• How

  • Open Messaging and enter a group conversation after being newly added or re-added.

  • Allow the conversation to load.

  • Review the message thread and confirm earlier historical messages are visible before new real-time updates continue.

  • Open the same conversation from a notification if needed and confirm chat history is still available.

  • Additional note: Real-time messaging continues to function after historical messages are loaded.

  • Additional note: Behavior may vary by messaging environment where existing platform parity was already in place.

• Use Case - A user who is added back into an active group conversation can immediately review earlier messages to understand what has already been discussed, what actions were requested, and what updates have already been shared. This helps the user rejoin the conversation with full context and respond appropriately.

Incident Notification Navigation Reliability

• What - Fixed an issue where push notifications and in-app alert banners could update the navigation state without fully rendering Incident Details, causing the app to remain on the map while indicating the incident screen was active. The fix now ensures the complete deep link flow is executed so the relevant incident context is loaded, the Incidents area is activated, and the correct details screen or panel is shown consistently across foreground, background, and cold-start app states.

• Why - Users depend on notifications and alerts to jump directly into active incident information, and partial navigation behavior can delay response or create uncertainty about whether the incident actually opened. Correcting this issue improves reliability, restores expected behavior across entry points, and creates a more dependable response workflow.

• How

  • Open an incident from a Push Notification, In-App Banner, or supported acknowledge action.

  • The app now completes the full navigation flow automatically.

  • On phones, Incident Details will render directly.

  • On tablets, the incident details panel will expand as expected.

  • No user configuration is required for this fix.

• Use Case - A responder taps a push notification for a newly assigned call while the app is in the background. Instead of landing on the map with an incorrect navigation state, the app now opens the correct incident details view immediately, allowing the responder to review dispatch information without extra taps or uncertainty.

Dispatch “New!” Label Behavior

• What - Corrected the logic for the New! dispatch label so it is now cleared after an incident has been viewed, regardless of whether the user opened that incident from a push notification, in-app banner, or acknowledge action. This fix applies consistently across supported dispatch types while preserving the intended behavior of other status indicators such as Closed and Updated.

• Why - Dispatch labels are meant to reflect true incident status, and leaving the New! label visible after a dispatch has already been opened creates confusion and reduces trust in the indicator system. This update improves status accuracy and gives users greater confidence that the list reflects actual review state.

• How

  • Open a dispatch from any supported entry point, including Push Notification, Banner, or acknowledge workflow.

  • After the incident is viewed, return to the relevant dispatch or incident list.

  • The New! label will no longer remain on items that have already been opened.

  • Existing behaviors for other status labels continue unchanged.

• Use Case - A supervisor reviewing multiple incoming incidents from both banners and notifications can now rely on the dispatch list to show which items are still genuinely new. This helps prevent duplicate review and makes it easier to prioritize incidents that have not yet been acknowledged or opened.

WebView Stability on Samsung Devices Running Android 16

• What - Resolved a critical crash affecting Samsung devices running Android 16 where WebView initialization could fail and cause the app to close unexpectedly. The fix replaces the previous XML-based WebView implementation with a more stable programmatic setup that includes retry handling, and it also corrects an issue that caused PDFs and other WebView-based content to appear as blank screens.

• Why - WebView is used for important app content such as documents, SOPs, and externally rendered pages, so crashes or blank screens in this area significantly disrupt app usability. Addressing this issue improves stability in a high-risk area of the app and ensures users on affected devices can access critical content reliably.

• How

  • Open a document, SOP, PDF, or other WebView-based content in the app.

  • On supported Samsung devices running Android 16, the content should now load without the previous crash behavior.

  • Blank-screen behavior for supported WebView content has also been corrected.

  • No user action or setting change is required to benefit from this fix.

• Use Case - A user opening a PDF attachment or operational document from within the app on a Samsung device can now view the content normally instead of encountering a crash or empty screen. This is especially important when accessing reference material during active incidents or time-sensitive operations.

Map Icons Rendering Reliability

• What - Fixed an issue where map icons and markers were not loading or rendering consistently in Map View, even when valid data was available. This correction addresses a regression in the rendering flow so marker data is properly parsed, created, assigned to the appropriate layer, and displayed according to visibility and zoom-level rules, resulting in improved consistency with expected platform behavior.

• Why - Missing icons can make it difficult for users to interpret map activity, unit locations, or important overlays, especially during active response scenarios. Restoring reliable marker rendering improves map trustworthiness and ensures users can make better operational decisions based on visual data already available in the system.

• How

  • Open Map View in the app.

  • Pan or zoom to the area where markers and map icons are expected to appear.

  • Supported map elements should now display consistently when data is available.

  • Marker visibility will continue to follow configured zoom thresholds and layer settings.

  • No additional setup is needed for the corrected rendering behavior.

• Use Case - A field responder monitoring unit positions and incident-related map overlays can now rely on icons appearing consistently as they move through map areas and zoom levels. This reduces the chance of misinterpreting missing visuals as missing data and supports more confident decision-making in the field.