How to Price Mobile App Development: A Worked Quote
Estimate an app build feature by feature, set an hourly rate above your floor, add contingency and split the price into milestones. Worked $36,000 quote.
To price mobile app development, you need an hourly rate that covers your costs and an honest estimate of the hours the scope will take. The fixed price, the milestones, the change-order rate and the support retainer all follow from those two numbers. This guide builds one quote from start to finish, using the same project as the app developer invoicing guide, so you can see the quote turn into invoices. It does not publish "typical app costs": a figure without a scope is not a price anyone can hold you to.
| What you are pricing | How to price it | Worked example result |
|---|---|---|
| Hourly rate | At or above your rate floor, adjusted for the work and the client | $120 per hour |
| Fixed-price build | Feature-by-feature hours × rate, plus contingency | 250 h + 20% = 300 h → $36,000 |
| Payment schedule | Milestones tied to testable builds | 15% / 35% / 30% / 20% |
| Change requests | Estimated hours × the same rate, approved before work starts | 22 h → $2,640 |
| Post-launch support | Capped hours per month × rate | Up to 10 h, not to exceed $1,200 |
| Store accounts | Paid by the client, in the client's name | Apple 99 USD a year; Google Play US$25 once |
How do you set an hourly rate for app development?
Start from your rate floor, the rate below which every hour costs you money, and price above it. The floor is what you need to earn in a year (pay, benefits you buy yourself, self-employment tax and business costs such as test devices and software) divided by the hours you can realistically bill. The freelance rate floor guide works through that calculation step by step; its example floor is about $97 an hour.
For context on salaries, the US Bureau of Labor Statistics Occupational Employment and Wage Statistics for software developers (May 2025) put the median wage at $65.38 an hour ($135,980 a year) and the mean at $71.20. These are employee wages, not client rates, and they exclude the self-employed. A freelancer who wanted to match the median salary would need a rate well above $65.38, because a freelance rate also pays for benefits, taxes, equipment and unbilled time.
The example developer charges $120 an hour, above their floor, because they have shipped several store apps and the client is a funded startup. That choice is theirs; the floor only tells them the lowest rate they can accept.
How do you estimate the hours for an app build?
Break the scope into features and tasks, estimate each one, and include the work that is easy to forget: QA across devices, store submission and project communication. Hypothetical example: a booking app for a mobile dog-grooming startup, built for iOS and Android from one cross-platform codebase, with a small backend.
| Scope item | Estimated hours |
|---|---|
| Discovery workshop and clickable prototype | 30 |
| Backend: data model, booking API, simple admin panel | 55 |
| Sign-up, login and customer profiles | 20 |
| Booking and calendar flow | 50 |
| Card payments through the client's payment provider SDK | 30 |
| QA on a device matrix (recent iPhones and Android phones, two OS versions each) | 35 |
| Store listings, privacy details, submission and review responses | 12 |
| Project management: weekly calls, demos, written updates | 18 |
| Estimated hours | 250 |
| Contingency, 20% (this developer's choice for a first build with a new client) | 50 |
| Hours priced | 300 |
| Fixed price | 300 × $120 = $36,000 |
Push notifications were left out of the first version to keep the budget down. When the client asked for them mid-project, they became change order CO-02: 22 hours × $120 = $2,640, approved before work started.
Three habits make estimates more reliable:
- Price discovery first if the scope is vague. The 30-hour discovery and prototype phase can be sold on its own (30 × $120 = $3,600) and turned into a fixed quote for the rest once the screens and integrations are agreed.
- Write down what is excluded. In this quote: push notifications, a web booking page, offline mode, translations and any server costs. Exclusions are what make the change-order rate enforceable.
- Compare with your records. If your last two booking flows took 70 hours, a 50-hour estimate is a hope, not an estimate.
How does native versus cross-platform change the price?
It changes the hours, so it changes the price; the rate stays the same. The example uses one cross-platform codebase. If the client wanted separate native apps, the developer would re-estimate the client-side items (sign-up, booking, payments and a second QA pass) for a second codebase. Suppose that adds 90 hours: 340 hours estimated, 408 with the 20% contingency, and 408 × $120 = $48,960. That increase is this developer's estimate for this scope, not a general ratio. Show the client both totals with the trade-offs, and let them choose.
How should you split the price into milestones?
Tie each payment to something the client can check, not to a calendar date. The example uses four milestones, matching the app developer invoicing guide:
| Milestone | Client can verify | Share | Amount |
|---|---|---|---|
| 1. Prototype approved | Clickable prototype signed off | 15% | $5,400 |
| 2. Feature-complete test build | TestFlight and Google Play internal-testing builds | 35% | $12,600 |
| 3. Store submission | Release candidates submitted to both stores | 30% | $10,800 |
| 4. Launch and warranty | 30-day warranty ends with no open critical bugs | 20% | $7,200 |
| Total | 100% | $36,000 |
Milestones are payment points, not a timesheet. Milestone 1 bills $5,400 for discovery work estimated at 36 hours with contingency ($4,320), which keeps payments a little ahead of the work and tests whether the client pays on time before the largest phase begins. The last 20% depends on store approval and the warranty period, so be clear in the contract that a store rejection caused by the client's content or business model does not delay payment indefinitely. The milestone invoicing guide covers the wording.
Who pays for store accounts and running costs?
The client, and the accounts should be in the client's name so the client owns the app listing. Apple states that "The Apple Developer Program is 99 USD per membership year" and that prices may vary by region (Apple Developer: Enrollment, accessed 27 October 2026). Google Play says: "There is a US$25 one-time registration fee" (Play Console Help: Get started with Play Console, accessed 27 October 2026).
List every running cost in the quote as the client's: store fees, backend hosting, the payment provider's fees, email or SMS services and any paid SDKs. If you pay one on the client's behalf, bill it at cost with the receipt, as the invoicing guide does with the $25 Google Play fee. Keeping these out of your fixed price avoids paying for the client's servers out of your margin for years.
How do you price changes and post-launch support?
Use the same hourly rate for both, with written approval and a cap.
- Change orders. Estimate the hours, multiply by the contract rate and get approval before starting. CO-02 at 22 hours is $2,640, and it appears as its own line on the next milestone invoice. The project total becomes $36,000 + $2,640 + the $25 store fee reimbursed = $38,665.
- Warranty. Fixes to defects in what you delivered, for an agreed period (30 days here), are already paid for in the final milestone.
- Support and maintenance. Operating system updates, SDK and library upgrades and store policy changes are new work after the warranty. Price them as a monthly retainer of capped hours: up to 10 hours at $120, not to exceed $1,200. In a month with 7.5 hours of work the invoice is 7.5 × $120 = $900. The retainer invoicing guide covers the agreement.
How should you raise your rates as an app developer?
Recalculate your floor each year and quote new projects at the new rate; apply increases to existing support retainers at renewal, with written notice. A move from $120 to $130 an hour adds $3,000 to the same 300-hour build ($39,000 instead of $36,000) and $100 to a full 10-hour support month. Showing the client the arithmetic makes the change easy to accept. The rate increase guide has notice wording.
When is a fixed-price quote the wrong fit?
- Scope still unclear after discovery. If the client cannot describe the screens and integrations, sell time and materials in short sprints with a weekly budget report, or sell another discovery phase.
- Hardware, regulated data or heavy integrations. Bluetooth devices, health or financial data, and legacy systems carry risks a contingency cannot price. Quote those parts by the hour.
- Equity instead of cash. Equity is an investment decision, not a rate. Price the work in cash first, so both sides know what is being exchanged, and take legal and tax advice before accepting shares for services.
- Subcontracting for an agency. The agency owns the client and the milestone plan; you usually bill hours against its purchase order.
From quote to invoice with InvoiceQuickly
InvoiceQuickly is invoicing software, not a project estimating tool. Pro includes timer and manual time entries, but it does not estimate hours or connect to Jira, GitHub or app stores. Once the quote is agreed:
- Estimates (Pro): send the milestone plan as an estimate; the client accepts it in their portal and you convert it to an invoice.
- One invoice per milestone, with the build number in the description, and change orders as separate lines with their approval dates. There is no deposit feature, so the first milestone is its own invoice.
- Recurring invoices (Pro): a monthly schedule can create the support retainer as one line with saved tax, discount and payment terms, as a draft for you to adjust to the hours used.
- Payments: record full or partial payments on every plan; on Pro, add a Stripe or PayPal link from your own account.
The Free plan includes 5 invoices, 5 clients and 3 AI drafts; Pro is $9/month. See pricing, the mobile app developer invoice template, the payment terms guide and more pricing guides on the InvoiceQuickly blog.
Frequently asked questions
How do you calculate the cost of developing an app?
Estimate the hours for each feature and task, including QA, store submission and project communication, add a contingency, and multiply by your hourly rate. In the worked example, 250 estimated hours plus 20% is 300 hours, and 300 × $120 = $36,000.
How much should a freelance app developer charge per hour?
At least your rate floor: what you need to earn in a year, including taxes, benefits and costs, divided by the hours you can bill. Experience, the client and the risk in the scope decide how far above it you go. For context, BLS data put the May 2025 median wage for employed software developers at $65.38 an hour, which a freelance rate has to exceed to cover what an employer would otherwise pay for.
Should app development be fixed price or hourly?
Fixed price works when discovery has produced a clear scope, and it should include a contingency and a change-order rate. Hourly, in short sprints, suits unclear scopes and risky integrations. Many developers sell discovery by the hour and the build at a fixed price.
Who pays for the Apple and Google developer accounts?
The client, with the accounts in the client's name. Apple's Developer Program is 99 USD per membership year and Google Play charges a US$25 one-time registration fee. If you pay either on the client's behalf, bill it at cost with the receipt.
How do you price app maintenance after launch?
As a monthly retainer of capped hours at your rate, after a defined warranty period. For example, up to 10 hours at $120, not to exceed $1,200 a month, billed for the hours used with a ticket list.
What milestones should an app development quote use?
Points the client can verify: an approved prototype, an installable test build, store submission, and the end of the warranty period. The example splits $36,000 into 15%, 35%, 30% and 20%.
Practical guidance for freelancers and small businesses creating and managing invoices.
Create your next invoice from one prompt
Describe the client, work, prices, and payment terms. Review every field before you send.
Create a Free InvoiceRelated guides
How to Price Consulting: Day Rates, Project Fees, Retainers
Turn your rate floor into a day rate, a fixed project fee and a retainer, check the fee against client value, and invoice it. One engagement, fully worked.
How to Price Copywriting: Per Word, Per Project or Retainer
Price copy from the hours each deliverable takes, see when per-word rates work and when they underpay, and compare quotes with the EFA's 2026 rate chart.
How to Price Graphic Design: Project Fees and Usage Rights
Turn your rate floor into a brand identity quote and price copyright assignment, licences, revisions and unused concepts as separate lines. Worked example.
How to Price Illustration Work: Creation Fees and Licences
Price illustration as a creation fee plus a usage licence: a worked quote-to-invoice example, 2026 survey data on how illustrators charge, and kill fees.
Useful, occasional notes
Get invoicing tips that actually help
Join the InvoiceQuickly update list for practical invoicing advice and product news.
No spam, ever. Unsubscribe anytime.