App development services for web and mobile.

Web and mobile applications built from the scope up — user journeys, interface, development and release, with the thinking written down before code starts.

Get a fixed quote All services

5+Years buildingSince 2021
100+Projects deliveredLaunched and still running
6+Countries servedRemote-first delivery
100%Client satisfactionWould work with us again

About this service

What is app development?

App development is building software people install or open in a browser to do one job well. The hard part is rarely the code. It is working out what the app should do before building all the things it could do.

Built around one job
We start from the process someone carries out by hand today, and remove it. If an app would not delete a real annoyance, we say so before we build anything.
Scoped before it is built
Journeys, screens and data are written down first. That costs two weeks up front and saves months afterwards, when the scope would otherwise still be moving.

Most failed applications are not badly built. They solve a problem nobody had, or they make a simple job feel like work. So we spend the first part of the project removing things rather than adding them.

We build web applications and mobile applications. A web application runs in a browser and is usually the right first choice: nothing to install, one codebase, and it works on every device. A native or cross-platform mobile app is worth the extra cost when people need it offline, or when camera, Bluetooth or background location are genuinely part of the job.

Turn a useful idea into a usable product.

Scope

What you get with app development.

A written product scope

Every screen, what it does, and what it deliberately does not do. This is the document that stops the project growing quietly.

User journeys and prototypes

Clickable versions of the main flows, tested on real people before they are built. Changing a prototype costs a morning; changing working software costs a week.

Interface design

Every screen, every state — including the empty, loading and error states, which are where most apps feel unfinished.

The working application

Reviewed regularly on a live link. You are never waiting weeks to find out where the project is.

Accounts and data

Sign-up, sign-in, roles and permissions designed in from the start rather than bolted on afterwards.

Release and store submission

Submission to the app stores, including the privacy declarations they require. This is where a lot of first releases stall.

Cost

How much does an app cost to build?

Applications are quoted per project, and the range is wide because the difference between a simple internal tool and a customer-facing product is the difference between weeks and months. What moves the price:

Get a fixed quote

How many distinct screens: Screens are the closest thing to a unit of work. The count, and how different they are from each other, drives most of the estimate.
Number of user types: One kind of user is straightforward. Staff, customers and administrators each needing to see different things roughly doubles the permission and interface work.
Does it need its own data: Anything worth remembering needs a database, and everything touching the database needs building and securing.
Integrations: Talking to payment providers, accounting software, maps or another API adds work and risk in roughly that order.
Which platforms: One web app, or one cross-platform mobile app, is one codebase. Native iOS and native Android separately is two.

For applications we work in stages — a first version with the core journey, then the rest — rather than one build of everything. You get something real sooner, the first part proves the idea, and no single payment has to carry the whole risk.

Process

How we build an app.

01
The problem, in plain words
Who is using this, what are they trying to do, and what do they do instead right now. No screens discussed yet.
02
Scope and journeys
The flows, written down. This usually cuts the original idea in half, which is a good sign: it means the important part is clear.
03
Prototypes on real people
Clickable and tested. If the journey confuses people before it has been built, changing it is nearly free.
04
Build in stages
Core journey first, then the rest. Each stage is something usable rather than a progress bar.
05
Release and support
Store submission, monitoring, and a plan for what happens after launch.

Tools

What we build apps with.

React

Shared interface code across web and mobile

React Native

One mobile codebase for both app stores

Next.js

Web applications with server rendering where it helps

Node.js

The server side, APIs and background work

PostgreSQL

Reliable relational data for anything with real records

Prisma

Typed database access that catches schema mistakes early

Fit

When an app is worth building.

Worth doing if

You have a process people carry out by hand, by message or on paper, that an app would genuinely remove.
Your customers already ask for something on their phone that you cannot currently give them.
You want an internal tool that removes a specific repeated task.
You have an existing product that needs rebuilding properly rather than patched.

Not worth it if

You want an app that will make money on its own with no promotion behind it. Distribution is the hard part, not development.
The idea is still changing weekly. We can help you settle it, but we cannot build against a moving target.
You need something live in a fortnight. Apps that are rushed ship broken and get abandoned.

Proof

We have done this before.

A few projects where the website had a clear job to do. Open one to see what changed for the business.

View all projects

Questions

App development questions.

If your question is not here, ask it directly. We answer honestly, even when the answer is that we are not the right fit.

Ask a different question

How long does an app take?

A focused app with a handful of screens is usually eight to sixteen weeks. Anything with accounts, payments or a large number of screens runs longer. We will tell you which category yours is in during the first call, before anyone signs anything.

Do you build mobile apps or web apps?

Both. We will usually recommend a web app to start with, because there is nothing to install and it works everywhere. A mobile app is the right call when people need it offline, or when camera, Bluetooth or background location are genuinely part of the job.

What does it cost?

It depends almost entirely on how many screens and user types there are. We quote per project after the scope is written down, and we build in stages so the first payment does not have to carry the whole risk.

Who owns the code?

You do, in full, once each stage is paid for. It is in your name, in your repository, with the documentation to go with it. There is no licence to renew and nothing we hold over you.

Will it work offline?

Only if we build it that way deliberately, and only for the parts that genuinely need it. Offline support is a real decision with real cost, so we scope it as a feature rather than assuming it.

Can you take over an app someone else built?

Often, yes. We will review what exists and give you an honest read on whether it is worth continuing or cheaper to rebuild. Either way you get the assessment whether or not you hire us.

Also available