Selected work01 / 04

All work
Hand holding a smartphone displaying a dark mobile app interface

Mobile · Web · Field operations

Atlas Dispatch

Year
2025
Status
In production
Timeline
26 weeks
Role
Product design, mobile and web engineering, cloud infrastructure

Overview

Atlas Dispatch connects an operations desk with technicians in the field: a web console for the office and a mobile app for the team on site.

Challenge

Jobs were handed out by phone and tracked in spreadsheets. Technicians often had no signal, so updates came late or not at all, and the office couldn’t see who was where.

Programmer working on a laptop and external monitor

Solution

One shared job model for both apps. A mobile app that works offline and syncs when signal returns. A live dispatch board that flags conflicts before they happen.

Product

  • 01Offline job sync with conflict handling
  • 02Live dispatch board, drag to assign
  • 03Photos, signatures and checklists on site
  • 04Separate access for office and field
Team gathered around a whiteboard during a planning session
Fig. A: Mapping the workflow with dispatchers
Hand holding a smartphone displaying a dark mobile app interface
Fig. B: Technician app, job detail

Technology

  • React Native
  • TypeScript
  • Node.js
  • PostgreSQL
  • Redis
  • AWS

System architecture

  1. 01Clients

    • iOS / Android app
    • Dispatcher console

  2. 02API

    • GraphQL gateway
    • Auth service

  3. 03Services

    • Jobs
    • Sync engine
    • Notifications

  4. 04Data

    • PostgreSQL
    • Redis
    • Object storage

Timeline: 26 weeks

  1. Discovery

    3 wks

  2. Design

    5 wks

  3. Build

    16 wks

  4. Launch

    2 wks

Outcome

Dispatchers work from one live board. Technicians close jobs with or without signal. It’s in production and still growing.