Cost to Rebuild an App: What You'll Pay and When to Skip It

Picture a physical therapy group in Tampa. A contractor built its booking app in 2021. It still works, mostly, but the calendar screen freezes on newer iPhones and the contractor stopped replying last spring. The owner asks two developers to take a look. One says it needs a small update. The other says the whole thing has to be rewritten, and that quote is five times higher. Both sound completely sure, and the owner has no idea what the cost to rebuild an app should even look like.

"They did it by making the single worst strategic mistake that any software company can make: They decided to rewrite the code from scratch."

Joel Spolsky, Things You Should Never Do, Part I, Joel on Software, 2000

Spolsky was writing about Netscape, and developers have argued with him ever since. We side with him more often than not, even though we'd get paid more if we didn't. Some apps do need replacing, though. So here's the cost to rebuild an app as we'd work it out, the bills that tend to go missing from the first quote, and a test you can run on your own app before you pay anybody.

What's the cost to rebuild an app?

Price it like a new app of the same size. A rebuild means writing the thing again, so the hours look a lot like the first time around, and the old code saves less than owners hope. These are the same sizes we use in our app development cost guide:

You'll see other guides quote a rebuild as a percentage of what the first version cost. We wouldn't plan a budget that way. Your original invoice tells you what one team charged in 2021, at their rate, for features you may have stopped using by now. The size of the app you need today is what sets the price.

That Tampa app has logins, payments and notifications, so it's mid-size. Two things can move it down the range: cutting the screens your analytics show nobody opens, and keeping a healthy backend while replacing only the app people hold in their hands.

The bills that don't make the first quote

The price table covers the new build. Moving your business onto it is a separate job, and it's where rebuild budgets tend to go wrong.

Get the store listing wrong and it's expensive to undo. Apple ties your listing to a bundle ID, and Google ties it to a package name and signing key. Keep those and your rebuild reaches customers as a normal update with your reviews intact. Lose them and you're publishing a brand new app with zero reviews, then asking every customer to go and download it.

If those accounts are in a former developer's name, fix that before anything else. Our source code ownership checklist shows how to check and what to ask for.

Six questions to run before you pay for a rebuild

Answer these yourself, or pay a developer for a few hours to answer them with you. Use someone who isn't quoting the rebuild.

Our rule of thumb: four or more answers on the right, budget for a rebuild. Two or three, replace the worst part first. One or none, fix what you have.

You'll notice "the code is messy" isn't on the list. Developers say that about almost any code they didn't write, and on its own it tells you nothing about what the app costs your business. If someone's case for a rewrite stops there, ask which of these six answers they'd change, and why.

A Google Play warning doesn't mean your app is dead

Since August 31, 2026, Google Play requires new apps and updates to target Android 16 (API level 36). Existing apps need to target at least Android 15 (API level 35) to stay available to new users on newer Android phones. The extension Google offered ran out on November 1.

Had a warning about this from Google? Slow down. For most apps it's an upgrade job: raise the target version, fix whatever the Android behavior changes break, retest and resubmit. It only counts toward a rebuild if the framework or old plugins can't compile at that target, which is the second question in the table.

The option most people skip: replace one piece at a time

You can usually replace the worst section first and leave the rest running. In Tampa, that might mean a new booking flow on the existing backend, shipped in weeks. Customers get the fix quickly, and if that solves the problem you can stop there and keep your money.

We build new products the same way: ship something small in weeks, see what happens, then build the rest. It won't suit an app whose foundations are the problem, though. If the data structure is wrong, every new piece inherits the mistake.

When a rebuild was the right call

I've made this call myself. Rezaid Film Manager is a project management platform for film production. It had been built and was in testing, but it needed an architecture it could grow on. As Solutions Architect I own the system design, and I led a rebuild on the MERN stack (MongoDB, Express, React and Node).

Most of the hidden cost table didn't apply, because there was no user base yet and no reviews to protect. That's the cheapest moment you'll ever get to rebuild an app. Five years and thousands of customer records later, the same decision costs far more, so run the test early.

What to get in writing before you sign

We've delivered 1,000+ projects in 9+ years, and we start them all the same way: drawing the client's system, meaning what the app's main job is, what connects to what, and who maintains it. Ask any team you're considering for that drawing. Then ask for:

• Data migration as its own line in the quote, with a say on who checks the results
• The store listing plan
• A switch-over date, plus how long the old backend stays on
• A short handover document, so you never end up where the Tampa owner is now

If you want a second opinion on a quote you've received, our mobile app development team will go through it with you.

FAQs

How much does it cost to rebuild an app?

About the same as building a new app of that size, plus migration work. At US and UK agencies that's $15,000 to $40,000 for a simple app and $75,000 to $150,000 for a mid-size one. Our own prices run from $7,000 to $32,000 for simple apps and $16,000 to $120,000 for mid-size ones.

Is it cheaper to fix an app or rebuild it?

Fixing is usually cheaper if the framework is still maintained and the bugs sit in a few screens. Once every fix breaks something else, or the data structure no longer fits your business, patching can end up costing more over time than replacing it.

Will I lose my reviews and users if I rebuild my app?

You won't if you release the new version as an update to the same listing, using the same bundle ID on Apple and the same package name and signing key on Google. Publish it as a new app and you'll start again with zero reviews.