← back to work04 / FREELANCE · CLIENT DELIVERY

Electronic Kuna

A field service business running installations, servicing and surveillance across several crews — scheduling, job records and costs in one internal system, on desktop and in the field.

ROLE
Everything (solo contractor)
PERIOD
2025–2026
STACK
React Native · Electron · Node.js
LIVE
Internal — not public
The daily dispatch — every crew's jobs for one date, with customer, address, notes and cost
The monthly schedule — jobs by date and assigned crew, with urgent work flagged
Service records — recurring servicing by type and date, tied back to the job and customer
The fleet — registration, inspection, permit and extinguisher expiry counted down per vehicle

THE CONTEXT

The office schedules the work; the crews carry it out on the road. Both need the same job records, but they need them in completely different shapes — a full day's dispatch across every team on one side, one technician's next job on the other. One backend, two very different surfaces.

WHAT I DID

  1. 01

    One backend, three surfaces

    A Node.js REST API behind a React Native app for the crews and an Electron desktop app for the office, sharing a single data model.

  2. 02

    Daily and monthly dispatch

    Jobs grouped by crew and by date with urgent work flagged, so the office sees the whole schedule and a technician sees their own.

  3. 03

    The job record

    Customer, address, dates, notes, assigned crew and price on a single card — from booking through to archive.

  4. 04

    Beyond the schedule

    Vehicles, parts, expenses and notifications alongside the work, so the real cost of a job sits with the job.

  5. 05

    Delivered direct

    Requirements gathered with the client, built and shipped solo, then iterated against daily use.

OUTCOME

One internal platform the office and the field crews both run on — mobile, desktop and API, delivered end to end by one person.

NEXT PROJECTZIK Analytics→