Field service applications
Job dispatch, checklists, parts, time capture and sign-off for technicians and crews.
07 / Software beyond the desk
Built for the field, not the boardroom.
A mobile application earns its place when the work happens away from a desk. Deliveries, inspections, site visits, service calls. The engineering problems that matter are unglamorous — intermittent connectivity, battery cost, and an interface that works one-handed in bad light.
The problem
What field software has to survive
Conditions a desktop application never encounters.
Reality on the ground
- Coverage that disappears between locations
- Data costs that make constant syncing unreasonable
- A device at eleven percent battery halfway through a shift
- Paper forms captured into a system hours or days later
- No way to know where a job or a vehicle currently is
- Proof of delivery that is a signature on a page nobody can find
Built for it
- Offline-first: work continues without signal and syncs when it returns
- Efficient sync that batches and compresses rather than chattering
- Location tracked at a sensible interval instead of continuously
- Capture at the point of work, visible in the back office immediately
- Live job and vehicle status for dispatch and for the customer
- Timestamped, geotagged photographic and signature evidence
Services
What we build
Logistics & delivery
Route, tracking, status updates and proof of delivery across dispatch, driver and customer.
Inspection & compliance
Structured capture with photographs, geotagging and timestamps that stand up as records.
Customer applications
Account, ordering, booking, tracking and support in your customers' hands.
Internal workforce tools
Attendance, requests, approvals and communication for staff who are not at a computer.
Back-office integration
Mobile capture connected to the systems that already run the business, not a separate island of data.
Process
Field observation
We watch the work being done. Field applications fail when they are designed from an office assumption about how the job runs.
Platform decision
Cross-platform, native or a well-built responsive web application — chosen on the requirements, not on preference. Sometimes an app is not the right answer.
Offline & sync design
What is stored locally, how conflicts resolve, and what happens when two people edit the same record. Designed before the interface.
Build & device testing
Tested on real devices in real conditions, including the older hardware your team actually carries.
Store release
App Store and Play Store submission, review handling, and a release process you can repeat.
Operate
Crash monitoring, OS-version compatibility, and iteration based on how it performs in the field.
Mobile Applications
Questions we are actually asked
A well-built responsive web application handles a surprising amount, costs less, and needs no store approval. You need a native app when you require reliable offline operation, background location, push notifications, camera-intensive capture or hardware integration. We will tell you honestly which case you are in.
Works with
Software & Systems
Business systems built around how your organisation actually works — replacing spreadsheets, email chains and disconnected tools with one connected platform.
Explore Software & Systems ExploreWeb & Digital Experiences
Digital experience engineering — websites and web platforms built as products, engineered for performance, accessibility and search, not assembled from a template.
Explore Web & Digital Experiences ExploreAI & Automation
Applied AI that removes repetitive work, makes operational information findable, and puts intelligence inside the systems your teams already use.
Explore AI & Automation Explore
Tell us what is not working.
A short conversation is usually enough to tell whether this is the right capability for your situation — and we will say so if it is not.