All work

    Client work · under contract

    Dirt Burner Monitor

    A paper burn log, replaced by a native iOS app

    Year
    2026
    Role
    Sole developer: spec, build, backend, App Store delivery

    Published 2026-07-23 · Updated 2026-11-09 · By Kai Myers, K.AI Consulting

    The problem

    The client runs a dirt burner: a thermal remediation plant that heats contaminated soil until it is clean. Operators record readings off a control-room chart recorder every hour, by hand, onto a paper Daily Burn / Maintenance log. Paper works right up until you need to find something in it: a reading from three weeks ago, proof that a temperature excursion was caught and acted on, or a shift record that has gone home in somebody's truck.

    The readings themselves are not optional. They are how the plant knows it is operating inside its permitted envelope, and how it demonstrates that after the fact.

    Dirt burner monitor home screen showing shift, hourly reading, burn, and dashboard entry points
    Shift hub, with the open shift and active burn at the top
    Dirt burner monitor hourly reading capture screen
    Guided hourly capture, ordered to match the control-room board sweep
    Dirt burner monitor alert limits configuration screen with threshold values blurred
    Per-reading caution and alarm thresholds (client setpoints blurred)

    Screens captured from a demo account. The client's process setpoints and operational readings are blurred or absent.

    What I built

    A native iOS app that mirrors the control-room recorder screen-for-screen, so an operator trained on the paper log already knows where everything is. Hourly capture is guided: the app asks for each reading in the same order the board is swept.

    Every reading is classified into a three-zone scheme (in range, caution, alarm) with per-supervisor configurable thresholds. Classification happens twice: once on the device for immediate feedback, and again server-side, authoritatively, so an out-of-range value cannot be missed because a phone was offline or a threshold was stale.

    Alerts fan out per recipient, deduplicated, over both push and email. Supervisors choose their own channels. Photo evidence is time-stamped and attached to the reading it belongs to, and each shift closes into a PDF.

    The whole thing is offline-first. An operator in a plant with bad signal keeps working; a client-UUID-keyed outbox syncs in order when connectivity returns, tolerating photo upload lag without duplicating or reordering records.

    Where it landed

    • On the App Store, and used by the client's crew through the 2026 season
    • Hourly readings, photos, and a PDF and CSV for every shift in one place
    • Out-of-range readings rechecked on the server and sent to supervisors by push and email
    • Built to cut time on paperwork and to make an old reading easy to find when a supervisor or inspector asks
    • Offline capture with ordered sync when the signal comes back

    Built with

    Expo SDK 54Expo RouterReact NativeNativeWindSupabase (Postgres · Auth · Storage · Edge Functions)TanStack QueryResendEAS Build

    Decision-support only. The app is not a safety interlock, a CEMS-certified instrument, or a regulatory reporting system, and the client remains responsible for plant operation, safety, and compliance. Client not named.

    Got a problem shaped like one of these?