{"id":12552,"date":"2026-08-19T11:58:53","date_gmt":"2026-08-19T09:58:53","guid":{"rendered":"https:\/\/consultoriaehero.com\/?p=12552"},"modified":"2026-08-19T12:15:10","modified_gmt":"2026-08-19T10:15:10","slug":"how-much-does-it-cost-to-make-an-app-real-prices-and-breakdown-by-phase","status":"publish","type":"post","link":"https:\/\/consultoriaehero.com\/en\/how-much-does-it-cost-to-make-an-app-real-prices-and-breakdown-by-phase\/","title":{"rendered":"How much does it cost to make an app: real prices and breakdown by phase"},"content":{"rendered":"

The question how much does it cost to make an app<\/strong> has a bad reputation because almost nobody answers it. You ask for a quote, they reply \u201cit depends,\u201d and they ask for a meeting. And it does depend, of course, but it can be narrowed down a lot before sitting down to talk. Let\u2019s see exactly what it depends on, with real ranges and with the items almost nobody tells you about until after you\u2019ve signed.<\/p>\n

The short answer<\/h2>\n

An app with a clear purpose, its own server, and published in both stores typically costs between 5,000 and 25,000 euros<\/strong> in the Spanish market. Below 5,000 there is usually a template with your logo on top; above 25,000 there are usually several people working for months and a complex product behind it.<\/p>\n

That range is so wide because the price is not set by \u201cthe app\u201d: it is set by four decisions you can make before asking for a quote.<\/p>\n

The four things that drive the price<\/h2>\n

1. How many screens it has<\/h3>\n

This is the most direct variable. An app with ten screens costs roughly half as much as one with twenty, and the calculation is done screen by screen. Before asking for a quote, sketch on paper the screens you really need for the first version. Almost always there are fewer than it seemed.<\/p>\n

2. Whether it needs its own server<\/h3>\n

An app that only shows information can live on its own. As soon as there are user accounts, changing content, notifications, or any data shared between devices, you need a server with its database and management panel. That takes between 30 and 50% of the budget<\/strong>, and it is the item most often underestimated.<\/p>\n

If you already have a website with an API, or an ERP that exposes data, that part becomes much cheaper: the app connects to what already exists instead of building it from scratch.<\/p>\n

3. Whether it charges inside the app<\/h3>\n

Charging in an app is not just adding a payment button. It involves the payment gateways of each store, subscriptions with their trial periods, purchase verification on your server \u2014 because the phone can be tampered with \u2014 and the commissions from Google and Apple. Add easily between 1,500 and 3,000 euros to the project.<\/p>\n

4. Android, iOS, or both<\/h3>\n

With current tools, you develop once and publish on both platforms, so the extra cost of the second one is no longer 100% as it was a few years ago. Count on 20-30% more for the second store: it is not the code, it is testing on different devices and a second review round.<\/p>\n

Indicative breakdown by phase<\/h2>\n

This is how a typical 9,000-euro project is split, so you can see where every euro goes:<\/p>\n\n\n\n\n\n\n\n
Definition<\/td>\nWhat it does, who it is for, and what the first version does NOT do. The document with the screens and the closed budget comes out of this. 8-12%.<\/td>\n<\/tr>\n
Design<\/td>\nHow it looks and how it is navigated. If you accept the standard components of each system, this item drops a lot. 10-15%.<\/td>\n<\/tr>\n
App<\/td>\nThe development of the screens and the logic on the device. 35-45%.<\/td>\n<\/tr>\n
Server and panel<\/td>\nDatabase, API, management panel, backups, and scheduled tasks. 25-35%.<\/td>\n<\/tr>\n
Publishing<\/td>\nDeveloper accounts, store listings, screenshots, privacy policy, data declarations, and review rounds. 8-12%.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

What almost nobody tells you: the cost of keeping it alive<\/h2>\n

The most expensive mistake is not getting the initial budget wrong: it is not accounting for the second year. An app is not delivered and forgotten.<\/p>\n