Having an app built: web app, mobile app or PWA?

The short answer

For most business tools, such as a customer portal, a planning tool, a quoting module or an internal dashboard, a web application is the best start. It works on computer, tablet and phone, needs no installation and is easier to maintain. Choose a true mobile app if your users rely on it daily on their phone and you need features such as push notifications, the camera, location or offline use.

The three types side by side

When a web application is the best choice

• Your team or customers mainly work on a computer, as with an admin, planning or quoting tool.
• You want to replace a spreadsheet or paper process with one central environment.
• Users log in to view, enter or approve data.
• You want to start quickly and grow the app based on feedback.

When a mobile app makes sense

• Field staff record work, photos or signatures on their phone.
• You want to reach customers actively with push notifications, for example about an appointment or an order.
• The app must work without an internet connection, such as in a warehouse or on a building site.
• A presence in the App Store or Google Play matters for your brand or sales.

How an app project works

1. Intake: what problem are we solving, for whom, and how does it work today?
2. Scoping: a list of screens, user roles and features, with a clear first version.
3. Design: sketches or clickable screens of the key steps, so you can give feedback early.
4. Development in phases: the core first, then extensions. You test along the way.
5. Launch and follow-up: hosting, security, backups and improvements based on real use.

What determines the price of an app?

There is no standard price for an app, because every application has different screens and rules. The biggest factors are the number of screens and steps, the number of user roles each with their own permissions, integrations with existing software such as accounting or a CRM, and whether the app must appear in the app stores. Also budget for recurring costs for hosting, security and maintenance.

A common mistake is wanting to build everything at once. A smaller first version that solves the main problem is in use sooner, costs less and produces insights that make the next steps better.

Common mistakes when having an app built

• Starting without a clear description of the problem and the users.
• Trying to fit every wish into the first version.
• Choosing a mobile app where a web app would do, which costs more and is slower to update.
• Making no agreements about ownership of the code, the data and maintenance.
• Forgetting that users need guidance to adopt the new way of working.

How we help

At Minds on Web we build web applications, customer portals and mobile apps on a strong technical foundation backed by the Techminds engineering team. We always start with a free introductory conversation to map out the problem and the users. You then get a clear list of features and screens and a fixed quote upfront, so you know what the first version includes. Apps and custom work are always quoted individually, because every application is different.