What does it cost to build an app?

The short answer: 2026 cost ranges

Here are current Swedish-market ranges as of 2026, drawn from published Swedish agency price guides and our own build experience. These cover design and development of the first shippable version, not ongoing running costs (those are separate, further down). Cross-platform here means one codebase shipping to both iOS and Android — the approach we use, via Capacitor.

Why such wide bands? Because "an app" can mean a focused MVP that proves one idea, or a multi-role platform with billing and live data. The bands above reflect typical Swedish rates of roughly 800–1 200 kr/h for a senior freelancer or 900–1 800 kr/h for an agency, multiplied by realistic hours. The honest version: the only way to narrow a 300 000 kr range to a real number is to define the scope.

What actually drives the cost

Price is the sum of a handful of decisions. Each one moves the number meaningfully, and most of them are about scope rather than technology:

• Screens and flows — every screen is design, build, edge cases and testing. Going from 8 screens to 25 is the single biggest multiplier on most projects.
• Backend and API — if the app stores data, has accounts, or syncs across devices, it needs a backend. This is often as much work as the app itself, and sometimes more. We build on Cloudflare Workers (edge) and Neon Postgres, which keeps this lean.
• Native vs cross-platform — building separately for iOS and Android (native) costs roughly 40–80% more than one cross-platform codebase. With Capacitor we ship one React + TypeScript codebase to both stores, so you pay closer to the cost of a single app, not two.
• Design — a templated look is cheap; a distinctive, branded, animated interface costs more because it's drawn, not assembled. Most products sit in between.
• Integrations — payments (Stripe), auth, maps, push notifications, analytics, third-party APIs. Each one is a connection to test and maintain. Two or three is normal; ten is a different project.
• App Store submission — getting onto the App Store and Google Play is mostly process: store accounts, signing, review, privacy declarations. It's modest in hours but a real step, and Apple's organization enrollment is a prerequisite many first-timers don't budget for.
• Maintenance — apps aren't finished at launch. iOS and Android ship breaking OS updates yearly, dependencies need patching, and users find bugs. Plan for it from day one (see below).

Native vs cross-platform — the cost lever most people miss

The biggest avoidable cost in app development is building the same app twice. Fully native means a separate iOS codebase (Swift) and Android codebase (Kotlin) — two teams, two builds, two sets of bugs. Swedish guides put native at roughly 40–80% more than cross-platform for the same scope.

Cross-platform writes the app once and ships it to both stores. We build with Capacitor wrapping a React 19 + TypeScript app, which means one codebase, one set of features, both App Store and Google Play — and the same web stack can power a marketing site or web dashboard from the same code. For the large majority of products, native's marginal benefits don't justify paying for two of everything. We'll tell you honestly on the rare occasions a true native build is the right call.

A worked example: a real MVP

Say you want to validate a consumer app idea: users sign up, see a personalised feed, save items, and you can push them a notification. Roughly:

• 8–10 screens with a clean, branded design — not a template, not a custom illustration suite.
• Accounts and login, a backend storing user data, a simple admin view for you.
• One payment or subscription flow if you're charging, plus push notifications.
• Shipped to both the App Store and Google Play from one Capacitor codebase.

That lands in roughly the 150 000–350 000 kr band in 2026, over about 6–10 weeks. It's a real, shippable product you can put in front of users — deliberately scoped so you spend on learning whether the idea works, not on features you're guessing at. Add roles, heavier integrations, or a bespoke design language and you move up toward the standard-app band.

Ongoing costs after launch

Launch is the start of the cost, not the end of it. Budget separately for the running costs below — they're small next to the build, but real and recurring.

The maintenance line is the one founders most often forget. A 300 000 kr app realistically costs on the order of 45 000–60 000 kr a year to keep healthy. Skipping it doesn't save money — it just defers the bill to the day an OS update breaks the app.

How Klura prices — and why it's different

We're a senior, independent studio, not an agency. That changes the maths in your favour in a specific way: there's no account manager, no sales layer, no junior-billed-as-senior, and no overhead markup baked into the rate. You talk to the person who actually designs and writes the code.

Practically, that means a quote scoped to what your product needs rather than padded to feed a team, and decisions made by someone who has to live with them. Klura is a registered Swedish AB (org.nr 559530-1465) with a named, accountable owner — you know exactly who is on the hook. This very site runs on the same stack we'd build your app on: TanStack Start on Cloudflare Workers. It's a working proof artifact, not a slide.

We don't publish a fixed price list, because an honest number depends on your scope and a made-up one helps nobody. What we will do is give you a straight, indicative range on a first call and a fixed proposal once the scope is clear.

FAQ