One codebase. Both app stores.
iOS and Android from one codebase, built with Expo and React Native, so you pay for one build. I submit it to both stores, and the accounts stay yours.
| What you buy | From | Usual time |
|---|---|---|
| AppiOS and Android from one codebase, in the stores | €32k | 6–10 weeks |
Week one is a fixed fee of €3,000, counted toward the project. Stop at the end of it and I refund it in full. Prices excl. VAT.
Scope
What you get, and what you don’t.
Included
- Design and build for iOS and Android, from one codebase
- Sign-in, the core flow and push notifications
- App Store and Google Play submission, with the listings and screenshots
- Crash reporting and analytics, set up before launch
- A test build on your own phone every week
- The code in your repository and the store accounts in your name
Not included
- Apple’s and Google’s developer fees. The accounts are yours, so the fees are too.
- A backend beyond what the app needs. Larger systems are product work.
- Games, AR, or anything that needs fully native code
- How long store review takes. Apple and Google decide that.
Anything under “Not included” can be added, except the last one. It changes the quote, and you see the new number before I start.
Price
What moves the price.
Moves the price up
- Offline use and sync
- Payments and subscriptions
- A web app alongside it
- Bluetooth or other hardware
Keeps it at the from-price
- An API that already exists
- One language
- Following each platform’s conventions instead of fighting them
The problem
You need an app. You don’t need two teams.
Mobile, without hiring a mobile team.
It starts with users asking for it, or a pilot customer who needs it on a phone. Then the quotes come in, and they assume two builds, one for iOS and one for Android, and most of a year.
For most products that is the wrong shape. One codebase can ship to both stores, and one person can own the design and the code, so the app you approve is the app that ships.
Sometimes an app is the wrong answer altogether. If people use the thing at a desk, or only now and then, a web app costs less and reaches everyone. I’ll say so on the call.
The numbers
The usual route is long. Here is one public number.
Public benchmark
11 months
is the average length of an app project reviewed on Clutch, at an average cost of $90,780.
Source: Clutch, Cost to build a mobile app (opens in a new tab), 2026. Reviewed projects of every size, page updated September 2026. A public benchmark, given as context. It covers projects of every size, so it is not a comparison with this scope, and not a promise.
Proof
The proof today, stated plainly.
Here is the honest state of it. I have built and shipped product software, including the clinic platform above, which runs in a browser, and the websites in my case studies. I have not yet shipped a client’s app to the App Store or Google Play under web0.
If that is a deal-breaker, it should be. If it isn’t, week one is where you find out: you get the scope in writing and the main flow as real screens, on your own phone, before you owe anything more.
Week one
Hire me for a week first.
Fixed feeFive working days
Week one
€3,000counts toward your project
Refundable
If you stop on day fiveWeek one is a product of its own: five working days for a fixed €3,000, counted toward the project. You get the scope in writing, real screens and a live link. Then you decide.
- Day 1The scope, in writing
- Day 2First real screens
- Day 3A live link
- Day 4Your notes, my changes
- Day 5You decide
Stop at the end of week one and I refund it in full.
Questions
Questions people ask before the call.
Yes. I prepare the listings, screenshots and privacy answers, submit to both stores and handle the back-and-forth with review. The developer accounts are yours, so the app is too.
Cross-platform, with Expo and React Native, for most products: one codebase, one build to pay for, both stores. I’ll tell you if yours is the exception, such as heavy 3D, games or deep hardware access. I’d rather lose the project than build it the wrong way.
Often a web app is enough, and it costs less. An app earns its price when people open it daily, need it offline, or need notifications. If yours doesn’t, I’ll point you at the Product scope.
Apple and Google decide, and it varies. I submit early, so review runs inside the timeline and not after it.
The two developer accounts, hosting for the backend, and any services the app uses. They are in your name and billed to you. I list them, with what each costs, in the week-one scope.
Week one is the first week of the project, sold as its own sprint: a fixed fee of €3,000, counted toward the project. Stop at the end of it and I refund it in full. The work from that week stays with me.
You do, once it’s paid. Week one’s work becomes yours when you carry on; stop in week one and it stays with me, and you get the fee back. After that, each stage’s work and its IP are yours once that stage is paid, and I keep no rights to them. I treat your business information as confidential and can sign an NDA.
Your choice. Your team can take it over, since everything is documented and already in your accounts. Or I stay on with a Marathon retainer for improvements, new features and support, from €7.5k a month.
Yes. You talk to me and I do the design and the code. No account managers, no handoffs, no juniors learning on your project.
Promises
Four promises, in writing.
Fixed price
No overrunsThe price on the quote is the price. If I underestimated, that is my cost.
Staged payments
Stop after any stageYou pay per stage and can stop after any stage.
Week one
Refunded if you stopWeek one is a fixed fee of €3,000, counted toward the project. Stop at the end of it and I refund it in full.
Revisions
Until you sign offChanges inside the agreed scope of a stage are included until you sign it off.
An app starts at €32k. Week one costs €3,000, and you get it back if you stop there.