The question "how much does it cost to develop an app?" has an honest answer and a useful answer. The honest one: anything from a couple of hundred thousand to tens of millions of kronor. The useful one: the cost is predictable once you understand what drives it, and you can influence most of the drivers before a single line of code is written.
This guide covers what determines the price, which ranges are reasonable on the Swedish market in 2026, where the hidden costs are, and how to keep the total down without building a worse product.
The cost drivers: what determines the price
App development is in practice priced as hours times hourly rate. What separates a 300,000 SEK app from a 3 million SEK app is the number of hours, and the hours are driven by five factors.
Platforms
Should the app exist on iOS, Android or both? Two separate native apps essentially mean double the development work. Cross-platform frameworks (more on that below) reduce the difference but do not remove it. Also remember that many "apps" need a web interface too, such as an admin panel, which nobody includes in the first estimate.
Feature complexity
The number of screens says less than what happens behind them. Authentication, real-time features like chat or live updates, offline support with synchronization, payment flows, maps and location, push notifications with logic behind them: each such feature adds hours. A good exercise is to list the features and ask what happens if each one is cut. The ones that survive that question are your real requirements list.
Backend
Almost every app needs a server side: database, APIs, user management, business logic. The backend often accounts for 30 to 50 percent of total development cost and is at the same time the part buyers most often underestimate, because it is invisible in the sketches. An app that only presents content from an existing system is far cheaper than one that needs its own backend built from scratch.
Design
An app that follows the platforms' standard components is cheaper to design and build than one with a custom interface, bespoke animations and a unique visual identity. Design also includes work that does not show: user flows, prototypes and usability testing. Cutting corners here is often expensive, since a mistake caught in design costs a fraction of a mistake caught in code.
Integrations
Does the app need to talk to an ERP, a CRM, a payment provider or external data sources? Integrations vary enormously in cost depending on how well documented the other party's APIs are. A modern REST API with good documentation is days of work. A legacy business system without a public API can be months. We build API integrations for companies where this exact part turned out to be the project's biggest risk, so estimate it early.
Approximate price ranges on the Swedish market in 2026
The ranges below are broad and approximate. They reflect what established Swedish agencies and development firms typically charge, not individual freelancers or offshore teams. Your actual quote depends on everything above.
MVP, simple app: roughly 200,000 to 500,000 SEK. A few screens, standard components, login, a simple backend or an integration with an existing system. The purpose is to test an idea on real users, not to build the finished product.
MVP, more ambitious: roughly 500,000 to 1 million SEK. More features, its own backend, one or a few integrations, polished design.
Full-scale product: roughly 1 to 3 million SEK. Multiple platforms, complete backend, several integrations, payment flows, admin tools, scalable architecture.
Complex product: from roughly 3 million SEK and up. Large-scale real-time features, high security requirements, AI functionality, many integrations. There is no upper limit here; large consumer apps have development budgets of tens of millions per year.
One more benchmark: apps with built-in AI functionality, such as assistants or intelligent content handling, typically add both development time and ongoing operating costs for model calls. We work with AI development as part of app projects and almost always recommend phasing AI features separately, since they are the hardest to estimate.
Native or cross-platform: what does it do to the budget?
Native means separate apps built with Apple's and Google's own tooling (Swift for iOS, Kotlin for Android). Cross-platform means one shared codebase, using frameworks like React Native or Flutter, running on both platforms.
Budget-wise:
- Cross-platform typically saves 30 to 40 percent compared to two native apps, not 50, since some platform adaptation is always required and testing still happens on both platforms.
- The saving shrinks with complexity. Advanced camera handling, Bluetooth, background processing and heavy animations often require platform-specific code even in cross-platform projects.
- Maintenance gets cheaper with one codebase: a bug is fixed once, a new feature is built once.
For most business apps and MVPs, cross-platform is the right starting point today. Native is justified when performance is critical, when the app depends heavily on platform-specific features, or when it will live for many years with a large team. The wrong choice in the other direction, going native "just to be safe" for an app that does not need it, is one of the most common ways to burn budget unnecessarily.
Hidden costs: what is not in the quote
The development cost is not the total cost. Plan for the following:
Maintenance and further development. A common rule of thumb is 15 to 20 percent of the development cost per year. iOS and Android release new versions every year, third-party libraries get updated, real users find bugs. An app that is not maintained stops working in practice within a couple of years.
App store fees. Apple's developer account costs 99 USD per year, Google's is a 25 USD one-time fee. The big item is the commission: Apple and Google take 15 to 30 percent of revenue that goes through the stores' payment systems. If the app sells digital services, this affects the entire business model and belongs in the calculation from day one.
Third-party services. Server hosting, databases, push notifications, maps, analytics, crash reporting, email and SMS. Small amounts individually, together typically a few thousand kronor per month for a smaller app, and considerably more as the user base grows. Services with free entry tiers can get expensive exactly when the app starts to succeed.
Publishing and review. App Store review can require changes and resubmissions, especially on first publication. Budget calendar time and some development hours.
Legal and compliance. Privacy policy, GDPR handling, terms of service. Not large amounts, but zero is the wrong number.
How to keep the cost down
Three things affect the total cost more than any negotiation over hourly rates:
Clear scope before start. The most expensive app is the one that changes direction mid-build. Spend time defining what the app should do, for whom, and above all what it should not do in version one. Every feature cut before the start is free; the same feature cut halfway through has already cost design, architecture and partial development.
Prototype first. A clickable prototype costs a fraction of development and exposes most flawed assumptions: flows that do not hold up, features nobody uses, screens that are missing. Test the prototype on five real users before any code is written. It is the cheapest quality assurance available.
Build in phases. Build an MVP with the core feature, launch, measure, and let real usage decide what gets built next. The opposite, building everything at once, means paying full price for features that turn out to be unnecessary. Phasing also makes the budget controllable: every phase is a decision point.
Questions to ask a vendor
A quote is only comparable if you know what it contains. Ask these questions:
- What exactly is included: design, backend, testing, publishing, project management?
- What does maintenance cost after launch, and what does it include?
- Who owns the code and all accounts (App Store, Google Play, cloud, domains)?
- Which tech stack do you propose, and why that one for our project?
- How are changes handled during the project, and what do they cost?
- What happens if we want to switch vendors in two years? How transferable is the solution?
- Can we get references from clients with similar projects?
A vendor who gives evasive answers to questions 3 or 6 should not be hired, regardless of price. Lock-in is a real cost that never shows up in the quote.
A worked example: what affects your specific estimate
Take a hypothetical booking app for a service business: users log in, see available times, book and pay. As a cross-platform MVP with standard components and an integration with an existing booking system: likely in the range of 400,000 to 700,000 SEK, approximately. The same app with its own booking engine in the backend, national e-ID login, card payments via a custom integration and bespoke design: likely above a million. The feature list looks almost identical on paper. The difference is in what gets built behind the screens.
That is why a fixed price without a thorough requirements review is a warning sign. Serious vendors want to understand the project before they name a number.
Next steps
Want a concrete picture of what your app idea would cost? At Shapp we work with app development from prototype to launched product, and we always start with scope and prototype before talking total budget. That gives you a number that holds, instead of a guess that cracks.
