Illustration: a crew phone with a safety checklist works offline aboard a container ship; queued changes sync to a fleet overview.

Key figures

maritime workers supported in production
4,000+
maritime operators using it in production
DFDS, Shell

How the offline loop works

  1. On board

    • Safety workflows
    • Saved on the device first
  2. When a connection returns

    Sync queue

    • Changes sent in order
    • Nothing lost offline
  3. Backend

    • Changes reconciled
    • One operational record
  4. In production

    • Used by crews at sea
    • Repair and iteration under real use
Workers keep working without a signal. Their changes queue on the device and reconcile when the vessel reconnects. As fractional CTO, Kuan led the product, application, backend, and operations.

“Kuan’s expertise paved the way for our growth and enabled us to acquire the trust of external investors and, as a consequence of that, additional funding.”

Yassin Askar Co-Founder & CPO, Scoutbase

Operating problem

A maritime workforce product had to work in remote environments where connectivity, trust, and operational accuracy mattered more than a polished demo.

What changed

The product system was shaped around offline-first use, reliable synchronization, worker-facing UX, and production operation rather than handoff-heavy feature delivery.

System scope

  • Product workflow definition for maritime safety operations
  • Offline-capable application behavior and synchronization queues
  • Frontend and backend production implementation
  • Operational repair, iteration, and support over real usage

Technical constraints

  • Keep frontline workflows trustworthy when vessels move between reliable, intermittent, and absent connectivity.
  • Reconcile queued offline changes without losing operational state or confusing the worker using the product.
  • Evolve the application and backend under real usage while preserving supportability for thousands of workers.

Evidence

In production with maritime operators including DFDS and Shell.

Need a delivery partner for your software project?

Share the market, constraint, current state, and budget reality in writing. If it looks like a fit, you will get a human response with the next step.

Start a project
Next case study Lane Technologies Tenant-experience product systems and mobile delivery workflows for a high-growth real estate technology company.