iOS Version: 5.9.7

New Features

Time Card Access from Mobile

• What - Added a new Time Card option within the mobile app’s Scheduling menu, allowing users to access the web-based Time Card feature directly from their device. The feature includes permission-based visibility, consistent navigation across entry points (menu, shortcuts, and pinned pages), and supports dynamic updates when permissions change, ensuring reliable and consistent access across devices and sessions.
• Why - Providing direct access to Time Card functionality from mobile improves operational efficiency by allowing personnel to manage time tracking without needing to switch platforms. Permission-based visibility ensures appropriate access control while maintaining consistency with existing scheduling workflows.
• How
  • Open the Responder Mobile App
  • Tap the Menu
  • Navigate to Scheduling
  • Select Time Card
  • The Time Card web view will open within the app
  • Note:
    • Visibility is controlled by the personnel_shift_timecard permission
    • The feature may also be accessed via shortcuts or pinned pages if configured
• Use Case - A supervisor or responder in the field can quickly access their Time Card from the Scheduling menu to review or manage shift entries without needing to log into a separate web system, improving efficiency during daily operations.

Feature Enhancements

Map Layers Experience Redesign 

• What - The Map Layers experience was fully redesigned using SwiftUI to improve performance, consistency, and reliability when managing map data in the app. This update improves how responders interact with layer controls for items such as hydrants, preplans, and other map information, while also improving map behavior across Google Maps and ArcGIS. The redesign addresses UI and interaction issues such as spacing, animations, and layer name truncation, and it strengthens support across iPhone and iPad, different device orientations, and offline scenarios. Layer selections and map preferences now also persist more reliably across sessions, account changes, and app restarts.
• Why - This enhancement was made to provide a faster, more dependable, and more consistent map experience for responders who rely on map layers in time-sensitive situations. By modernizing the screen with SwiftUI and improving persistence, offline behavior, and cross-device consistency, the app reduces friction when accessing critical map data and helps users work more efficiently in the field.
• How
  • Open the map within the mobile app.
  • Select the Layers controls to view available map layer options.
  • Turn individual layers on or off for items such as Hydrants, Preplans, and other supported map data.
  • Confirm that layer visibility updates in real time on the map.
  • Notes:
    • Layer selections and preferences now remain more consistent across app restarts and account changes.
    • The updated experience is designed to work more reliably across iPhone, iPad, multiple orientations, and offline conditions.
• Use Case - A responder preparing for an incident can quickly open the map, enable hydrants and preplans, and confirm that the correct layers appear immediately without needing to reconfigure settings after restarting the app. This helps provide a more reliable operational view whether the responder is using an iPhone in the field, an iPad in a vehicle, or working in an area with limited connectivity.

iOS 26 SDK Compatibility Update 

• What - The app was updated to use the iOS 26 SDK to meet Apple App Store requirements and support continued submission and distribution. This update also improves compatibility with newer iOS versions while maintaining stable performance across supported devices and form factors, and it ensures the app can build and upload successfully without SDK-related compliance issues.
• Why - This enhancement was necessary to keep the app aligned with Apple platform requirements and to ensure continued availability through the App Store. Updating the SDK also helps maintain a stable experience for users on newer iOS versions and reduces the risk of submission delays or compatibility issues.
• How
  • Update the app to the latest available version from your organization’s standard deployment process.
  • Open the app on a supported iPhone or iPad running a supported iOS version.
  • Continue using the app as normal; no feature enablement is required for this improvement.
  • Notes:
    • This is a platform compatibility update and does not require additional configuration by end users.
    • The update supports continued app submission and distribution requirements from Apple.
• Use Case - An agency deploying the latest version of the app can continue distributing updates to users without interruption from Apple SDK requirements. Responders using newer iOS devices can also continue working in the app with improved platform compatibility and without changes to their normal workflow.

Incident View Time and Timestamp Improvement

• What - The Incident View clock and timestamp display were updated to improve clarity and consistency. Time formatting now respects client-configured settings when available, with a default to military time when no configuration is provided. The “Last Updated” timestamp was also renamed and moved to the top of the screen to make data freshness easier to identify, improving readability for time-sensitive incident information.
• Why - This enhancement was made to reduce confusion around incident timing and to help responders assess current information more quickly. Clearer formatting and more prominent placement of update timing improves situational awareness and reduces the cognitive effort required to interpret critical timestamps during active response operations.
• How
  • Open an incident in Incident View.
  • Review the primary date and time information displayed on the screen.
  • Look at the top of the screen to view the Last Updated timestamp.
  • Confirm that time formatting follows your configured format when available.
  • Notes:
    • When no client-specific time format is configured, the app defaults to military time.
    • The Last Updated timestamp is now surfaced more prominently for faster visibility.
• Use Case - A responder reviewing an active incident can immediately confirm when the information was last refreshed and interpret times using the expected format for their organization. This makes it easier to determine whether dispatch details, status changes, or scene information are current while operating under pressure.

Dev Info Screen Content Refresh

• What - The Dev Info screen was updated to display current and accurate application details, including replacement of outdated support email information with the correct contact details. This improves the accuracy, clarity, and consistency of information shown within the screen.
• Why - This enhancement was made to remove outdated reference information that could create confusion for users seeking application details or support contacts. Keeping static information current helps ensure users receive accurate guidance when referencing the Dev Info screen.
• How
  • Open the app menu.
  • Navigate to Dev Info.
  • Review the application details and support contact information shown on the screen.
  • Notes:
    • No setup is required for this update.
    • The improvement is limited to the accuracy and presentation of static informational content.
• Use Case - A user verifying app version details or looking for support contact information can open the Dev Info screen and trust that the information presented is current. This helps reduce confusion and improves confidence when reporting issues or confirming app details.

iOS 26 “Liquid Glass” Map Layers Toggle Spacing Improvement

• What - The Map Layers interface was refined to fix an issue where toggle buttons could overlap or crowd nearby text labels under the iOS 26 “Liquid Glass” design. The update improves spacing, readability, and layout consistency so layer names and controls display more cleanly across supported devices and iOS versions.
• Why - This enhancement was made to preserve readability and usability after visual changes introduced by iOS 26. When controls and text crowd together, users can have difficulty identifying or selecting the correct layer options, especially in fast-moving situations where quick interpretation is important.
• How
  • Open the map and access Layers.
  • Review the list of available map layer options.
  • Use the toggle controls to enable or disable layers as needed.
  • Confirm that toggle buttons and text labels display with consistent spacing.
  • Notes:
    • This update is especially relevant on devices using the newer iOS visual styling.
    • No additional configuration is required.
• Use Case - A responder adjusting multiple map layers during an incident can quickly read each layer name and select the correct toggle without visual crowding or confusion. This creates a cleaner and more dependable interface when rapid map adjustments are needed.

iOS 26 “Liquid Glass” Web View Button Styling Improvement 

• What - An issue affecting Web View control buttons was fixed so that the Increase, Decrease, and Refresh controls no longer display with incorrect circular styling under the iOS 26 “Liquid Glass” interface. This restores a more consistent button appearance and maintains proper functionality across Web Views, including settings and authentication screens, on both iPhone and iPad.
• Why - This enhancement was made to maintain a consistent and predictable interface after iOS 26 design changes affected button presentation. Correct button styling helps users recognize available actions more easily and supports a more polished and reliable experience across app screens that use Web Views.
• How
  • Open any supported screen that uses a Web View, such as settings or authentication-related pages.
  • Locate the Increase, Decrease, and Refresh controls.
  • Use the controls as needed to confirm they display and function correctly.
  • Notes:
    • The update applies across supported iPhone and iPad devices.
    • No feature enablement is needed for this improvement.
• Use Case - A user accessing a settings or login-related Web View can immediately recognize the available controls and use them without distraction from incorrect visual styling. This improves usability and creates a more consistent experience across the app’s embedded web-based screens.

SwiftUI Interface Modernization

• What - Continued modernization of the mobile application through expanded migration from UIKit to SwiftUI using an MVVM architecture. This release includes migration of the App Menu, Responding Status Bar, Active Preplan Level Info View, Units Tab, Unit Filters, Route Indications (compact and detailed views), Map Zoom Level Indicator, and Street View experience. Additionally, legacy UIKit navigation bridges were removed in favor of native SwiftUI navigation, improving consistency across screens. All components maintain full feature parity while enhancing UI responsiveness, state management, and real-time data handling across navigation, mapping, and unit management workflows.
• Why - Migrating to SwiftUI reduces reliance on legacy frameworks, simplifies the codebase, and improves long-term maintainability. This effort enables more consistent UI behavior, better performance, and faster delivery of future enhancements while ensuring reliability in real-time operational workflows such as incident response, navigation, and unit tracking.
• How
  • Open the Responder Mobile App
  • Use the following features as part of normal workflows:
    • Access the Menu to navigate application features
    • View and manage units in the Units Tab
    • Apply filters using Unit Filters
    • Begin responding to an Incident to view the Responding Status Bar
    • Open the Map to:
      • View Route Indications (compact or expanded)
      • See the Zoom Level Indicator during map interactions
      • Access Street View for supported locations
    • Open a Preplan and switch levels to view the Active Preplan Level Info
  • Navigation between screens now uses native SwiftUI components
  • Note: All existing functionality, permissions, and workflows remain unchanged
• Use Case - A responder navigating to an incident can seamlessly move between the Units tab, map routing, and incident details while viewing real-time updates. The updated SwiftUI components ensure smoother transitions, consistent UI behavior, and reliable display of critical information such as routes, unit statuses, and preplan data, improving efficiency during active response scenarios.

Incident List UI Redesign

• What - The Incident List interface has been redesigned to improve readability, accessibility, and overall situational awareness. Incident cards now emphasize the incident address with stronger visual hierarchy and include the city name to assist with mutual aid awareness. Units assigned to an incident are displayed as individual pill-style badges rather than plain text, making it easier to quickly scan responding resources. The card layout has been refined to provide clearer spacing and improved contrast, and the highlight bar indicating incident state has been repositioned for a more modern and consistent visual presentation that aligns with current web Responder user experience standards.

• Why - The previous incident list layout made it difficult to quickly identify key information during active operations, especially when multiple units or jurisdictions were involved. The redesign improves scanning speed, readability, and accessibility while maintaining familiar interactions. The update also aligns the mobile interface with broader platform design standards to ensure a consistent experience across devices.

• How

  • Open the Responder Mobile App

  • Navigate to the Incident List

  • View incident cards displaying:

    • Bold incident address for quick identification

    • City name for improved jurisdiction awareness

    • Unit pill badges representing responding units

  • Tap an Incident Card to open incident details

  • Swipe an Incident Card to hide it if needed

  • Note: Existing incident list interactions and behaviors remain unchanged

• Use Case - During a multi-agency response, personnel reviewing the Incident List can quickly identify the correct incident by the emphasized address and city while easily scanning which units are assigned using the pill-style unit badges. This allows responders to assess the situation faster and reduces the chance of selecting the wrong incident when multiple calls are active.

Unit Status Colors on Incident List

• What - The Incident List now displays dynamic color coding for units based on their real-time status. Unit badges automatically update with status-specific colors that match the status visualization used within the Incident Details view. In addition, incident status indicators such as New, Updated, and Closed are displayed with corresponding color-coded labels and highlight bars to provide immediate visual feedback when incidents change state.

• Why - Quickly understanding unit status is critical during active operations. By applying consistent color-coded status indicators across the Incident List and Incident Details views, users can instantly interpret unit activity and incident state without needing to open additional screens. This improves situational awareness and reduces the time required to interpret dispatch updates.

• How

  • Open the Responder Mobile App

  • Navigate to the Incident List

  • Observe unit badges displayed as pill indicators

  • Unit pills automatically change color based on real-time unit status

  • Incident cards may display labels such as New, Updated, or Closed

  • These labels update automatically based on dispatch updates received through real-time data

  • Note: Status indicators clear automatically after the incident is viewed or refreshed

• Use Case - A responder reviewing the Incident List during a busy shift can immediately recognize which units are actively responding or available by the color of the unit badges. When an incident receives new dispatch information, the Updated indicator highlights the change, allowing personnel to quickly open the incident and review the latest details.

Events & Activities Menu Update (iOS)

• What - The Activities menu has been renamed and reorganized as Events & Activities to better reflect the functionality available in this section. The update consolidates related functionality and introduces Daily Operations, which opens the activities list page directly. Legacy menu items such as Activity Log and Events List have been removed.

• Why - The previous menu structure separated related operational tools across multiple items, which could create confusion when navigating the app. Consolidating these items under a unified Events & Activities section improves discoverability and aligns the menu structure with current operational workflows.

• How

  • Open the Responder Mobile App

  • Tap the Menu

  • Select Events & Activities

  • Tap Daily Operations to open the activities list

  • Note: Visibility of this section is controlled by the activities_activity_log permission

• Use Case - A supervisor reviewing daily operational activities can quickly access the Daily Operations list through the Events & Activities section without needing to navigate through multiple legacy menu items.

Fixes

Database Migration Stability and Error Handling

• What - Improved the database migration system to prevent crashes and database corruption during application upgrades. Migrations are now wrapped in transactions, include explicit error handling, and only update the database version after a successful migration. If a migration fails, the system logs the issue and safely recreates the database to restore a stable application state.

• Why - Some users experienced crashes or corrupted local databases during upgrades, particularly when migrating from older versions with multiple accounts. The updated migration process improves reliability and ensures the application can recover safely from migration failures.

• How

  • Update the Responder Mobile App to the latest version

  • Launch the app after installation

  • If a database migration is required:

    • A loading indicator appears while the migration runs

    • On success, the app automatically opens the Map

    • On failure, the system recreates the database and routes the user to the Login screen

  • Note: Migration errors are logged automatically for diagnostic review

• Use Case - When a user upgrades the mobile app from an earlier version, the system safely migrates stored data. If a migration issue occurs, the application automatically recovers by rebuilding the database and allowing the user to sign in again, preventing crashes or corrupted data.

SSE Reconnection After App Lifecycle Changes

• What - Fixed an issue where dispatch updates delivered through Server-Sent Events (SSE) would stop after certain app lifecycle transitions such as moving the app to the background and returning to the foreground. The application now automatically reconnects to the SSE stream when the app becomes active again.

• Why - Real-time dispatch updates are critical for operational awareness. When SSE connections failed to reconnect after lifecycle changes, users could stop receiving updates until the app was restarted. The fix restores reliable automatic reconnection behavior.

• How

  • Open the Responder Mobile App

  • Navigate to the Incident List or Incident Details

  • Send the app to the background

  • Return the app to the foreground

  • The system automatically reconnects to the dispatch update stream

  • Note: No user action is required to restore updates

• Use Case - A responder briefly switching to another application while responding to an incident can return to the Responder app and immediately continue receiving dispatch updates without needing to restart the application.