Hendeca Labs

How Much Does a Custom App Cost in 2026?

Real price ranges for web apps, iPhone apps, Android apps and cross-platform apps, and what an app keeps costing after it launches.

Izzy Young · Founder, Hendeca Labs

6 min read

"How much does an app cost?" is the first question almost everyone asks me, and the honest answer used to be "it depends."

That's true, but it isn't useful. So here's a more useful answer.

For a small business or startup, a custom app usually costs somewhere between $2,000 and $35,000 to build, depending mostly on what kind of app it is and how much it has to do. Very complex apps cost more.

That's a wide range, so the rest of this article narrows it down: what each kind of app costs, what moves a project from one end of the range to the other, what an app keeps costing after it launches, and how to keep your own project at the lower end.

The prices below are Hendeca Labs' own starting ranges. I've also included what agencies typically charge, so you have something to compare against.

1. The Short Answer: What Does an App Cost?

Here are the ranges by the kind of app you're building.

Kind of app Simple Standard Complex Typical build time
Web app built with Lovable $2,000–$3,500 $4,000–$7,000 $7,500–$12,000 1–3 weeks or more
Native iPhone app (Swift) $8,000–$15,000 $16,000–$30,000 $32,000+ 4–10 weeks or more
Native Android app (Kotlin) $8,000–$15,000 $16,000–$30,000 $32,000+ 4–10 weeks or more
Cross-platform app (iPhone + Android) $10,000–$18,000 $20,000–$35,000 $38,000+ 4–10 weeks or more

These are starting points for a quote, not fixed prices. Scope decides the final number, and you get a written quote before any work starts.

For comparison, industry guides put a simple iPhone app from a large US agency at roughly $25,000–$60,000, a mid-sized one at $60,000–$150,000, and a complex one well above that.

That gap isn't because agencies are dishonest. They carry account managers, project managers, offices and sales teams, and that overhead is built into every quote. A small studio doesn't carry most of it.

You can read more about how I build mobile apps and web apps.

2. What Do "Simple," "Standard" and "Complex" Actually Mean?

The tier names only help if you know which one your idea fits.

Simple

A single-purpose app. It does one job well, with no backend or a light one.

Examples: a booking tool for one location, a calculator or quoting tool for your customers, an internal checklist app for your team.

Standard

A multi-screen app that talks to a backend. This is where most real business apps land.

Examples: an app where customers sign in, see their orders or appointments, and get notifications; a member app for a gym or church; a tool your staff use to log jobs in the field.

Complex

Heavier integrations, user accounts with different roles, payments, and a longer build.

Examples: a marketplace with buyers and sellers, an app that takes payments and syncs with your accounting software, anything with real-time features like chat or live tracking.

If you're not sure which tier your idea is, that's normal. Working it out is the first thing we do together.

3. What Pushes the Price Up?

Two apps with the same number of screens can cost very different amounts. These are the things that usually make the difference.

Accounts and sign-in

The moment people need to sign in, the app needs secure accounts, password resets, email verification, account deletion and somewhere to store everyone's data safely. That's real work, and app stores now require some of it, such as letting people delete their account.

Payments

Taking money means a payment provider, receipts, refunds, failed-payment handling and, on phones, following Apple's and Google's rules about in-app purchases. It's one of the most common reasons a project moves up a tier.

Integrations

Connecting to your existing systems, such as a calendar, a CRM, accounting software or a shipping provider, adds time for each one. Some services have good tools for developers. Others are painful to work with, and that shows up in the quote.

Both phone platforms

Building separate native apps for iPhone and Android roughly doubles the work. A cross-platform app shares one codebase across both and typically costs 30–40% less than building two native apps.

The number of people who sign off

This one surprises people. A project with one decision-maker moves faster than one where four people need to approve every screen. More reviewers means more rounds of changes, and more rounds mean more time.

Uncertainty

If the idea is still changing, the build changes with it. That isn't a bad thing. It's often how good products get made. But it costs more than building something that's already clearly defined.

4. What Does an App Cost After It Launches?

The build is only part of the cost. An app also costs money to run and to keep working.

App store accounts

  • Apple: $99 a year for a developer account.
  • Google Play: a one-time $25 fee.

Both accounts should be in your name, not your developer's. That way the app is unambiguously yours.

Hosting and backend

If the app needs a backend (the servers and database behind it), running it usually costs nothing at launch and up to $50+ a month as it grows. Many small apps stay in the free tiers of their hosting services for a long time.

Maintenance

Phones get new operating systems every year, and apps need updating to keep up with them. Libraries need security patches. Bugs turn up once real people use the app.

Hendeca Labs' maintenance plans start at $149 a month for a web app, $249 a month for a native iPhone or Android app, and $299 a month for a cross-platform app. They cover updates, security monitoring, backups, crash monitoring and small fixes.

For comparison, agency app retainers commonly start around $900 a month.

Maintenance is optional, and some apps can go months without needing anything. But budgeting for it from the start is much better than discovering the app stopped working after an iOS update.

5. How Can You Keep the Cost Down?

You have more control over the price than you might think.

Start with the smallest version that's useful. Most first versions try to do too much. Pick the one problem your app solves, build that well, and add features once real people are using it. This is usually the single biggest saving.

Consider a web app first. If your customers don't need anything a phone app uniquely offers, such as notifications, offline use or the camera, a web app works on every phone and computer from day one and costs a fraction of two native apps.

Choose cross-platform if you need both phones. Unless you need the very most from one platform, one shared codebase is the better deal.

Be decisive about who signs off. One person with the authority to say yes keeps the project moving.

Have your content ready. Text, images, prices and policies that arrive late hold up the build.

6. Why Not Just Hire the Cheapest Developer?

You'll find quotes far below these ranges, especially from overseas freelancers or marketplaces.

Some of them are excellent. Plenty aren't.

The risk with a very cheap build isn't usually that you get nothing. It's that you get something that works in the demo and then becomes expensive: it breaks on certain phones, gets rejected by the App Store, can't be extended without starting over, or depends on a developer who has stopped replying.

Whoever you hire, ask these questions before you sign:

  • Will the code, the app store accounts and the hosting accounts be in my name?
  • What happens if the app is rejected by Apple or Google?
  • What's included after launch, and what does support cost?
  • Can I see apps you've already shipped?

Good answers to those questions are worth more than a lower number.

7. A Final Thought: Price the Problem, Not the Features

It's easy to price an app by counting features. A better way is to ask what problem the app solves and what solving it is worth to your business.

An internal tool that saves your team five hours a week pays for itself quickly. A customer app that nobody needs won't pay for itself at any price.

That's why every project at Hendeca Labs starts with a conversation, not a quote. Sometimes the right answer is a smaller app than you expected. Sometimes it's no app at all.

You can see apps and sites I've built, and if you have an idea you'd like priced, I'd be happy to talk it through with you and send you a written quote.