An internal system and a mobile app.
No app stores.

Who this is for

Companies whose people work in the field — technicians, drivers, installers, delivery crews — coordinated by dispatchers in the office. That usually means three separate systems: a web app for the office, a mobile app for the field, and some database tying them together. Three systems, three bills, three places to break.

The problem with native mobile apps

If you have had a native app (Android/iOS), you know the cost:

• Every change requires a mobile developer — a separate specialist, a separate budget.
• Publishing through the App Store and Google Play: fees, reviews, days of waiting.
• Two separate codebases if you want both iPhone and Android.
• Users run old versions because they never updated the app.

The answer: an app that lives in the browser

We build the mobile side as a PWA — an app installed on the phone from the browser, with an icon on the home screen like any other, but without an app store.

It has everything you expect from a native app:

• Push notifications on new tasks — working on both Android and iPhone.
• Offline mode — tasks can be viewed and completed without coverage (a basement site, out of range), syncing automatically once the connection returns.
• Camera — photos attached to reports straight from the app.
• GPS — coordinates on every action, if your process needs them.
• Access to your full data catalog, even without internet.

Plus three advantages native apps don't have:

1. Instant updates — the new version reaches every phone immediately, with no store and nothing for the user to do.
2. One team, one codebase — maintenance doesn't require a mobile specialist.
3. No fees to Apple and Google, and no approval rules.

How it works

First we describe your process as it actually is — who does what, in what order, what goes wrong. Then we build the system around it, not the other way round.

If we're replacing an existing system, the rule is: the first release is indistinguishable for your users. No "improvements" that confuse people used to the old ways. New capabilities switch on after the transition is done.

A real example

A company with offices in two countries ran three systems — web for dispatchers, a native Android app for the field, and a cloud database with growing fees. iPhones weren't supported at all.

We replaced all of it with one system: 12 working days for the full replacement, including migrating over 38,000 records and the complete archive. The mobile side is a PWA with push, offline and camera, verified on real iPhone and Android hardware. Maintenance no longer requires a mobile specialist.