Mobile app development: iOS and Android apps with a business mindset.

Making an existing website installable (PWA integration) starts from €700 + VAT, a custom PWA web application from €1,900, one with its own backend and integrations from €3,900. A cross-platform MVP starts from €7,000 + VAT, and a native or complex app from €14,000 + VAT. The final price is decided by the feature list, not the platform: after a needs assessment we give a detailed, written quote. Operations and support are available from €150 a month + VAT.

Detailed price bands: mobile app development prices 2026.

An MVP typically takes 6–12 weeks, a more complex app 3–6 months. The timeline mostly depends on how mature the spec is and how quickly approvals come through. After kickoff we schedule in milestones, so you can see exactly where the project stands throughout.

If you need two platforms fast and cost-effectively, cross-platform (Flutter or React Native) is the way to go. If you don't need an app store presence, a browser-installable PWA is the cheapest route. We recommend native development when you need hardware-level functions or outstanding performance. We don't base the decision on taste but on the feature list and budget, together with you.

For an internal company app the answer is simple: whichever platform runs on the devices in your colleagues' hands. For a consumer app your own analytics decide it, so it's worth checking what proportion of your website visitors come from iOS and Android. With cross-platform development the question mostly disappears, because the same codebase ships the version to both app stores, and the difference stays in the submission process and a handful of platform features.

For cross-platform development we use Flutter and React Native, for native development Swift (iOS) and Kotlin (Android), and we also build PWAs and backend APIs. We choose the technology to fit the task, not the other way round. The backend and operations are in-house too, so you don't need to coordinate with several companies.

Yes, we handle everything from setting up the developer accounts through the store listings to the review process. We deal with rejection risks at the design stage already, because preventing them is cheaper than resubmitting. You need to budget for the stores' own fees: Apple charges $99 a year, Google a one-off $25.

Yes, for most business applications: the users, the data and the notifications live on a server. We develop the backend API ourselves, and we can run it on our own Ubuntu VPS servers, with monitoring and daily backups. That way the app, the API and the server are all in one hand.

Yes, we build an API onto the existing system and connect the app to it. For online shops, this is a proven way to serve returning customers: push notifications, faster checkout, loyalty features. It works equally well with WShop, Magento 2 and WooCommerce based webshops.

Partly, yes, if we plan for it. Some of the data can be stored on the device, so already downloaded content can be read offline too, and data recorded in the field can also be saved for later syncing.

One thing to decide in advance: what should happen if someone else has changed the same data in the meantime. We clarify this conflict handling during the needs assessment, because building it in afterwards is expensive.

On top of the store fees (Apple $99 a year, Google a one-off $25) you need to budget for annual iOS and Android version updates and bug fixes. We take this on as a monthly operations package from €150 a month + VAT. Without it, an app quietly goes out of date within 1–2 years and can even be pulled from the store.

Yes, at project closure we hand over the complete source code and every access. There's no lock-in: the app can be taken elsewhere at any time, even to another developer. In the reverse situation, we'd expect exactly the same.

Yes, we build an MVP with a reduced feature set that works in a live environment, suitable for market validation and investor demos. The focus is on showing the core value proposition, not on perfection. The later full version builds on this foundation, nothing needs to be thrown away.

We add measurement to the app: how many installs there have been, how many people use it daily, which screen they stop on and where the flow breaks off. This isn't personal surveillance but aggregated usage data, in line with consent rules.

The store dashboards also show downloads, churn and ratings. Together these show what's worth improving in the next version.

Uploading to the store on its own doesn't bring you users. The steps worth starting with: optimising the store listing (title, keywords, screenshots, video), communicating on your own website and in your newsletter, and reaching out to your existing customer base.

For an internal company app, this question doesn't apply; there, the rollout and training matter most. For a consumer app, it's worth budgeting for advertising too, because you have to work for a download just as much as for a website visitor.

A support period follows handover, after which you can choose a monthly operations package and a development budget as needed. This includes keeping up with new OS versions, handling app store rule changes and bug fixes. We also take on one-off changes separately.

Yes, after a code audit we give you a realistic picture of its state: whether it can be continued or it's cheaper to rewrite. The audit has a fixed price and is quick; after it, you get an itemised proposal. We've already brought many projects back to life this way.

App development has several layers: besides the interface it includes the server side (backend and API), user management, push notifications and store publishing, along with the App Store and Google Play rules. A website can be updated instantly, whereas a new app version goes through store review. If the goal can also be reached from a browser, a PWA web application is a cheaper way in, and we'll tell you that during the needs assessment.

With a needs assessment and choosing the technology: we clarify the goal, the main features and whether a PWA, cross-platform or native app fits best. Then we create an interface design and a clickable prototype, so the idea can still be tested cheaply. Development proceeds in iterations, ending with testing, store publishing and measurement.

It's worth asking six questions: who builds the server side, whose name the developer accounts are registered under, how you can try out the app along the way, what happens after publishing, exactly what the price includes, and how the app connects to your existing web system. With us, the backend and operations are in-house, and the developer accounts stay in your ownership.

Yes. If the task can also be solved from a browser, a web application or a PWA is a faster and cheaper route, without store approval. Client portals, booking and back-office systems, internal company interfaces: we cover this in detail on the web application and web app development page.