Daynis OlmanAI, Cloud & Digital Platform Leader

Guardian Live Mobile

An iOS and Android operational experience giving access to Guardian Live safety events, investigation workflows, alerts, statistics, feedback, onboarding and user settings.

From safety event to response in the field.

  1. 1. Safety event
  2. 2. Guardian Live services
  3. 3. Mobile workflow
  4. 4. Operational response
Evidence: Production systemMobile and safety technology· Seeing Machines
Role
Mobile architecture and delivery leadership
Serves
Guardian Live operational users.
Core technologies
Flutter · Riverpod · GoRouter · CI/CD

Executive overview

The problem. Safety operations teams needed critical Guardian Live workflows away from the desk, with the reliability expected of a production safety product.

Who it serves. Guardian Live operational users.

What Daynis did. Mobile architecture and delivery leadership. An iOS and Android operational experience giving access to Guardian Live safety events, investigation workflows, alerts, statistics, feedback, onboarding and user settings.

Why it matters. Extends critical safety operations into a reliable mobile experience, demonstrating production mobile architecture, release discipline and delivery leadership.

Business architecture and impact

Capabilities created

  • Safety event search and investigation on mobile
  • Alerts and notification workflows
  • Statistics, feedback, onboarding and settings
  • Localised experience

Extends critical safety operations into a reliable mobile experience, demonstrating production mobile architecture, release discipline and delivery leadership.

System architecture

  1. Operational users

    Where requests and source data originate.

  2. Flutter app (feature modules)

    The interface people use day to day.

  3. Riverpod, Dio, GoRouter

    Orchestrates requests and enforces business rules.

  4. Guardian Live services + Notifications

    Connections to downstream and third-party systems.

Governance: Authentication
Delivery: TestFlight & Google Play automation
A Flutter app organised by feature uses Riverpod for state, Dio for API access and GoRouter for navigation. Authenticated users search and investigate events and receive notifications. Builds ship automatically to TestFlight and Google Play, with release pipelines authenticating through Workload Identity Federation rather than long-lived keys.

Key flows

  • Operational users to Flutter app (feature modules)
  • Flutter app (feature modules) to Riverpod, Dio, GoRouter
  • Riverpod, Dio, GoRouter to Authentication
  • Riverpod, Dio, GoRouter to Guardian Live services
  • Notifications to Flutter app (feature modules)

Technical depth

Highlights

  • Flutter with a feature-oriented architecture
  • Riverpod, Dio and GoRouter
  • Authentication, event search and notifications
  • Localisation
  • Automated TestFlight and Google Play delivery using Workload Identity Federation

Architecture decisions

Feature-oriented structure

Code is organised by feature so teams can change one workflow without destabilising others.

Keyless release pipelines

Workload Identity Federation lets release automation authenticate without stored long-lived credentials.

Security and governance

  • Authenticated access to safety data
  • Release automation without long-lived secrets

What I led

  • Mobile architecture ownership
  • Release engineering and delivery governance
  • Cross-functional collaboration with product and platform teams

Evidence and links

Evidence: Production systemDelivered as a production system.

Building something similar?

Talk to Daynis about mobile and safety technology architecture and delivery.

Start a conversation