Field service management apps
Field service app development for technicians, dispatchers and work orders
We take on field service app development for HVAC, elevator, fire safety, solar, telecom, utilities, medical equipment and industrial machinery service teams. We build the technician app, the dispatch and planning console, the customer portal and the integrations with your ERP, CRM and asset records.
The defining requirement is offline. Technicians work in basements, plant rooms, rooftops and rural sites with no signal, and a job sheet that won’t save is a job that gets written on paper. We design the data model for offline first and treat sync as the core feature, not an afterthought.
- Technician app that works with no signal
- Work orders, assets, parts and signatures
- ERP and CRM integration planned up front
- You own code, data and store accounts
Who this is for
Custom builds usually suit service companies or equipment manufacturers with tens to hundreds of technicians, and processes that generic tools handle badly: regulated inspection checklists, complex assets with service history, warranty and contract rules, or an ERP that has to stay the system of record.
A smaller team with standard jobs should start with an off-the-shelf field service management product. Custom software makes sense when per-user licences get expensive at scale, when your checklists and compliance reports are a competitive edge, or when you want the app inside your own customer experience. Sometimes the best answer is a custom technician app on top of an existing back office.
This page goes one level down from our manufacturing app development page, which covers the sector. For staff-facing tools beyond field work, see internal employee app development. Consumer-facing booking for trades is closer to home services app development.
Decide before design
- Which system is the record: ERP, CRM or the new app
- Company phones, BYOD or rugged devices
- Which data must be available offline
- Inspection checklists and report formats
- Contractors as well as employees?
The apps in a field service product
Technician app
Today’s jobs, route, site and asset details, service history, checklists, photos, parts used, time on site, customer signature and a service report generated on the spot. Works fully offline.
Dispatch and planning console
Job board, drag-and-drop scheduling, skills and certifications, SLA timers, preventive maintenance plans and live job status. Built by our admin panel and dashboard development team.
Customer portal
Raise a service request, see asset history and upcoming visits, approve quotes and download reports and certificates. Often a web portal first, with an app later.
Core features by app
| Area | Technician app | Dispatch, back office and portal |
|---|---|---|
| Work orders | Job details, priority, SLA, notes, status changes offline | Create, assign, split and close jobs; SLA tracking |
| Scheduling | Day and week view, accept or reject, travel start and arrival | Skills matching, territories, drag-and-drop planner, emergency slots |
| Assets | Scan a barcode or QR tag, see history, readings and manuals | Asset register, contracts, warranties, preventive maintenance plans |
| Checklists | Dynamic forms, mandatory photos, readings with limits, pass or fail | Form builder with versioning, compliance templates |
| Parts | Van stock, parts used, request parts, returns | Stock levels, reorder points, cost to job |
| Time and cost | Labour time, travel time, expenses | Timesheets, job costing, invoices to ERP |
| Sign-off | Customer signature, service report PDF, email on completion | Report archive, customer portal downloads |
| Safety | Lone-worker check-in, permits and risk assessments before work | Incident reports, certification expiry alerts |
Offline-first: how the technician app keeps working
An offline-first app reads and writes to a database on the device, and syncs with the server when it can. The technician never waits for the network. We use Room over SQLite on Android, SQLite or SwiftData on iOS, or a shared SQLite layer in cross-platform builds, and keep every change as a queued operation with a timestamp and author.
The hard decisions are about scope and conflicts. Scope means deciding what each technician downloads: their jobs for the next few days, the related assets and history, the forms they need and the manuals they might open, without filling the phone. Conflicts happen when the office edits a job the technician has also changed offline. We set rules per field (office wins on scheduling, technician wins on readings and notes, append-only for photos and comments) and flag the rest for a dispatcher to resolve.
Photos and signed reports are the heaviest data. They upload in the background, resume after interruptions and are never deleted from the device until the server confirms receipt. We test all of this in airplane mode, on weak signal and across app restarts, because sync bugs only show up in the field. MongoDB deprecated Atlas Device Sync in September 2024 and ended it on 30 September 2025, so we don’t build on it.
Advanced features that drive cost
- Route and schedule optimisation. Automatic planning by skills, SLA, location and parts availability. It needs clean data first.
- Preventive maintenance. Plans by time, usage or meter readings that generate jobs automatically, tied to contracts and warranties.
- Configurable form builder. Letting your team build and version inspection checklists without a developer. It costs more up front and saves every later change.
- ERP integration. Two-way sync of customers, assets, parts, timesheets and invoices with SAP, Microsoft Dynamics, Oracle or a bespoke system. Our enterprise app integration service covers the patterns.
- Connected equipment. Reading fault codes or sensor data over Bluetooth from the machine being serviced. See our Bluetooth BLE app development page.
- Remote expert video. A live video call from site to a senior engineer, with annotation, which adds a media service and bandwidth fallbacks.
The cost most often missed is data cleanup. Asset registers, customer sites and parts lists in older systems are usually incomplete or duplicated, and the app exposes that on day one. We plan a data migration and cleanup task in discovery.
See a typical effort range for your field service app
Pick platforms, screens, features and backend in our calculator and get a planning range in hours and weeks at the default $25–$49 per hour market band. After discovery we turn it into a fixed price.
Recommended stack for field service app development
For most field service app development a cross-platform build works well, because the technician app is mostly forms, lists, camera and sync. Flutter app development is our usual default with a local SQLite database and a sync engine we control; our guide to offline-first mobile app architecture explains the design. Native Android app development is worth it when you standardise on rugged Android devices with built-in scanners, or need deep background and Bluetooth behaviour.
On the server, PostgreSQL holds work orders, assets and audit history. An API in Node.js or Laravel exposes a sync endpoint that accepts batches of changes and returns what has changed since the device’s last sync. An integration layer with queues and retries talks to your ERP, so a slow ERP never blocks a technician. Our mobile app backend development service covers this architecture in more depth.
Integrations: ERP, maps, devices and identity
ERP and CRM
Customers, sites, assets, parts, price lists and invoices from the system of record, with clear rules on which side owns each field.
Maps and location
Site locations, routing handoff to the phone’s navigation app and arrival detection. See Google Maps and location services.
Device management and identity
Company devices managed through an MDM, single sign-on with your corporate identity provider and remote wipe for lost phones. More on our authentication and SSO page.
Scanners and printers
Camera-based barcode and QR scanning, built-in scanners on rugged devices, and mobile printers for on-site receipts or labels.
Compliance, data and store-distribution notes
General information, not legal advice. These points shape field service apps most often.
Distribution. Internal apps for your own staff don’t need a public store listing. Options include private distribution through your MDM, Apple Business Manager custom apps and managed Google Play. Customer-facing portal apps go through normal store review.
Technician location. Tracking employees’ location is personal data under GDPR and UK GDPR. Track during working hours or active jobs only, say so clearly in the app, and keep the data no longer than the purpose needs. On Android 12 and later, Bluetooth scanning needs runtime permission, and location is required only if scan results are used to derive location.
Inspection records. Safety and regulatory inspections often need tamper-evident records: who did what, when, with which readings and photos. We keep an append-only audit log and versioned forms, so a report always shows the checklist version it was completed against. Which standards apply to your sector is for your compliance team to confirm.
Security. Field devices get lost. Data on the device is encrypted, sessions expire, and admins can revoke a device. We test against OWASP MASVS controls for storage, authentication and network.
Built in by default
- Offline database with queued sync
- Per-field conflict rules
- Append-only audit log on jobs
- Encrypted on-device data and remote revoke
- Location tracked only during work
Typical effort estimate (hours) by version
Typical effort estimates (hours) for design, technician app (cross-platform), offline sync engine, backend, dispatch console, QA and project management. Fixed prices follow discovery.
| Version | Typical scope | Typical effort estimate (hours) | At the $25–$49/hr market band |
|---|---|---|---|
| MVP (one workflow) | Offline technician app with jobs, assets, fixed checklists, photos, signature and PDF report; sync engine; dispatch board; one-way import from your ERP or spreadsheets | 1,300 to 1,900 | $32,500 to $93,100 |
| v1 (operations) | Two-way ERP integration, parts and van stock, preventive maintenance plans, configurable forms, SSO and MDM, customer portal, timesheets | 2,200 to 3,300 | $55,000 to $161,700 |
| Scale (enterprise) | Schedule optimisation, multi-country and contractor access, connected-equipment readings, remote expert video, analytics and SLA reporting | 3,600 to 5,500+ | $90,000 to $269,500+ |
Dollar figures multiply the hours by the $25–$49/hr band most firms list on the Clutch Pakistan app developer directory. That is market data for illustration, not our pricing. ERP connector licences, MDM and hosting are running costs on top. The app development cost pillar explains how hours become a budget.
How a field service app pays back
Most field service apps are internal tools, so the return is operational rather than app revenue.
More jobs per technician
Less paperwork, less travel back to the office and fewer repeat visits because the right history and parts were known in advance.
Faster invoicing
Signed reports and parts used flow straight to billing, instead of waiting for paper job sheets.
Fewer licence fees
At scale, owning the software can replace per-user subscriptions. Run the numbers honestly, including maintenance.
Service contracts as a product
For equipment makers, a customer portal and preventive maintenance plans support paid service contracts.
How we build your field service app
NDA and discovery (1–2 weeks)
Workshops with dispatch, technicians and finance, plus a ride-along where possible. Output: job lifecycle, offline scope, conflict rules, integration map, clickable prototype and a fixed price.
Sync engine and data model first
We build the offline database, sync endpoint and conflict rules before the screens, and test them with generated jobs on real devices in airplane mode.
Two-week sprints with demo builds
TestFlight and Play internal testing builds every sprint, with release notes. A small group of your technicians uses them on real jobs from early on.
Integration and data migration
ERP connection through a queue, asset and customer data cleanup, then a parallel run against your current process, tested by our mobile app testing services team.
Rollout by region
Private distribution or store release from your accounts, training material, a pilot team, then region-by-region rollout with monitoring through Crashlytics or Sentry.
Field service app development FAQs
Does the technician app really work with no signal?
Yes, that is the design. Jobs, assets, history, forms and manuals the technician needs are downloaded in advance and stored in an on-device database. Everything they do offline, including photos and signatures, is saved locally and queued. When a connection returns, changes sync in the background and resume if interrupted. We test in airplane mode and on weak signal throughout the build.
What happens if the office and technician edit the same job?
We agree conflict rules in discovery and build them per field. Typically the office wins on scheduling and assignment, the technician wins on readings, notes and parts used, and photos and comments are append-only so nothing is lost. Anything that doesn’t fit a rule is flagged for a dispatcher to resolve, with both versions visible.
Can it integrate with our ERP?
Usually, yes. We connect to SAP, Microsoft Dynamics, Oracle and bespoke systems through their APIs or an integration platform, with a queue in between so a slow or offline ERP never blocks technicians. We agree which system owns each field, such as customers, assets, parts and invoices, before any code is written, because that decision drives most of the integration effort.
Should we build custom or buy a field service product?
Buy if your jobs are standard and your team is small; established products are faster to roll out. Build when per-user licences get expensive at scale, when your checklists and reports set you apart, or when integration with your systems is the hard part. A middle path is a custom technician app on top of an existing back office.
Do internal field apps need to go through the App Store?
Not necessarily. Apps only for your own staff can be distributed privately through your device management system, Apple Business Manager custom apps or managed Google Play. That avoids a public listing and gives you control over which devices get the app. Customer-facing apps still go through normal App Store and Google Play review.
How long does a field service app MVP take?
After one to two weeks of discovery, an MVP with an offline technician app, sync engine, dispatch board and a one-way data import usually takes 8–16 weeks. Two-way ERP integration and configurable forms push it toward the longer end. Your technicians get working builds every two weeks and should use them on real jobs early.
Get job sheets off paper and into the system
Tell us your service types, team size and the systems you run today. We reply within one business day with questions, a typical effort range and the next step toward a fixed price.