Field-service app for a heating & cooling business
The owner runs a heating and cooling company with eight technicians. Every morning they called the office to get their jobs, and every evening they called again to say what they had done. The owner wanted that to stop.
He wrote a one-page brief: technicians need their daily jobs on a phone, and they need to update status without calling the office. The developer started there.
Round one: the job list
The developer turned the one-page brief into a first build. When it ran, the job list appeared on a phone-sized screen, with each job's address and customer name. The owner watched it and said the list was right, but the technicians would also need a job's history — what had been done there before.
The developer wrote that down: add a history panel, and check the next build on a phone, not just on a desktop.
Round two: the false start
The next build put the history where the office could see it. The build ran, and the try came back green on the desktop. But the owner's tech was in a basement and had no way to reach an office screen. The history moved to the phone, where it was one tap away.
Round three: the live schedule
With the history on the phone, the developer watched the schedule update in real time on the tablet in the owner's office. A technician marked a job done from a driveway, and the office saw it change seconds later.
The owner looked at one screen and saw everything waiting on him: parts to order, calls not yet returned, a technician idle since noon. The technicians stopped asking "Did you get the latest job?" each morning, because the answer was already on their phones.
Round four: the caught change
Later, the developer changed the status field from done to completed. The try-it caught that the office tablet still looked for done, so the live schedule would have stopped refreshing the moment a tech marked a job complete. The fix went in before anyone in the field heard about it.
Round one — asked for job history. Why: a tech needs what was done before. Round two — moved the history to the phone. Why: a tech in a basement couldn't reach the office screen. Round three — live schedule. Why: the office needs to know the moment a job is done. Round four — renamed done to completed. Why: the try-it caught the office tablet still polling for done.
The developer kept the brief, the rounds, and the decisions in one dated trail, so anyone could walk back and see why the history moved to the phone — and what the try-it caught before it reached a truck.
Request access