Mobile Applications
We build mobile applications only where a mobile website cannot serve the need, and we tell you when it can.
What we usually find
Most court services are better delivered on the web than in an app store, and an app nobody maintains is worse than no app. Sometimes, though, the work is genuinely mobile: field staff, offline conditions, secure device requirements.
The first question we ask is whether something your agency already owns can be made to do this. Where the answer is yes, that is the recommendation, and it is a smaller and cheaper engagement than the one described below.
What follows is what the work looks like when the answer is no: the reference scope for a typical engagement, the variables that move what it costs, and what your agency holds at the end of it. Scoping is done by the engineers who will do the build, which is usually why the scope comes back smaller than an agency expects.
What a typical engagement includes
- An honest recommendation first, including that you may not need an app
- Native builds or a shared codebase, chosen for what your team can maintain
- Offline behavior where the work happens away from a desk
- Accessibility on both platforms, tested with screen readers
- Store submission, signing, and release process handed to your team
This is a reference scope, written in full before the work starts and adjusted to your agency during scoping. Anything included is written down, and anything left out is written down too.
What moves the price
Two agencies buying the same offering will pay differently, and these are the reasons why. We publish them because they are the questions we would ask in the first scoping session, and you can work out most of your own answers before that session happens.
- iOS, Android, or both
- Whether offline and synchronization are required
- Device management and security requirements
What happens when scope changes
Scope changes on nearly every project. We manage changes through a documented approval process, so your agency sees the cost of a change before any work happens.
- The change is documented
- Anything outside the written scope is raised as a change request, in writing, as soon as we identify it.
- The change is priced
- You receive the cost and the schedule impact in writing before any work on the change starts.
- Your agency decides
- You can approve, defer, or decline the change. Declining does not affect the rest of the engagement.
- No work proceeds without approval
- No change is built or billed without your written approval.
What your agency owns at the end
The source code is yours, in your own repository from the first commit. Host it yourself, keep us on support, or move it later: all three options are priced in advance.
How Custom Digital Solutions runs, phase by phaseWhat it costs, and how it is bought
This offering is bought through the Build engagement, against a scope written and agreed before any work starts. We publish a price only once it is a commitment, so the band for this engagement is not on the page yet. Everything else about it is.
Builds usually depend on services such as hosting, email, messaging, identity, or payments. Your existing services are the starting point.
See engagements and pricingMobile Applications
- Price
- From $60,000
- Timeline
- 12 to 20 weeks
- Bought through
- Build
What we need from your team
- A decision maker who can approve scope in one meeting
- Access to the systems it must integrate with
- Staff time for research and review, about 3 hours every two weeks
The safe first step
The readiness assessment is free, takes about 20 minutes, and returns a scored report you keep. It creates no obligation, no call, and no follow-up.