Mobile app development Your app on iOS and Android.
A custom mobile app is an iOS and Android app made for your users, linked to your back office and published in your name on the App Store and Google Play. I develop it, I handle its publication, and you test it on your own phone every week.
The signs
When a mobile app makes sense.
- 01
Your teams work in the field.
Technicians, sales reps, site managers: they enter and look up information on site, not in the evening at the office.
- 02
Your customers book, pay for or track something.
An app keeps them in touch with you, with notifications at the right moment.
- 03
Your app exists on iOS, not on Android.
Some of your users can't get to it.
- 04
Your product goes through the phone.
You are launching a service, and your users expect it in their pocket.
An app isn't always necessary. If a well-made website meets the need, I will tell you: it is cheaper to build and to maintain.
Healthcare app, intervention management, booking: the sector does not change the method, but sensitive data is scoped from the start (hosting, access, retention).
What you get
A published app that doesn't break with every update.
- 01
Published in your name.
I prepare the store listings, handle the submission to Apple and Google, and answer their feedback. The app sits under your own developer account.
- 02
Android or iOS, without starting over.
An app that exists on one system only can be ported to the other, natively if your field requires it.
- 03
Nothing sensitive on the phone.
Secure sign-in, PIN or biometrics, no data stored on the device when your field requires it.
- 04
One point of contact.
The same person designs the app, the server and the admin tool.
Native or cross-platform?
| Approach | Principle | When to choose it |
|---|---|---|
| Cross-platform | A single codebase for iOS and Android (Flutter, React Native with Expo). | Most business and consumer apps: one budget, two stores. |
| Native | One codebase per platform (Swift for iOS, Kotlin for Android). | Strong security or phone-integration requirements, or an existing app to port. |
I recommend one or the other during scoping, based on your need, not on my preferences.
How it works
You test each version on your phone.
30 minutes
Call
Who will use the app, and what for.
One week
Scoping
The screens, the flows, the rules and the link with your back office, and a fixed price.
Every week
Build
A test version on your phone (TestFlight on iPhone, internal testing on Google Play).
Then
Publishing
I check every version before it goes to Apple and Google, and I handle the submission.
What it costs
The price of your app, with no surprises.
Scoping
€1,900 excl. VAT
One week. Deducted if you continue.
Build
€11,900 excl. VAT · per month
€11,900 a month excl. VAT, or €6,500 excl. VAT for two weeks for a short project. The number of months is estimated during scoping and written into the quote.
Care
From €250 excl. VAT · per month
Apple and Google change their systems every year: your app has to keep up. Maintenance in detail →
What changes the price
What makes the price vary
The number of screens and user profiles, the back office to build or to connect, and the choice between native and cross-platform.
Paid directly by you
- Apple: US$99 a year
- Google Play: US$25, one-off
- Server hosting, in your name
Frequently asked questions
Before you get started.
Do I need two apps, one for iOS and one for Android?
Not necessarily. With Flutter or React Native, a single codebase serves both platforms, which lowers the cost. Native makes sense for particular security or integration needs.
Who publishes the app, and in whose name?
I handle the submission, but the app is published under your Apple and Google developer account. It belongs to you, like the code and the access.
How long does it take?
A few weeks for a first published version. Longer if the back office has to be built. The schedule is set during scoping. To test an idea quickly, see the first version (MVP).
Can you take over an existing mobile app?
Yes. I start with a review of the code, to know what to keep, then I stabilise it before building on it. See app rescue.
Let's talk about your app.
A 30-minute call to describe your project and find out whether you need an app, and which one. You talk directly to the person who will build it.