FieldOS, Part 3: The App People Open, and What 10 Hours Taught Me About Pricing
Everything in this series so far — the jobs, the parts, the dispatch board, the nine add-ons — runs quietly in the background. None of it matters if the people actually doing the work can't get to it. A technician standing in a parking lot needs a screen that works on his phone. A dispatcher juggling six trucks needs to see the whole board at once. A customer who just wants to know when someone's…
FieldOS, Part 3: The App People Open, and What 10 Hours Taught Me About Pricing
Everything from the previous articles — the jobs, add-ons, and dispatch board — functions smoothly in the background. However, if the people executing the work cannot access these features, they become irrelevant. A field technician requires a phone screen that functions, a dispatcher needs to view the entire board simultaneously, and a customer should not have to provide a password to discover when a technician is arriving.
Thus, the final component focused on creating the actual application that everyone uses — a single login with distinct views tailored to each role, all built atop the foundation established in the first two parts.
One App, Every Role: Thirteen distinct views operate under one login, each catering to specific job requirements without unnecessary information.
A Technician's Day in the Field: Time tracking is now directly linked to the job itself—clock in upon job commencement and clock out upon completion, with this data automatically integrated into the invoice from Part 1.
Dispatcher's Board: All open jobs, technicians' schedules, and the ability to assign and reassign tasks with just a few taps, without the need for phone calls or whiteboard adjustments.
What Customers See: A customer who reported an issue using the public form from Part 2 can login and monitor the status of their issue from reported to assigned to completed, viewing any quote awaiting their approval – no complicated bookkeeping or inquiries about updates.
Try It Yourself: A public demo login resets the entire system to a pristine state with each login, allowing anyone to interact as a technician, dispatcher, or customer, without affecting actual data.
Overcoming the Friction: Wiring an interface on top of a working system uncovers issues that isolated testing might miss. Each of these problems was identified through actual user interactions, not just code reviews.
The parts inventory screen would sort and flag low stock incorrectly, erroneously reporting that a count of 14 was lower than a count of 5. This issue arose because the quantities were incorrectly treated as words rather than numbers during processing, causing alphabetical sorting rather than numerical ordering (14 reads as less than 5, similarly to how "apple" is less than "banana"). Once identified, a straightforward fix resolved the problem across all relevant areas.
A maintenance schedule saved for the 15th was showing as the 14th in the calendar field due to the plain date format lacking explicit time information and defaulting to a time zone that shifted the date back by one day. This was corrected by explicitly including time on every date moving forward, a simple but essential change.
A filing cabinet named the same as a web page caused an error when opening the equipment page or refreshing it. The app's internal storage folder coincidentally shared a name with the web address of that page, leading to conflicts. Renaming the internal folder resolved the issue universally.
Eighty-three unnecessary invoices generated by the demo's automatic invoice-drafting feature went unnoticed. The demo, intended to provide a clean starting point, inadvertently created 83 fake draft invoices during test jobs. This was fixed by updating the reset function to also clear these false invoices, and confirmed by running the reset twice consecutively to ensure the count remained unchanged.
The core of FieldOS — incorporating all features from Parts 1 and 2 into a single, functional application — took under five hours to complete, tracked meticulously as real time, from planning through to bug fixing, with no rounding of hours. Summing the time spent across all three parts of this series, the total comes to approximately ten hours — not ten weeks — for creating a comprehensive field service platform that connects every role from the technician in the field to the customer at home.
This showcases FieldOS as a fully operational system, streamlining workflows and significantly reducing the time needed to develop such a system from months to mere hours.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
