An app is justified when there is repeated use
Work away from the desk, notifications, running without a connection. When none of that applies, a site that sits well on a phone solves it better and costs less — and we say so before quoting.
Systems and operations
What is included
- An app for iOS and Android from a shared codebase
- Installable web apps when the store is not worth it
- Fieldwork with syncing afterwards
- Publishing and follow-up in the app stores
- Connection to the system the company already uses
Who it makes sense for
When it makes sense — and when it does not
The right question is not "do we want an app?", it is "what does only an app solve?".
Teams working in the field, often with no connection
Services with repeated use, where the app saves steps every day
Operations that need notifications to happen on time
Not sure? The diagnosis answers in under a minute.
Frequently asked questions
What people ask us about apps
Often not. If use is occasional and there is no offline work or notifications, a fast site on the phone delivers the same for a fraction of the cost, and with no app stores in the way. We would rather say that in the first meeting than discover it halfway through the project.
We work from a shared codebase that produces the iOS and Android versions. It saves time and keeps the two identical; when a feature really does require native code, that part is built separately.
We do, with the accounts in the client's name. Submitting to the App Store and Google Play has rules of its own and rejections are normal on the first round — it is part of the job and it is accounted for in the timeline.
Not sure whether you need an app?
Three questions and we tell you whether it is worth it — including when the answer is no.