The honest answer: it depends on the scope
The price of an app is the price of the work it takes, and the work depends on what the app has to do. Two apps that sound alike, such as “a booking app”, can differ many times over in size once you list what each must do. That is why a price quoted before anyone has written the scope down is a guess, whoever gives it.
The useful question is not what an app costs, but what makes this app bigger or smaller. The rest of this guide is that list.
What makes a build bigger
- Kinds of user. Every kind of user, such as customers, staff and an administrator, needs its own screens and its own rules about what it may see and do.
- Screens and steps. Each screen and each step in a flow is work to design, build and test.
- Rules and edge cases. Cancellations, refunds, limits, approvals and anything that depends on who is asking. Rules are often more work than screens.
- Sign-in and accounts. Letting people sign in, reset a password and manage what is theirs.
- Payments. Taking money, and handling what happens when a payment fails or is refunded.
- Other services. Each connection to something else, such as a calendar, a mailing tool or another company's system, has to be built and tested against that service.
- Tools for you. An admin area where you can see, correct and export your data.
- Design and polish. A custom look, animation and careful wording all take time, and are often worth it.
- One kind of user
- A handful of screens
- Sign-in from the stack
- A web app
- No payments yet
- Guests, staff and an admin
- Many screens and states
- Payments and refunds
- Two app stores
- A calendar and a mailing tool
- An admin area with exports
Web app or app store app
A web app runs in the browser on phones and computers alike, from one build. Many can be installed on a phone from the browser and work offline, without an app store. An app sold through the app stores usually means separate work for each store, and each store's review. If a web app does the job, it is the smaller build.
- One build for phones and computers
- Shared as a link
- Can be installed from the browser
- An update is live for everyone at once
- Work for each store
- Each store’s review before release
- A store listing to keep up
- An update waits for review
Building it and running it are two different costs
Building is the work to make the first version. Running is what it takes to keep it live afterwards: hosting, the database, sign-in, email, and keeping it working. Running is paid every month for as long as the app is live, so ask about both before you commit, and be wary of a price that folds the two together.
Other companies' services, such as a payments provider, bill you directly at their own prices. They are part of the cost of the app, but not of the build.
- The first version, to its written scope
- A price agreed before the work starts
- Hosting and the database
- Sign-in and email
- Watching it, and fixing what breaks
How to keep the cost down
- Start with one kind of user and one main job.
- Write down what the first version is not, and keep to it.
- Prefer a web app unless you need something only an app store app can do.
- Use what the builder already provides, such as sign-in and email, rather than connecting your own.
- Decide the rules early. A rule discovered halfway through the build costs more than one written down first.
The guide on describing your app idea covers how to write the first version down.
How 19 Agents prices a build
The agents turn your idea into a written scope, break it into work items and price them. You see one fixed price for that scope before any work starts, and nothing is built until you accept. If the build costs more than quoted, the price you approved does not change. A change of scope gets its own quote.
The same quote names the Run tier the product falls under, from its scope, performance and scale, with its monthly price, so you see the running cost before you approve the build. A database, user sign-in and email come with the 19 Agents stack. The pricing page has the details, and the guide to fixed-price app development explains what a fixed price should and should not cover.
During the beta
The terms are shared on admission, before you build anything.
- The beta is closed, and admission is gradual. It is not offered in the United Kingdom.
- Every product starts from a new idea. Bringing code you already have comes after the beta.
- The beta is for building and testing: it does not include collecting personal data about real customers or users, or connecting a production database.
- Not every type of application or business requirement is supported yet.
Questions
- How much does it cost to build an app?
- It depends on the scope: how many kinds of user it has, its screens and rules, sign-in, payments and connections to other services. Any price given before the scope is written down is a guess. With 19 Agents you see one fixed price for a written scope before any work starts.
- Why do quotes for the same app idea differ so much?
- Because each builder fills the gaps in the description differently. Compare quotes against the same written scope, and check what each one leaves out.
- Is a web app cheaper to build than an app store app?
- Usually, because one web app runs on phones and computers alike, and many can be installed on a phone from the browser. An app store app often means separate work for each store and each store’s review.
- Does the build price include hosting?
- Not with 19 Agents. Running a released product is a separate monthly price, and the build quote names the Run tier the product falls under, so you see that cost before you approve the build.