Skip to content

Mobile / Custom Software

FieldOps Mobile

Offline-First Field Service Application

An iOS and Android application for field crews working without connectivity, with conflict-safe sync and photographic proof of work.

  • React Native
  • TypeScript
  • Node.js
  • PostgreSQL
  • Firebase
Abstract mobile application layout showing job cards and synchronisation states

Overview

Project Overview

Field crews were completing jobs on paper because every previous app assumed a connection. FieldOps treats offline as the normal case: the entire day's work is available on the device, evidence is captured locally, and synchronisation resolves conflicts deterministically when signal returns. Dispatch sees progress as it syncs rather than at the end of the day.

Services provided

  • Mobile App Development
  • Custom Software Development
Client
Confidential — utilities maintenance contractor
Industry
Manufacturing
Timeline
13 weeks
Year
2024
Platforms
iOS, Android, Web dispatch console
Team
2 engineers, 1 designer, 1 delivery lead

Challenge

The Challenge

Crews worked in basements, rural sites and industrial buildings with no reliable signal. Two previous applications had been rejected by the field team.

  • Connectivity was absent or intermittent for most of a typical working day.

  • Earlier apps lost work when a submission failed, so crews reverted to paper.

  • Paper job sheets were re-keyed in the office, adding a day of lag and transcription errors.

  • Proof of work was inconsistent, which caused billing disputes.

Solution

What We Built

We designed for the disconnected case first and treated connectivity as an optimisation, not a requirement.

  • Made the device the source of truth for an in-progress job, with a local database as primary storage.

  • Defined explicit per-field conflict resolution rules rather than last-write-wins.

  • Queued evidence uploads with resumable transfer and background retry.

  • Delivered form definitions from the server so new job types ship without an app store review.

  • Ran a two-week pilot with the crews who had rejected earlier apps, and changed the interaction model based on it.

Capabilities

Key Features

What FieldOps Mobile does in day-to-day use.

  • Full offline capability

    The complete day's schedule, forms and reference material available with no connection.

  • Conflict-safe sync

    Deterministic resolution rules per field, so simultaneous edits never silently lose data.

  • Evidence capture

    Photos, signatures and readings captured locally with location and timestamp metadata.

  • Dynamic job forms

    Form definitions delivered from the server so new job types need no app release.

  • Route awareness

    Cached mapping and ordering so navigation works in areas with no data coverage.

  • Dispatch visibility

    Job status streams to the office as it syncs, with clear indication of stale data.

Stack

Technology Stack

The tools this system runs on, grouped by the role they play.

  • Mobile

    • React Native
    • TypeScript
    • SQLite

  • Backend

    • Node.js
    • REST API
    • Background workers

  • Data

    • PostgreSQL
    • Object storage

  • Services

    • Firebase Cloud Messaging
    • Map & geocoding APIs

  • Infrastructure

    • Docker
    • GitHub Actions
    • Over-the-air updates

Architecture

How It Works

The path a single request takes through the system, end to end.

    ASSIGN01

    Dispatch schedules

    The day's jobs are assigned and pushed to the device.

    CACHE02

    Download for offline

    Jobs, forms and map tiles cached locally before the crew leaves.

    WORK03

    Complete on site

    Forms, photos and signatures captured to the local database.

    SYNC04

    Reconcile

    Queued changes upload with per-field conflict resolution.

    CLOSE05

    Billing handoff

    Completed jobs and evidence flow into invoicing automatically.

Outcome

Results

What changed for the business after launch.

  • 100%

    Jobs completed in-app

    Paper job sheets eliminated across the pilot region.

  • 1 day → live

    Dispatch visibility lag

    Status arrives as it syncs rather than after re-keying.

  • 0

    Jobs lost to sync failure

    Measured across the first six months of operation.

  • 91%

    Crew adoption in month one

    After two previous applications had been abandoned.

Interface

A Closer Look

Screens from the delivered system.

  • Daily job list on a mobile device
    The full day's work, available with no connection.
  • Job evidence capture screen
    Evidence capture with location and timestamp metadata.
  • Synchronisation status view
    Sync state is always explicit — never a silent failure.

More work

Related Projects

Other systems built on similar foundations.

View all projects
  • Abstract mobile route execution layout with ordered stops and status indicators

    Mobile / Logistics

    RouteLens Driver App

    A driver application for route execution, exception handling and proof of delivery, with live progress streaming to dispatch.

    • React Native
    • TypeScript
    • Node.js
    • PostgreSQL
    • +1

    View Case Study

  • Abstract diagram of a multi-agent voice routing system with connected conversation nodes

    AI / Voice / Multi-Agent

    VeriVoice

    An intelligent multi-agent voice platform designed to automate business conversations and workflows.

    • React
    • Next.js
    • Node.js
    • AI
    • +1

    View Case Study

Next step

Want a System Like This?

Tell us what your business needs to automate and we'll map out a practical build.

Book a Free ConsultationContact Us

hello@devrox.comWe reply to every enquiry within one business day.