Mobile applications

Some work does not happen in front of a monitor: the person delivering, installing, serving a room, counting stock. If your operation lives there, the system has to go with that person.

Free review

When you need this

Someone writes on paper and enters it into the system back at the office.
Your field team phones in to ask something they could look up themselves.
You need photos, signatures or the location where the work was done.
Your customers write to you from a phone but you make them use a desktop.

What it includes

iOS and Android, native or cross-platform depending on what the case asks for.
Working offline and syncing when the signal comes back.
Camera, location, notifications and signature, where they earn their place.
Store submission and the updates that come after it.

How we do it

The choice between native and cross-platform is not ideological: it comes out of the audit, looking at what the app needs from the phone and how many people will maintain it afterwards. It gets decided before building and goes in writing with the rest of the scope.

Five phases, each with its own acceptance criteria

Questions about this service

Native or cross-platform?

It depends on what you ask of the phone. If the app lives off the camera, the sensors or raw performance, native. If it is mostly screens and data, cross-platform is cheaper to maintain with a small team.

Does it work without a signal?

It gets built for that when it matters: the app stores locally and syncs when coverage returns. That is the normal case for field operations.

Usually comes with

Custom software