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 dedicated point of contact.
In short: mobile app development for Manchester (553,230 residents) means a project driven by a senior expert — not an agency. Direct communication, ownership of the code, published on App Store and Google Play within weeks.
You are based in Manchester and you have a mobile app idea.
It is the classic scenario. Enthusiasm is at its peak. You are already picturing your logo on everyone's home screen across England.
The journey between an idea on a napkin and a published app on the stores is long. Very long.
Spoiler: the vast majority of app projects never reach profitability. Not because the initial idea was bad, but because the execution was a mess.
How do we actually build an application in Manchester? It is not just a developer locked in a basement typing random code. It is an industrial, creative, and highly rigorous process.
If you want your project to survive in England, you must follow four major manufacturing steps.
Here is how it really happens.
The first step is concept validation. What precise problem does your application solve? For whom? You must be able to answer in a single sentence. If it is too vague, that is a bad sign. Spoiler: trying to build a Swiss Army knife is a fatal mistake. Knowing that most app features are never actually used, we are going to prune your idea to keep only the pure value.
The second step is technical architecture and design. Before building a house in Manchester, you draw blueprints. It is exactly the same here. We choose the right engine for your app, whether that is native code like Swift or Kotlin, or hybrid tech like Flutter. We design the screens following strict ergonomic rules, taking inspiration from standards like Google's Material Design. We build solid foundations before we start painting the walls.
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?
Manchester has a real developer market of its own, so anyone hiring outside it has usually decided that a small team or one person suits the project better than an agency. That tends to make for clear briefs: you already know what you are not looking for, which is half the work of scoping done before we speak.
It also means the conversation can start honestly. If your project genuinely needs four developers working in parallel to hit a fixed date, I will say so and you should hire locally or use an agency — that is a real answer, not a sales tactic. What I am good for is the other shape of project: one product, one person who holds the whole picture, and a build where the person writing the code is the person you spoke to about why it matters.
Manchester's media and e-commerce presence shows up in the kind of work I get asked about. Retail apps in particular have a trap that catches almost everyone: the app is only the visible tenth of the job. Stock levels, pricing rules, delivery options and returns all live in systems that already exist, and the mobile app has to agree with them in real time. When people tell me a shopping app should be quick to build, they are thinking of the screens, not of the fact that a price shown wrongly for an hour is a real commercial problem.
Practically, we are in the same working day: one hour of difference, so a morning question gets a morning answer. Manchester is also two hours by train from London and well connected to the continent, which matters if the project needs me in a room at the start. For most builds it does not, but for the first scoping session it is occasionally worth the trip, and I would rather do that once at the beginning than repair a misunderstanding at the end.
The economy in Manchester is evolving fast. Very fast.
Local businesses can no longer settle for a basic, aging website. Digital transformation is happening everywhere across England. And mobile devices have become the absolute center of this shift. 🚀
In short: your clients live with their phones in their hands.
It is an unavoidable reality that most global web traffic comes from mobile devices. If your business in Manchester is not easily accessible on their home screen, it is practically invisible to a massive chunk of your audience.
I help companies build this vital digital presence. Governments across United Kingdom are pushing small and medium businesses to adapt to these new consumer habits, and funding digital growth.
The observation is the same everywhere. The residents of Manchester want to order, book, or find information with a single tap, whether they are on their couch or commuting.
With Invent Better you get an installable build every two weeks, even when it is incomplete. That is the difference between following a project and waiting for one. You have access to the code repository from day one, and every decision is written down rather than remembered. A disagreement surfaces after two weeks, not at final delivery.
Software development is far too often treated as a terrifying black box.
In many traditional projects, you sign a massive specification document, you pay a hefty deposit, and then you just wait. For months, you receive nothing but vague updates. A few reassuring emails. A lot of "trust us, it is coming along great."
And then the day of the final big reveal in Manchester arrives... and your heart sinks. The product looks and feels nothing like what you envisioned. But it is entirely too late, and your budget is completely gone.
The most important factor: when you work with me, that black box simply does not exist. Everything is entirely transparent.
A project runs in four stages: scoping that decides what goes into the first version, mockups you handle before a line of code exists, development delivered in installable slices, then publication. What matters is not the number of stages but their rhythm.
Four stages, in this order:
Nothing beats a concrete example to truly understand. Here is the story of an established service company.
This business had a standard website. Their analytics showed that most their traffic was coming from mobile phones. That is a massive number. But there was a major issue. They were getting absolutely zero bookings from those devices.
Their customers were trying to book appointments, getting lost on the clunky mobile site, and giving up entirely.
The technical challenge was very real. We needed to handle a complex calendar system, secure payments, send push notification reminders, and allow multiple users to coordinate schedules.
The client wanted to build everything at once. A loyalty program, a blog, a forum, and the booking module.
I reminded them of a vital statistic: most app features are never actually used. Why spend thousands of dollars on ghost options?
There is no single price for a mobile app. What sets the amount is the scope: the number of screens, whether it needs a server and user accounts, and whether it targets one platform or two. A scoping call gives a real range.
Three factors set the budget, plus two fixed costs:
The global e-learning market grows every single year. And for good reason: students and professionals in England want to learn anywhere, at any time.
A solid mobile e-learning platform is not just a messy list of videos. It is the ability to securely download those courses to watch them on the Manchester subway without burning through a cellular data plan.
You have to add gamification, achievement badges, and streak tracking to maintain high motivation. For schools, we integrate a direct notification system for parents, ensuring that critical information flows completely without friction.
The restaurant industry has radically changed. If your restaurant in Manchester is not in your regular customers' pockets, you are missing out on massive revenue.
Forget the big delivery platforms that take huge cuts of your margin. The key advantage of having your own application is total control.
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 Manchester 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 England.
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'll know where to start. No commitment.
Book a free call →30 minutes to start
Book →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.