Mobile app development for iOS and Android

iOS and Android. Native when performance decides it — cross-platform when that gets you there sooner.

When an app is worth building

An app earns its place when people work standing up. In field service, in the warehouse, on a building site, at a customer. There a phone is the one device already in hand — and camera, location, barcode scanning and offline operation are exactly what the work needs.

Not every idea needs an app. If your users sit at a desk, a web app is almost always cheaper and available sooner. We tell you which way we lean in the first conversation, even when that argues against the bigger project.

What companies use apps for

Field service

Capture jobs, checklists and reports on site, instead of typing up paper in the evening.

Warehouse and picking

Scan barcodes with the phone camera and post stock immediately, without separate handheld scanners.

Time and activity tracking

Record hours and tasks where they happen — with location where it has to be evidenced.

Customer apps

Orders, status and documents for your customers, when a browser portal is not enough.

Build it yourself?

App builders: fine for a test, thin in production

An app builder puts something on a phone within days. For an internal test, or to show a board an idea, that is a perfectly sensible route — and cheaper than commissioning us for it.

It rarely reaches production. What matters there is the unglamorous part: the app has to keep working in a dead spot and reconcile cleanly afterwards. It has to clear Apple and Google review. It has to still run against a new iOS version in two years, and for that somebody needs the source.

Offline and reconciliation: Local data and defined rules for when two devices change the same record.
Store approval: Apple and Google policy is the most common reason an app never ships.
Your developer account: The app belongs to you, not to a platform that can change its pricing.

How we build apps

01
Native or cross-platform
We decide on your requirement, not on preference. For most business applications a shared codebase across both platforms is enough.
02
Offline from the start
Warehouses and building sites have dead spots. The app stores locally and syncs later — otherwise it is useless in the field.
03
Store release
We handle submission and approval with Apple and Google, or distribute internally through your device management.

Common questions

Native or cross-platform — which is better?

For business applications a shared codebase is usually the better call: same features, half the cost, one thing to maintain. Native becomes interesting when you lean heavily on camera, graphics or background processing.

Who publishes the app to the App Store?

We do — ideally under your own developer account, so the app belongs to you and you stay independent of us.

Does the app work without internet?

Yes, where your work requires it. Data is held on the device and reconciled at the next connection. We plan for that from the start rather than bolting it on.

Do we actually need an app?

Often not. If your users mostly work at a computer, we will recommend a web app. We say so in the first conversation, even when it is the smaller project.