Mickael Romaniello
30 minutes, no slides, nothing to prepare.
Mickael Romaniello
30 minutes, no slides, nothing to prepare.
12 years of experience. 15+ apps delivered. One single point of contact, from concept to publication.
In short: for your Sydney (5,312,163 residents) project in New South Wales, you work directly with me, not a middleman. 12 years of experience, 15+ apps delivered, and a transparent end-to-end process.
Publishing an app is most the work. Maintaining it is the remaining a large share.
Most businesses in Sydney celebrate their app launch on the stores.
And then? Nothing.
The code slowly rots. Nobody watches the crash reports. Nobody anticipates when a new version of iOS or Android changes the rules.
The app that was supposed to scale your business becomes a massive liability.
Let's look at reality.
You just bought a brand new car. If you never change the oil, the engine will seize in two years. For a mobile application, it is exactly the same concept.
The hidden cost of inaction is invisible at first, but it hits hard. Users hate broken software.
There is no single type of maintenance, but three distinct pillars. Each plays a crucial role in the survival of your project in Sydney.
If you ignore these three pillars, the punishment from the market is immediate.
The key point: without corrective maintenance, you lose user trust (a large uninstall after a technical bug). Without adaptive maintenance, your app eventually disappears from the stores. And without evolutive maintenance, your competitors in Sydney simply overtake you.
A mobile application is a living digital product. The moment you stop taking care of it, technical debt accumulates. It is like termites in a wooden house. At first, you see nothing. Eventually, everything collapses.
Over 15 applications delivered. Startups that found their market fit. SMBs that streamlined their workflow.
In 12 years, I've seen what works and what crashes on iOS and Android. From Cannes, I won't promise you the moon. I promise you results. My job is to build solid tools that your users will actually adopt.
The key advantage is the real-world impact of your application. Shall we look together at how to grow your project in a smart and profitable way?
You are launching your project in Sydney.
And you are probably wondering who to work with to build your mobile app.
It is the first major decision you have to make. Some people think that to succeed, you absolutely need a big agency right around the corner. Others believe they should outsource to the cheapest team they can find overseas.
Both options come with serious tradeoffs.
A big agency will assign your project to a junior developer you have never met. An offshore team will deliver code you cannot read, three weeks behind schedule, with zero accountability.
The most important factor in the success of an app is not just the code. It is communication.
When you work with me, you get one dedicated expert with 12 years of experience and over 15 delivered projects. Not an account manager. Not a rotating team. One person who knows your project inside out.
Sydney is eight to ten hours ahead of me depending on which side of the daylight-saving switch we are on — and since Australia and Europe change clocks in opposite directions, the gap moves twice a year. Either way our working days barely touch. That suits a build with clear milestones and badly suits one that needs daily conversation. I will say which of the two your project is before we start rather than after, because the wrong answer wastes a month for both of us.
When it does suit, it works well. You finish your day and send comments; I pick them up as my day starts and work while you sleep; there is a new version waiting when you sit down. The requirement is that each week has a deliverable you can actually review on your own device, not a demonstration you have to watch me give. If a project cannot be broken into pieces like that, the timezone will fight it every week.
There is a practical Australian point that catches people from Europe: the App Store and Play Store treat Australia as its own storefront, with its own pricing, its own tax handling and its own review of anything region-specific. If you plan to sell beyond Australia, deciding that early matters, because pricing tiers and currency handling are easier to design in than to add. Storing amounts with an explicit currency instead of assuming one costs nothing at the start.
The last thing is scheduling the few conversations that do need to be live. Late afternoon for you is early morning for me, or the reverse, and both are workable if fixed in advance rather than arranged ad hoc each time. One reliable weekly slot beats four improvised attempts, and it removes the quiet drift that kills long-distance projects — the week where nobody quite got around to asking the question that was blocking everything.
An app can be built fast and cheap. What costs money is what comes next: code written without structure becomes impossible to change, and the smallest new feature means starting over. Invent Better charges for the work that makes a second version possible — tests, a readable architecture, and code another developer can pick up.
It is entirely possible to build a mobile application extremely fast and for very little money.
All you have to do is ignore every best practice, copy and paste random blocks of code from the internet, and cross your fingers hoping it holds together. On the day of your big presentation in Sydney, the app will probably look fine.
But that thin layer of paint will crack almost immediately.
The second you get more than ten users trying to log in at the same time, the system will crawl to a halt. On mobile devices, user patience is brutally short. And slowness is always perceived as a broken product.
What happens when your application completely crashes on a Tuesday morning? With a proper maintenance plan, the emergency response is codified and radically efficient for your business in Sydney.
T+0 (The Alert): The monitoring probes detect an abnormal spike in crashes. I receive an immediate notification directly on my phone. You have not even opened your morning emails yet.
T+30min (The Diagnosis): I dive into the code. Is the problem coming from our app? From an external server that went down? From an unexpected iOS update? I isolate the root cause.
T+2h to 24h (The Fix): I write the technical solution. A bug blocking checkout payments is fixed the exact same day. A minor visual glitch will be scheduled for the next business day.
T+24h to 48h (The Deployment): The hotfix update is pushed to the stores. Google usually validates very quickly; Apple takes between 24 hours and a few days depending on review loads.
A year ago, a local company from New South Wales contacted me in a panic. Their mobile app was crashing several times a day. Their store rating had plummeted. Negative reviews were pouring in, and the CEO was seriously considering shutting down the entire project.
Let's look at the facts.
I requested access to the code for a full one-week technical audit. The user interface was actually quite good, and the core idea was solid. The problem came from the foundations: deprecated libraries and terrible memory management.
I did not propose rebuilding from scratch. It was completely unnecessary.
I simply rewrote the critical most the codebase: the authentication flow and the checkout process. I hooked up Crashlytics to monitor what was happening live. I added robust automated tests to protect these specific user journeys.
I do not quote maintenance without looking at the app first, because technical debt and traffic differ in every case. So I work in levels. The essential level covers monitoring, critical bug fixes, and keeping the app compatible with each new iOS and Android release. Higher levels add feature work on a predictable monthly basis.
I do not provide cookie-cutter quotes without seeing the patient first. Every app in Sydney is unique, has different technical debt, and handles different traffic volumes. But here is how I structure my service levels.
The Essential level: This is life support. I provide 24/7 monitoring, fix critical blocking bugs, and ensure ongoing compatibility with new iOS and Android versions. Your app stays alive, functional, and compliant with store rules. It is your basic insurance policy.
Every industry has its own technical emergencies. Maintaining an e-commerce app requires completely different reflexes than maintaining a medical platform in Sydney.
There is absolutely no room for error. GDPR and HIPAA compliance audits must be constantly anticipated. Patient data security requires regular penetration testing to ensure the backend architecture remains bulletproof. I also actively maintain vital features like offline modes, which are essential for rural practitioners traveling across New South Wales.
The rhythm is highly seasonal. The goal is to have a flawless, stress-tested application ready right before the summer or winter peaks in Sydney. Maintenance focuses heavily on offline mode reliability (for foreign tourists without cellular data) and the real-time synchronization of booking databases. A crashing app in the middle of August is disastrous.
Not always, which is good news for the budget. An app that only handles its own user's data — a list, a tracker, a calculation — can keep everything on the phone and cost nothing to run. As soon as data has to be shared between people, synced across two devices, or seen by you on your side, a server is needed, and that is a cost that comes back every month.
It depends entirely on what was decided at the start, and it is one of the few choices that cannot be postponed. An app can keep its data on the device, let people work, then sync as soon as the network returns — with nobody pressing anything. It is essential the moment work happens in a warehouse, a basement, or on the road. Added afterwards, it often means rewriting half the app.
We pick a floor, and that choice has a price. Supporting older OS versions means more testing and giving up some capabilities. We look at who your users are: a consumer app and an internal tool deployed on a known fleet do not get the same answer. The floor can be raised later, when usage data shows nobody is left behind it.
It matters more than people think, because a heavy app is the first uninstalled when storage runs short. The weight rarely comes from the code: it is the bundled images and fonts. Loading images from the server rather than shipping them, and serving them at the right size, often halves it. That is invisible work, and it is the work that keeps the app installed.
Technically, sending costs almost nothing. What costs is everything around it: a server to decide what to send to whom and when, and enough care not to become intrusive. It is also the easiest mechanism to waste — a useless notification is the first cause of uninstalls, and an uninstalled app does not come back. Send few and make them useful, or send none.
Yes, with the user's permission, and how you ask matters as much as the feature. A permission demanded on first launch, with no context, is refused most of the time — and once refused it is painful to recover. Asked at the moment the person understands why, it is granted. Apple also requires a written explanation for every permission, and a vague one gets the app rejected.
Through the stores, and not instantly: Apple and Google review every version before it is published, and phones update at the pace of their own settings. So expect a share of your users to stay on an older version for weeks. That is why the server has to keep talking to previous versions, and why we avoid changes that break everything at once.
Often yes, and it all hangs on one thing: does your vendor provide a documented API. If they do, it is ordinary work. If they do not, or bill it per module, or refuse to open it to a third party, no app will work around that cleanly — workarounds exist and break at the vendor's next update. It is a question to put to your supplier before you put yours to me.
A website can be installed on the home screen, work offline and launch full-screen, with no store involved. It is a real third answer, and it is under-recommended because it earns less for whoever recommends it. Its limits: notifications stay restricted on iPhone, sensor access is partial, and you are not present in the stores — which matters if your customers look for you there.
Only if you have an audience in another language — and then it has to be designed in, not added on. Translation is not what costs; room is. German makes labels half again as long and overflows buttons drawn for English. Leaving room from the start costs nothing; redoing the screens afterwards costs days. The legal texts and the store listing count too.
While you hesitate, your competitors in Sydney are moving forward.
The mobile world moves fast. Very fast. Today, most global web traffic comes from mobile devices. If you keep pushing back the creation of your app, someone else will happily take your spot in New South Wales.
But be careful, do not confuse speed with haste. Launching an unstable application is the worst possible strategy.
In short: you have to act fast, but above all, you have to do it right. ⏳
In 30 minutes, you will know exactly where to start. No commitment. No technical jargon.
Book a free call →
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.
Once we are working together, travelling to meet you on site can absolutely be arranged if your project calls for it. Travel costs are quoted separately, upfront and with no surprises.