Mickael Romaniello
30 minutes, no slides, nothing to prepare.
Mickael Romaniello
30 minutes, no slides, nothing to prepare.
You have an app project. The first half hour is for finding out whether it holds up — not for selling it to you.
30 minutes, no slides, nothing to prepare.
Already have an app? I take it over: bugs, performance, getting it back on the stores.
Mickael Romaniello
Developer · Cannes · building mobile apps since 2013
Companies I have built for
Some of the clients I have built for since 2013.
What they said about it
Translated from the original French.
Mickael is an experienced developer with solid expertise in mobile development. He has offered quality support for many years.
The work was carried out with great professionalism. The developer understood the stakes of the Shokaze project perfectly and turned them into concrete, effective and well-thought-out solutions.
Reliable and responsive, Mickael guided us through our mobile app project. I recommend him!
Twelve years. Fifteen apps delivered. Both stores. And zero lock-in: the code is yours, documented, from the first day.
Based in Cannes, France · projects run in French and English
The key difference is this: an app earns its place on three tests, and it only takes one. If none of the three is true for you, a website is cheaper — and I will tell you so on the call.
Tick what is true for you
Mobile carries close to 60% of the world's web traffic (Statista, 2025), and France Num names it a growth lever for small businesses (France Num, 2025). But traffic is not the test.
The full test, with the question that decides on its own and the three cases where a website wins
None of the three?A website costs less — and I would have told you in thirty minutes, not in three months. One is enough.An app earns its place here.Talk it through in 30 minutes Two out of three.A strong case — one would already have been enough.Talk it through in 30 minutes All three.The clearest case there is, and the easiest to scope.Talk it through in 30 minutes
The point is this: you talk to the person who writes the code, and at the end the code is yours. iOS apps, Android apps, or both from one codebase, across five industries. Three things follow from that:
You explain the idea once. The person listening is the one who will build it, so nothing is lost being handed on.
No account manager, no ticket queue, no version of your project that only exists in someone else's notes.
You see the app running on a real device early and often, not a slideshow of what it will look like one day.
The code is yours at the end, documented, on a repository in your name. You can hire anyone to continue it.
App Store review, Play Console, privacy declarations, screenshots, the descriptions in both languages. I do that part.
And I stay after launch. The first month is when the real bugs turn up, and that is not the month to be alone.
In short: four steps, and you know at every moment which one you are in. No project of mine has ever disappeared into a tunnel for weeks with nothing to show. You get something you can open on your own phone long before the end, because an app you can hold is the only honest progress report there is.
We work out what this actually has to do, and I look hard at whoever is already doing it.
I draw every screen and you use them before a single line is written.
I build it, on real devices, and you get a version to open whenever you ask.
It goes on the stores, and I am still there the month after — which is the month it matters.
An app is never finished. iOS ships a major release every September, Android every year — and each one breaks something.
These are the six that come up on nearly every first call, answered here so you do not have to spend the call asking them. If yours is not below, ask it on the call — I would rather say "that one is not a fit for me" in thirty minutes than three weeks in.
Everything below is what I would tell you on the phone, in the same words.
Thirty minutes, no slides, and nothing to prepare. You describe what you want to build and who it is for; I ask the awkward questions — who else already does this, what happens if nobody downloads it, what the app has to do the day there is no signal. You leave knowing whether an app is the right thing at all, and I leave knowing whether I am the right person to build it. Pick a slot here. If the answer is no, you have lost half an hour and saved considerably more.
There is no price on this page, because a price given before the scoping is a made-up number — and you find that out on the day it moves. Here is how it works: the thirty-minute call is free and commits you to nothing. After it I send you a quote: one amount, with what is in it and what is not. Payment follows the length. On a project running over several months: 30% on signing, which is what starts the work, then the rest spread month by month to the end — you pay at the pace the work advances, and you see what advanced at each instalment. On a short one, of the order of a month: half up front, the balance on delivery. What moves the amount, in order: the number of screens, what has to be connected behind them — payment, health data, a system you already run — and whether the app has to work with no network. A change of scope during the build is quoted before it is done, never discovered on the invoice.
Yes, and this is often better value than a rebuild. I go through the code, the crash reports and the store reviews, and come back with what is actually causing the problem, what it would cost to fix, and — where it is true — which parts are fine and should be left alone. Plenty of apps that feel broken are one slow screen and two bad reviews away from being fine, and being told to rebuild is expensive advice.
I started in mobile in 2013, first for startups, then for larger clients. What derailed projects was almost never technical: it was the number of people between whoever had the idea and whoever wrote the code, because each step loses a little of the intent. I work with no one in between so those steps are gone — you explain it once, to the person who will build it, and they can tell you in the same breath that it will cost three extra days. The trade-off I say on the first call: I am not a team of ten. A project that has to ship on four platforms to a fixed date needs something other than me, and I would rather tell you that in thirty minutes than in the third month.
Book directly through Calendly, or use the phone number at the bottom of this page. During a project you have my number and you use it: no ticket to open, no desk to be transferred to, nobody to re-explain the context to.
Cannes, in the Alpes-Maritimes (06). It matters less than you would think — most of the work happens over a call and a shared screen, and I work with clients across France and Europe. But if you are nearby and would rather do the first meeting properly, with a coffee, say so and we will.
You have an app project. The first half hour is for finding out whether it holds up — not for selling it to you.
30 minutes, no slides, nothing to prepare.
Mickael Romaniello
Developer · Cannes · building mobile apps since 2013
Companies I have built for
Some of the clients I have built for since 2013.
What they said about it
Translated from the original French.
Mickael is an experienced developer with solid expertise in mobile development. He has offered quality support for many years.
The work was carried out with great professionalism. The developer understood the stakes of the Shokaze project perfectly and turned them into concrete, effective and well-thought-out solutions.
Reliable and responsive, Mickael guided us through our mobile app project. I recommend him!
Twelve years. Fifteen apps delivered. Both stores. And zero lock-in: the code is yours, documented, from the first day.
Based in Cannes, France · projects run in French and English
The key difference is this: an app earns its place on three tests, and it only takes one. If none of the three is true for you, a website is cheaper — and I will tell you so on the call.
Tick what is true for you
Mobile carries close to 60% of the world's web traffic (Statista, 2025), and France Num names it a growth lever for small businesses (France Num, 2025). But traffic is not the test.
The full test, with the question that decides on its own and the three cases where a website wins
None of the three?A website costs less — and I would have told you in thirty minutes, not in three months. One is enough.An app earns its place here.Talk it through in 30 minutes Two out of three.A strong case — one would already have been enough.Talk it through in 30 minutes All three.The clearest case there is, and the easiest to scope.Talk it through in 30 minutes
The point is this: you talk to the person who writes the code, and at the end the code is yours. iOS apps, Android apps, or both from one codebase, across five industries. Three things follow from that:
You explain the idea once. The person listening is the one who will build it, so nothing is lost being handed on.
No account manager, no ticket queue, no version of your project that only exists in someone else's notes.
You see the app running on a real device early and often, not a slideshow of what it will look like one day.
The code is yours at the end, documented, on a repository in your name. You can hire anyone to continue it.
App Store review, Play Console, privacy declarations, screenshots, the descriptions in both languages. I do that part.
And I stay after launch. The first month is when the real bugs turn up, and that is not the month to be alone.
In short: four steps, and you know at every moment which one you are in. No project of mine has ever disappeared into a tunnel for weeks with nothing to show. You get something you can open on your own phone long before the end, because an app you can hold is the only honest progress report there is.
We work out what this actually has to do, and I look hard at whoever is already doing it.
I draw every screen and you use them before a single line is written.
I build it, on real devices, and you get a version to open whenever you ask.
It goes on the stores, and I am still there the month after — which is the month it matters.
These are the six that come up on nearly every first call, answered here so you do not have to spend the call asking them. If yours is not below, ask it on the call — I would rather say "that one is not a fit for me" in thirty minutes than three weeks in.
Everything below is what I would tell you on the phone, in the same words.
Thirty minutes, no slides, and nothing to prepare. You describe what you want to build and who it is for; I ask the awkward questions — who else already does this, what happens if nobody downloads it, what the app has to do the day there is no signal. You leave knowing whether an app is the right thing at all, and I leave knowing whether I am the right person to build it. Pick a slot here. If the answer is no, you have lost half an hour and saved considerably more.
There is no price on this page, because a price given before the scoping is a made-up number — and you find that out on the day it moves. Here is how it works: the thirty-minute call is free and commits you to nothing. After it I send you a quote: one amount, with what is in it and what is not. Payment follows the length. On a project running over several months: 30% on signing, which is what starts the work, then the rest spread month by month to the end — you pay at the pace the work advances, and you see what advanced at each instalment. On a short one, of the order of a month: half up front, the balance on delivery. What moves the amount, in order: the number of screens, what has to be connected behind them — payment, health data, a system you already run — and whether the app has to work with no network. A change of scope during the build is quoted before it is done, never discovered on the invoice.
Yes, and this is often better value than a rebuild. I go through the code, the crash reports and the store reviews, and come back with what is actually causing the problem, what it would cost to fix, and — where it is true — which parts are fine and should be left alone. Plenty of apps that feel broken are one slow screen and two bad reviews away from being fine, and being told to rebuild is expensive advice.
I started in mobile in 2013, first for startups, then for larger clients. What derailed projects was almost never technical: it was the number of people between whoever had the idea and whoever wrote the code, because each step loses a little of the intent. I work with no one in between so those steps are gone — you explain it once, to the person who will build it, and they can tell you in the same breath that it will cost three extra days. The trade-off I say on the first call: I am not a team of ten. A project that has to ship on four platforms to a fixed date needs something other than me, and I would rather tell you that in thirty minutes than in the third month.
Book directly through Calendly, or use the phone number at the bottom of this page. During a project you have my number and you use it: no ticket to open, no desk to be transferred to, nobody to re-explain the context to.
Cannes, in the Alpes-Maritimes (06). It matters less than you would think — most of the work happens over a call and a shared screen, and I work with clients across France and Europe. But if you are nearby and would rather do the first meeting properly, with a coffee, say so and we will.
Most of my projects run remotely, and in practice that changes very little. We talk over video whenever you need to, not only at major milestones, and you can reach me with questions at any point during the project — I always answer.
You can also write to me directly on WhatsApp: same number I use every day, a French professional line that works internationally.
