App development in Malta, with the backend done properly

iOS, Android and macOS apps, where I own the whole project: scoping, architecture, backend, API, admin and delivery. I either build the app or bring in a specialist mobile developer I manage. You deal with one person.

Tell me what you’re working on

From €4,000. Not ready for a project? A Technical Second Opinion is €250.

Who this is for

You have an idea for an app, or you need one for your business, and you are weighing up who to trust with it. Perhaps it is a customer app for your service, a tool for your staff, or a product you want to launch. The expensive mistake is paying for screens first and discovering later that nobody planned the accounts, data, payments and admin behind them.

Before anything else, here is how I work, so you can judge whether it suits you.

Apps are not the centre of my work. What I bring is more than 15 years building the software that apps sit on top of, and responsibility for the whole project. For the app itself, I either build it or bring in a specialist mobile developer whom I manage. You have one point of contact either way.

Maybe you do not need an app at all. If your users only need to look things up, fill in forms or check a status, a fast mobile-friendly web application can do the job for less, with no store review in the way. I will tell you if I think that is the case.

Why the backend decides most app projects

Most app projects succeed or fail on what sits behind the app, not on the screens.

  • Accounts, sign-in and password recovery.
  • Payments and subscriptions.
  • The data the app reads and writes, and who is allowed to see it.
  • An admin panel so your team can manage users, content and orders without calling a developer.
  • Integrations with your existing systems.
  • The API that connects all of it to the app.

This is the work I have done for 15 years, these days mostly with Laravel and Filament, and it is where I would put the care first. An app with a weak backend is a good-looking problem. More on that side: Laravel development and API integrations.

Typical problems I solve

  • An app idea with no clear view of what needs building behind it.
  • A mobile developer delivering screens while nobody owns the backend, the admin and the launch.
  • A web system that now needs an app, using the data you already have.
  • An app that needs to talk to payment providers, a POS, a CRM or a legacy platform.
  • Nobody to coordinate between design, mobile development, backend and store submission.

iOS, Android and macOS

iPhone and iPad apps go through the App Store, Android apps through Google Play, and Mac desktop apps suit internal tools or products.

Many projects need only one platform first. If your users are mostly on iPhones, start there and add Android later, rather than paying for both before you know the idea works.

Native or cross-platform

This is a real trade-off, not a matter of taste.

Native means building separately for each platform in its own tools. You get the best performance, full access to device features and a polished platform feel. You also pay for two codebases if you need both platforms.

Cross-platform means one codebase for both. It is usually cheaper and quicker, and it suits most business apps with standard screens, forms, lists and notifications. It can get awkward with heavy graphics, unusual hardware access or very specific platform behaviour.

My default for a business app on a sensible budget is to look hard at cross-platform first, and go native when there is a clear reason. I would rather tell you that than sell you the more expensive option.

App store submission

Submitting an app is its own piece of work, and it catches people out.

  • Both stores require developer accounts, and the Apple one in particular takes time to set up.
  • Review can reject an app for reasons that are easy to fix but slow to discover late.
  • Privacy declarations must match what the app actually does with data.
  • Apps with accounts need clear ways to manage or delete them.
  • Payments inside an app may be subject to store rules and fees.

I plan for this from the start and handle the submission as part of the project, so launch day is not the first time anyone reads the rules. The stores’ own guidelines change, so I check them against your app rather than rely on memory.

Maintenance after launch

An app is never finished at launch. New iOS and Android versions arrive every year, store requirements change, and users find things you did not expect.

We agree upfront how that will be handled: who fixes bugs, who updates the app for new operating systems, and how new features are scoped. I can stay on for ongoing work or hand over cleanly to your own team.

How a project works with me

First I ask who the users are, what they need to do, and what systems it must connect to. Then I come back with a recommended approach: which platforms first, native or cross-platform, what the backend needs, and who builds what. If a specialist mobile developer is the right choice, I will say so and manage them for you.

Why work directly with me

I am an independent senior engineer. The person you speak to is the person who builds it, or who manages the specialist who does. There is no agency layer, no account manager and no junior handoff. One person scopes the work, decides the architecture, and is accountable for the result.

Already have developers?

If you have a mobile developer or an agency building the app, I can look after the backend and API, review the architecture, or act as a second pair of eyes. See working with me.

Relevant experience

My experience is in the systems behind products: architecture, APIs, integrations, admin tools and delivery, across clients such as TripX and Uniify. You can read about that on the work page, and about the wider custom software side. None of it is app work, and I would rather say so plainly.

Pricing

App projects start from €4,000. That figure covers a small, well-scoped project. A typical app with accounts, a backend, an admin panel, integrations and store submission costs more, and the specialist mobile developer, where needed, is part of the estimate. I will give you a written range once I understand the scope.

If you are unsure whether the idea is ready, or whether to build native or cross-platform, a Technical Second Opinion is a cautious first step.

Or send me the idea as it is. A few lines are enough. You do not need wireframes, a specification or a decision on platforms first.

Questions people ask

Do you have apps in the App Store?

No. Apps are not the centre of my work, and I won’t pretend otherwise. What I bring is 15+ years building the systems apps depend on, and ownership of the whole project, including a specialist mobile developer when the app itself needs one.

Should I build native or cross-platform?

Cross-platform is usually enough for a business app with standard screens and a tighter budget. Native makes sense when you need the best performance, deep device features, or a very polished platform feel. I will recommend based on your app, not on habit.

How much does an app cost in Malta?

Projects start from €4,000. A real app also needs a backend, accounts, an admin panel and store submission, so the total depends on scope. I give a written estimate once I understand what it needs to do.

Do you handle App Store and Google Play submission?

Yes, as part of the project. Both stores have review rules, privacy declarations and account requirements that can delay launch if left to the end, so we plan for them from the start.

What happens after the app launches?

Apps need ongoing work: operating system updates, store policy changes, bug fixes and new features. We agree how that will be handled before launch, so it is not a surprise later.

Tell me about the app idea

Send me a few lines about what the app should do. You don’t need wireframes or a finished specification to start the conversation.

You don’t need to know exactly what you need. Just describe the problem. Links to screenshots or docs are welcome.

Used only to reply to you. See the privacy policy.