Mobile apps people keep on their phone

iOS and Android applications, native or cross-platform, taken from idea through store approval to the updates that come after.

Worth building only if it belongs on a phone

Most apps are deleted within a week. The ones that survive do one thing that is genuinely easier on a phone than anywhere else — and do it without asking for an account before showing any value.

We help decide whether you need an app at all: often a fast mobile website does the job for a fraction of the cost and none of the store approvals. When an app is right, we build it to feel native on both platforms and to be releasable without drama.

Who this is for

If one of these sounds like your situation, it is worth a conversation.

A product that belongs in a pocket

Location, camera, notifications or offline use — things a browser does badly.

A field team on paper

Site visits, deliveries or inspections recorded on forms and typed up later.

An app that stalled

Half-built, or built and abandoned by the last supplier. We do take these on.

How we work

Engineering practice, stated plainly, so you can hold us to it.

You own the code

Your repository, your infrastructure, from the first commit. No hostage-taking, no licence to renegotiate.

Working software every fortnight

Something you can open and use, not a progress report. If a sprint produced nothing you can click, we say so.

Tests where they earn their keep

On the logic that would be expensive to get wrong. We do not chase a coverage number for its own sake.

Handover assumed from day one

Written so your team, or the next agency, can pick it up. That is a feature, not a risk to us.

Part of Technology

Part of Technology

Software that carries the business

Custom software, web and mobile applications, cloud platforms and the integrations that hold them together — built to be maintained, not just launched.

See all Technology services
What we commit to

What we commit to

  • A fixed price for a fixed scope, or a rate — never both at once
  • One named engineer who knows your system, not a rotating pool
  • Weekly written updates, including the weeks that went badly
  • Your data exportable in a documented format, always
  • No lock-in: no proprietary framework you can only maintain through us
How a build runs

How a build runs

Four stages. You can stop after any of them and still have something worth having.

Discovery

We map the process as it really is, agree what the software must do, and write down what it will not. You get the plan whether or not you build with us.

Design and architecture

Screens, data model, and the technical decisions that are expensive to reverse later. Reviewed with you before anyone writes code.

Build

Two-week cycles, each ending in something you can use on a staging environment. Priorities can change between cycles; scope inside one cannot.

Launch and support

Deployment, monitoring, and a support arrangement sized to what you actually need — which is usually less than you were quoted elsewhere.

Common questions

Often a fast mobile website does the job for a fraction of the cost and none of the store approvals. An app earns its place when you need the camera, location, notifications or offline use — we will tell you which you are.

Cross-platform for most business apps: one codebase, both stores, and the difference is no longer visible to users. Native where you are pushing the hardware. It is argued from your requirements, not our preference.

We handle submission and the review responses, including the first rejection, which is common and rarely serious. Budget a week for it on the first release.

Is this the right fit?

Tell us what you are trying to do. If app development is not the answer, we will say so.

Get in touch
Contact us