TL;DR
On this page
A 2026 freelance mobile app developer invoice has a different shape than a generic dev invoice. The line items handle App Store and Google Play developer fees and revisions, the milestones gate on TestFlight or Play Console acceptance rather than calendar dates, and the payment terms have to absorb the iteration risk that comes with App Store rejection cycles, OS-version compatibility surprises, and third-party SDK changes that surface only after the build hits real devices.
The general invoice basics live in how to write a freelance invoice. The hourly + project + retainer rate research is in mobile app developer freelance rates 2026. The companion proposal that locks deliverables and acceptance criteria is in mobile app developer proposal template.
Why Mobile App Developer Invoices Are Different
A web developer invoice scopes a single deployment target (the browser). A mobile app developer invoice scopes two stores (Apple App Store + Google Play) with their own submission processes, fee structures, review timelines, and acceptance gates. That changes the invoice in three concrete ways.
| Profession | Typical lines per invoice | Unique cost element |
|---|---|---|
| Web developer | 1-12 | Hosting, domain, third-party SaaS |
| Data engineer | 6-15 | Warehouse compute + storage + orchestration + observability |
| AI engineer | 6-15 | LLM inference + embedding + vector DB + GPU hours |
| Mobile dev | 6-12 | Apple Developer Program + Google Play Console + SDK fees + store submission time |
The store submission and revision time line is the most-overlooked cost in mobile dev invoicing. Both the App Store and Play Store have review processes that require time to package, submit, respond to rejections, and resubmit. Mature mobile freelancers bill this time explicitly on milestone or hourly invoices rather than absorbing it into the engineering subtotal.
The 4 Billing Models for Mobile Development in 2026
There are four production billing models. Each has a use case and a specific invoice format.
| Model | Use case | Invoice format |
|---|---|---|
| Hourly | Maintenance, store rejection response, OS patches | Line per task with hours and rate |
| Fixed-bid project | MVP build, defined-scope feature | One project line + change-order lines + store fee + SDK pass-through |
| Milestone billing | Multi-stage delivery work over $10K | One invoice per milestone tied to TestFlight/Play Console acceptance |
| Retainer (monthly) | Ongoing dev + maintenance + store submissions | Fixed monthly retainer + overage hours line + per-month SDK fees |
Per Second Talent's 2026 freelance mobile app developer hourly rate data, the senior median hourly anchor is $145 (cross-platform baseline), with native iOS at $155, native Android at $140, and specialists in AR/game/native performance at $275-$450+. Set your change-request hourly rate at the same number you would charge for a standalone hourly engagement.
Sample Hourly Invoice (Maintenance + App Store Rejection Response)
The hourly format works for maintenance, App Store rejection responses, OS-update compatibility patches, and exploration. Each task gets its own line.
| Description | Hours | Rate | Amount |
|---|---|---|---|
| iOS 18 compatibility patch (deprecated API replacement) | 5.0 | $145 | $725 |
| App Store rejection response (Guideline 2.3 metadata clarification) | 2.5 | $145 | $362.50 |
| Resubmission packaging + screenshots regeneration | 2.0 | $145 | $290 |
| Production crash investigation (Sentry → root cause) | 4.5 | $145 | $652.50 |
| Subtotal (engineering) | - | - | $2,030 |
| Sentry pass-through (March 2026 plan, dashboard attached) | - | - | $26 |
| Total due | - | - | $2,056 |
Notes:
- Each engineering line names the actual deliverable and the App Store guideline / OS version / specific bug, not "consulting" or "engineering work" generically.
- Store rejection response time bills explicitly. Mobile freelancers who absorb this work into the engineering subtotal end up underwater on rejection-heavy projects.
- Third-party SDK pass-through gets its own line with a dashboard screenshot attached as PDF.
Sample Milestone Invoice (Cross-Platform MVP, 33/33/34 Split)
For a $36,000 cross-platform MVP project split across three milestones per Plutio's 2026 invoice payment terms guide. This is the second of three invoices.
| Description | Amount |
|---|---|
| Milestone 2 fee - Core feature flow accepted in TestFlight + Play internal testing (per Section 4.2 of MSA) | $11,880 |
| Approved change order CR-002: in-app purchase flow added (RevenueCat) | $3,200 |
| Apple Developer Program annual fee pass-through (March 2026 renewal) | $99 |
| RevenueCat pass-through (March 2026 plan, dashboard attached) | $89 |
| Firebase pass-through (March 2026 - Crashlytics + Auth, dashboard attached) | $42 |
| Branch deep-link service pass-through (March 2026) | $35 |
| Subtotal | $15,345 |
| Less: Deposit credit (25% of total project value applied to milestones 1+2) | -$4,500 |
| Total due | $10,845 |
| Payment terms: Net 15. Late fee 1.5% per month after due date. | - |
Notes:
- Milestone fee references the contract section that defines the deliverable. The acceptance criterion (accepted in TestFlight + Play internal testing) is binary and auditable; the client either accepted the build or did not.
- Apple Developer Program fee passes through at cost when it falls in the project window. Same for renewals during a multi-month engagement.
- Each SDK line names the provider AND notes the dashboard is attached. Mature buyers will not reimburse pass-through without backup.
- Deposit credit applied as a negative line. Cleanest pattern: 50 percent of deposit to milestone 1, 50 percent to milestone 2, milestone 3 paid in full.
Sample Retainer Invoice (Standard Mobile App Maintenance + Dev)
Retainers are common in 2026 for production mobile apps where the engineer is on-call for OS updates, store submissions, third-party SDK breaking changes, and ongoing feature delivery.
| Description | Amount |
|---|---|
| Monthly retainer - Standard tier (50 hours included, $7,250) | $7,250 |
| Overage hours (3 hours @ $145/hr - App Store expedited review prep) | $435 |
| Apple Developer Program (annualized prorate per month) | $8.25 |
| Firebase pass-through (March 2026, dashboard attached) | $42 |
| Sentry pass-through (March 2026 team plan) | $26 |
| RevenueCat pass-through (March 2026) | $89 |
| Total due | $7,850.25 |
| Payment terms: Net 15. Auto-renews monthly unless cancelled by 15th of prior month. | - |
Notes:
- Retainer fee is constant month over month. Overages and SDK fees are the only variable.
- The "by 15th of prior month" cancellation cutoff prevents end-of-month cancellation tactics.
Mobile-Specific Pass-Through Line Items (Reference)
| Cost component | Typical billing unit | Where to source the dashboard / receipt for backup |
|---|---|---|
| Apple Developer Program | Annual fee | Apple Developer Program billing |
| Google Play Console | One-time registration | Google Play Console billing |
| Firebase (Auth, Firestore, Crashlytics) | Monthly | Firebase console billing |
| RevenueCat (in-app purchase + subscriptions) | Monthly | RevenueCat dashboard |
| Sentry / Bugsnag (crash + perf monitoring) | Monthly | Sentry / Bugsnag billing |
| Branch / AppsFlyer (deep linking + attribution) | Monthly | Branch / AppsFlyer dashboard |
| Mixpanel / Amplitude (product analytics) | Monthly | Provider billing |
| Push notification (OneSignal, Firebase Cloud Messaging) | Monthly | Provider billing |
| Beta distribution (AppCenter, TestFlight) | Monthly (TestFlight free) | Provider billing |
For any pass-through, attach the provider dashboard or invoice as PDF backup. The single most common cause of pass-through dispute is the client not believing the line-item dollar amount.
Deposit Schedule by Project Size
Per Plutio's 2026 invoice payment terms guide, deposit norms scale with project size and client trust.
| Project size | New client deposit | Established client deposit | Notes |
|---|---|---|---|
| Under $2,000 | 50% (with Due on Receipt or Net 7 terms) | 25% | Plutio explicit recommendation |
| $2,000-$10,000 | 50% with milestones | 25% with milestones | Plutio: 25-50% range with milestone billing |
| Over $10,000 | 25% with milestones | 25% with milestones | Plutio: 25% deposit recommended for large projects |
For mobile dev specifically, the deposit also covers the cost of getting set up: provisioning profiles, certificates, app identifiers, store metadata preparation, and (if you front it) the Apple Developer Program enrollment. Without a deposit, you absorb setup cost AND front the store fees on your card.
Late Fee + Kill Fee Clauses
Two clauses that should appear on every mobile dev invoice or attached MSA:
- Late fee. 1.5 percent per month on overdue balances per SolidGigs' 2026 freelance payment terms guide, or the maximum allowed by your local laws if higher. Activates the day after the due date; compounds monthly.
- Kill fee. 25 percent of remaining unpaid project value due within 14 calendar days of termination per Plutio's 2026 invoice payment terms guide. For mobile dev, this matters because mobile projects often involve store account setup, certificate management, and tooling investments that don't transfer cleanly to the next engagement.
What This Means for Sending Your Next Mobile Dev Invoice
Three takeaways for a mobile dev about to send the next invoice:
- Bill App Store / Play Store revision time explicitly. Don't absorb store rejection cycles into the engineering subtotal. They're billable work; line-item them.
- Tie milestones to TestFlight or Play Console acceptance, not calendar dates. App Store reviews legitimately delay timelines; acceptance-gate milestones survive that variance without disputes.
- Default to client-owned developer accounts. Apple Developer Program transfers are non-trivial; setting up the client to own the account from day one eliminates a handoff headache months later.
The companion rate research is in mobile app developer freelance rates 2026. The proposal format that locks scope before this invoice goes out is in mobile app developer proposal template. The general invoice fundamentals are in how to write a freelance invoice. The AI engineer invoice (similar pass-through structure for LLM/embedding/vector DB) is in AI engineer invoice template. The data engineer invoice (similar for warehouse/storage/orchestration) is in data engineer invoice template. The web-development comparison is in web developer invoice 2026. The deeper payment-terms playbook is in freelance payment terms and the late-paying-client playbook is in late-paying clients.
To send this invoice without rebuilding the line-item structure each time, use FreelanceDesk's invoice generator.