Module: technician web app

A Technician Web App on the Phone Already in Their Pocket: Jobs, Photos, Signatures, Payments and an Honest Scope

The technician app is where software meets a crawlspace. It has to work with gloves on, in bad light, with one bar of signal, for someone who would rather be fixing the unit. That makes it the module we scope most narrowly and test most carefully.

November 12, 2026 · 9 min read

app.acmeheatingandair.com · tech phone sync
One job, one basement, one bar of signal
Everything saved, one payment waiting on signal
  1. 07:42 day loaded: 5 jobs, notes and history saved on phone
  2. 09:10 job 4471 status: on site (no signal, queued)
  3. 09:31 6 photos and 2 notes saved on device
  4. 09:48 customer signature captured, option 2 chosen
  5. 09:50 card payment needs a connection: held
  6. 10:04 signal back: status, photos, signature sent
  7. 10:05 payment link texted to customer
Illustrative: a sample sync log for a fictional HVAC technician's phone

The short answer

A technician web app opens from a link on the phone a tech already carries, with no app store. It shows the day's jobs, job details and history, and takes photos, notes, signatures and payments. It is the heaviest module, largely because of weak signal in attics and basements. Version one can skip inventory, purchase orders and payroll. From $575, depending on complexity; this module lands well above that floor.

On this page
  1. One bar of signal, an attic at 130 degrees, and a phone in a glove
  2. What ServiceTitan's own help center says needs a connection
  3. The screens a technician touches on every job
  4. Left out of version one, on purpose
  5. Why this module is the heavy lift on the menu
  6. A link on the home screen instead of an app store listing
  7. Two techs first, then the fleet, then the bill

One bar of signal, an attic at 130 degrees, and a phone in a glove

The technician is kneeling beside an air handler in an August attic. The job needs the model number from the last visit, a photo of the cracked drain pan, and a signature before anyone climbs down. The phone shows one bar. Whatever software is on that phone gets about four seconds of patience, and it will spend them loading a logo.

This is the job a field app exists for, and it is hard. Companies keeping ServiceTitan's app can still close small gaps, and we wrote about custom tools for technicians who already carry ServiceTitan. ServiceTitan has spent years on it. Its Field Mobile App page, as read November 10, 2026, calls it "The all-in-one technician app for all of your jobs," says techs can "access job details, complete forms, capture photos, create estimates, and process payments," and describes it as "fully native" on iOS and Android phones and tablets. The same page lists AI features, including "Atlas in Mobile," translation into English and equipment model and serial number scanning.

A custom technician app will not match that list in its first version, and it should not try. What it can do is the core of the job, on the phone the tech already owns, inside an app your company owns, without a per-technician license for every new hire. It is one module of a custom field service app, and we tell every owner the same thing: build it after the easier modules, not before.

What ServiceTitan's own help center says needs a connection

Offline work is the hardest part of any field app, so it is worth reading what the most established vendor says about its own. In the commercial and construction FAQ on its product page, ServiceTitan says "the Field Mobile App and all its features are available in offline mode." Its help center is more precise. In an article published October 29, 2026, ServiceTitan says "Most core workflows" work offline and sync later, and lists job status updates, time tracking, signatures, notes, photos and estimates.

  • "A small number of features require an active internet connection, including purchase orders, customer Financing, contracts, and inventory availability."
  • "Payments captured offline are not finalized until the device reconnects."
  • "Standard price book pricing works offline. Dynamic pricing rates require a connection to load."
  • Invoice editing offline is "Partial": "Adding or editing tasks, price modifiers, and tax zones requires a connection."
  • Sending an e-signature request link "requires a connection."

We quote this not to score a point. We quote it because it is honest, and because it is the right benchmark. A large company with a mature native app still lists the features that need signal. A custom web app will have a longer list in version one, and anyone who tells you otherwise has not built one for a basement.

The screens a technician touches on every job

Version one is the part of the day that happens on every job, for every tech. Everything else waits until the core has survived a month of real use. The table below is the scope we usually start from.

Warm shallow-focus photo of a phone in a dash mount inside a work van, blank screen, work gloves and a tape measure on the seat, a hand reaching in
Version one of a technician app is the handful of screens used on every job, built for one-handed use in a van.
Technician web app, version one: the screens, what each does, and how it behaves with weak signal
ScreenWhat it doesWith weak or no signal
TodayThe day's jobs in order, with window, address, customer phone and one-tap directionsLoaded at the start of the day and kept on the phone
JobProblem description, notes from the office, equipment on file, last three visitsReadable from the morning copy
StatusEn route, on site, done, needs a return visit; shown on the dispatch boardSaved on the phone and sent when signal returns
Photos and notesCamera, captions, notes typed or dictatedSaved on the phone; uploaded later, smallest first
Options and signatureShows estimate options from the pricebook module and takes a signatureSignature saved locally; options need the morning copy
PaymentTexts a payment link or takes a card in person through the processorNeeds a connection; the job can close as unpaid and the link goes later

Left out of version one, on purpose

A short first version is not a cheap first version. It is a version technicians will actually use, which is the only kind that pays back. Each item below is real work in a real shop. Each one can be added later, once the core screens have been through a summer.

  • Truck inventory and stock counts. Valuable, fiddly, and useless until the counts are trusted. Keep the current method for now.
  • Purchase orders. An office task that rarely needs to happen in an attic.
  • Timesheets and payroll. Payroll is one of the heavy lifts on its own; until it moves, clock-ins stay where they are.
  • Financing applications. If you offer financing, the estimate links to the lender's own application instead.
  • Forms builders and checklists by job type. Start with one inspection checklist on paper or a fixed screen, then build the editor.
  • Full offline editing of invoices and estimates. Version one reads offline and saves statuses, photos, notes and signatures offline; editing prices waits for signal.
  • Equipment scanning and AI features. Pleasant, and nobody's first problem.

Why this module is the heavy lift on the menu

A dashboard reads data in an office with good internet. A technician app writes data from places with no internet, on phones you do not control, and has to agree with the office afterward. A tech marks a job done in a basement while the dispatcher reassigns it upstairs. Two photos of the same drain pan upload in the wrong order. The phone runs out of storage halfway through a video. Every one of those needs a rule, and the rules have to be tested in the field, not at a desk.

Every field app works perfectly in the parking lot. The basement is the test.

It also depends on the modules around it. Jobs come from the dispatch board, options from the pricebook, payments through the invoicing and payments module. If those are still in ServiceTitan, the technician app has to read and write there too, within the API rules ServiceTitan's Developer Portal sets, including the package requirement for customer-built apps. That is possible, and the API connection goes live the same day, but it is why we usually build this module late in a phased replacement, once its neighbors are in your own app.

We build the technician app as a web app. The tech opens a link, adds it to the home screen, and it behaves like an app. There is no store review, no waiting for a release to be approved, and every phone gets the update the moment it is published. Lost phones are handled by signing the user out from the office.

A web app suits you if

  • Your techs use their own phones or a mix of iPhones and Android phones
  • You want changes live the same afternoon, not after a store review
  • Your core needs are jobs, photos, notes, signatures and payment links

Think about a native app if

  • Your crews work for days in places with no signal at all
  • You need heavy background work, such as continuous location tracking
  • You depend on hardware add-ons that only a native app can drive

The trade-offs are laid out in more detail in our comparison of native iPhone apps and web apps. For most service companies starting their own app, the web version is where to begin, and it can be wrapped or rebuilt later if the business outgrows it.

Two techs first, then the fleet, then the bill

  1. 1

    Ride along before drawing anything

    We watch a real day, or you film one. The screens come from what technicians do, not from a feature list.

  2. 2

    Pilot with two technicians

    One who likes new tools and one who does not. The skeptic's complaints are worth more than the enthusiast's praise.

  3. 3

    Run beside the current app

    For a few weeks, the pilot techs use the new app while the office checks every job against the old system.

  4. 4

    Roll out to the crew

    A short session, a one-page card in every truck, and a phone number that gets answered.

The technician web app module is from $575 to build, depending on complexity, as of November 2026, and it is one of the heavy modules that land well above that floor. The fixed written estimate sets the price and the schedule before work starts. Hosting and maintenance are from $55 a month on our hosting and maintenance plan. Texts to customers, sent through the SMS module, bill at carrier cost, and payments carry the processor's own fees, paid to the processor.

ServiceTitan does not publish its prices, and owners with five or more technician licenses tell us their bill runs $2,500 a month or more. A technician app you own adds no license when you hire. Put your own numbers in the savings calculator, read what ServiceTitan includes if you are weighing what you would give up, and see the section hub for the whole case. Our web app development page describes how we build. Call (210) 346-0848; we are in San Antonio and have built for the web since 1999.

Questions owners ask about replacing ServiceTitan

Partly, and we say exactly which parts. Our version one keeps the day's jobs on the phone, and saves status changes, photos, notes and signatures offline to send when signal returns. Payments and price edits need a connection. Even ServiceTitan's help center, in an October 29, 2026 article, lists features of its native app that require one.

No. A web app opens from a link and can be added to the home screen, where it looks and behaves like an app. Updates reach every phone when we publish them, with no store review. If a phone is lost, the office signs that user out.

Yes, through a processor. The tech can text a payment link to the customer, or take a card in person through the processor's own reader. Stripe's US pricing page, read November 10, 2026, lists, as of November 2026, 2.7% + 5¢ for in-person domestic cards through Stripe Terminal. Payments need a connection; the job can close as unpaid and the link goes out later.

Truck inventory, purchase orders, timesheets and payroll, financing applications, a forms builder, offline editing of prices, and equipment scanning or AI features. The first version covers the screens used on every job: today's list, job details and history, status, photos and notes, options and signature, and payment. The rest is added once technicians trust the core.

Mostly. ServiceTitan's help center, in an article published October 29, 2026, says most core workflows work offline and sync later, but that purchase orders, customer financing, contracts and inventory availability need a connection, and that payments captured offline are not finalized until the device reconnects. Its product page states the offline claim more broadly; the help article is the more detailed source.

From $575 to build, depending on complexity, as of November 2026, and the technician app is one of the heavy modules that land well above that floor. You get a fixed written estimate, which sets price and schedule, before work starts. Hosting and maintenance are from $55 a month.

Keep reading

Free · No obligation

Get a first-version scope for your techs

Tell us how many technicians you run, what phones they carry and what they do on a typical job. A person at DataCram replies with what version one would include, what it would leave out, and a written estimate if you want one.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote