iOS and Android

Mobile app development.

We build iOS and Android apps for customers and for teams on site. A customer might need to pick up a booking where they left off. A technician might need to photograph a fault and save the job before reception drops out.

Inside a field app
AInterface
The screens someone uses to find a job, record what happened and check they have finished.
BApp logic
The rules for a job, including which details are required and when it can be marked complete.
CDevice features
The camera, location or notifications, with permission requested at the point of use.
DRecords & sync
A local copy keeps work available on site. A service reconciles changes with the office system when the connection returns.

When the work leaves the desk

A phone app is worth considering when people carry it through the job, use device features regularly or need to keep working offline. If customers only need an occasional form, opening a web link may be easier than installing an app.

See mobile app pricing

What the work involves

A walk-through of the job

Take us through one shift or visit. We map who starts the record, what the person on site must capture and what the office needs at the other end.

A prototype on the target phone

We put the main task on screen early. Trying it one-handed on the device people actually carry tells us more than another round of desktop mock-ups.

A build and release handover

The scope can include tested iOS and Android builds, the service connection, a release checklist and notes on store accounts, permissions and ongoing updates.

Where to start

Tell us who carries the phone, which devices they use and where the connection is unreliable. A blank copy of the form or a sketch of one job is a useful start.

Discuss a mobile app