Mobile app development for the people out of the office
Today's jobs, checklists, photos and a signature on the phone in their pocket, installed from the browser on iPhone and Android, from the same build as the desk.
Trusted by clients from global brands to local charities
Progressive web apps
An app, without the app store
A progressive web app runs in the browser and installs to the home screen straight from it. It opens full screen like any app, uses the camera, and works on iPhone and Android alike, from one codebase.
Installs from the browser
Send a link and it's on the phone. No store and no review queue.
Camera, photos and signatures
Photos attached to the job, a signature drawn on the screen.
Designed for a thumb
Screens laid out for one hand, on site or on the move.
Why not an App Store app?
We build web apps that install on a phone, not App Store apps, by choice. Here's why.
One build
One codebase serves the desk and the phone, so there's one set of data and one thing to look after.
Every release reaches everyone
A new version reaches every phone the moment we release it. No store review, no waiting for people to update.
No store, no gatekeeper
Nothing to list and no developer account to keep. Store rule changes don't touch you.
One team, one bill
No separate mobile team or second codebase, and one set of hosting to pay for.
What clients say about working with us
Questions about mobile apps
Yes, from the same build. It installs from Safari or Chrome and opens like any other app on the phone.
Yes. Photos, documents and signatures go straight into the record, so the office sees them the moment they're taken.
The same way as the desk: staff sign in with their work account, and the rules about who sees what live in the database, so they hold on the phone too.
You'll click through a prototype before the build starts, and the first release is usually in use within weeks, because it covers the part of the job that matters most. After that it grows month by month.
That depends on the job and is designed in from the start: what the app must still do with no signal, and how it catches up when the connection returns. We agree it in the workshop, before the build.
When the point is a listing in the App Store for the public to find and download, or when the app has to talk to hardware a browser can't reach, such as some specialist Bluetooth devices. If your system runs on FileMaker, FileMaker Go is its phone app, and our FileMaker team looks after that.
If we built it, the phone screens join the same system and the same data. If someone else built it, we start with an audit, then add the phone to it or plan a move.



