Web app or mobile app, or both? How to choose

You are about to have a business application built: a tool to track your cases, your field jobs or your orders. One question comes up very quickly: web app, mobile app, or both? The choice affects your initial budget, your teams’ day-to-day work and the cost of maintenance for years to come.

There is no one-size-fits-all answer, but there are good criteria. Here are the ones we apply in our custom software projects to decide whether you need a web app or a mobile app, native or cross-platform, backed up by a real example.

Web, native, cross-platform: three ways to build a business application

• A web app opens in a browser, on a computer, tablet or phone. When it is well designed, it adapts to every screen size. There is only one version to develop, nothing to install, and every update reaches everyone at the same time.
• A native app is developed specifically for each operating system: one for iOS, one for Android. It makes the most of the phone, but it requires two separate builds, published on the App Store and on Google Play.
• A cross-platform app starts from a single codebase to produce the iOS and Android versions, and sometimes the web and desktop versions too. Proven technologies such as Flutter or React Native make this possible.

There is also a middle way: the PWA (progressive web app). It is a web app that can be added to the home screen, work partly offline and send notifications. What it can do varies from one system to another, however, especially on the iPhone.

Six criteria for choosing between web and mobile

1. Where your users work

At the office, in front of a large screen, entering lots of data and working through detailed tables? That is where the web excels. On a building site, at a customer’s premises, in a warehouse or between two appointments? The phone becomes the main tool, and the interface has to come down to a few quick actions that can be done with one hand.

2. Working offline

Basements, rural areas, warehouses, journeys: if your teams have to work without a signal, this criterion carries a lot of weight. A mobile app can save entries on the device, then sync them as soon as the connection comes back. Conflicts then have to be planned for: what happens if two people edit the same record, one of them offline?

3. Phone features

Photographing a document, scanning a barcode, recording where a job takes place, logging in with a fingerprint or face, receiving reliable notifications, talking to a device over Bluetooth: the more your work relies on these features, the stronger the case for mobile. The browser handles some of them, such as the camera or location, but not all, and not the same way everywhere.

4. Distribution

A web app is shared with a simple link. A mobile app goes through the app stores, with their rules and a review before every release. For a tool reserved for your teams, private distribution options exist, often tied to how the company manages its phones. For your customers, on the other hand, being in the stores can be an asset: your icon stays on their phone.

5. The initial budget

Every platform has a cost. A web app on its own is a single build; two native apps add two more. Cross-platform narrows the gap by sharing most of the mobile code, but each platform still has its share of design, testing on many devices and releases to manage. We go into these factors in our article on what custom software costs.

6. Long-term maintenance

This criterion is often forgotten. iOS and Android change every year, and the app stores regularly raise their requirements: a mobile app has to keep up, or its updates may be rejected. And since your users don’t all have the same version installed, you have to stay compatible or force the update. A web app needs upkeep too, but it only exists in one version: the one on the server.

Web app or mobile app: which to choose, and when?

The web: the right starting point

For many business applications, a well-designed web app is enough, at least to start with, when:

• your users mostly work at the office, or have a reliable connection;
• the tool is used to look up information, enter data and manage the work, without using the phone’s features;
• you want to deliver quickly, on a controlled budget, and improve the tool regularly;
• your users are numerous, change often or are outside the company: a link is all it takes to give them access.

It is also the natural route for customer portals and software sold by subscription: here is how to launch a SaaS, from the idea to the first subscribers.

Mobile, when field work demands it

A mobile app is justified when several criteria add up: work on the move, areas with no signal, phone features at the heart of the job, or customers who use your service every day and expect an app.

Native or cross-platform?

For most business applications (forms, lists, photos, signatures, notifications), cross-platform strikes a good balance: a single codebase for iOS and Android, so less development and shared maintenance, with a difference users rarely notice. Native is still preferable for specialised needs: very demanding performance, the very latest system features, or intensive use of the hardware such as video or augmented reality.

Doing both without building everything twice

Often, the right answer is “both”: a web app for the office and administration, a mobile app for the field. The key is not to build two pieces of software. All the versions rest on the same core:

• a single database, so that everyone sees the same information;
• a single application programming interface (API), which holds the business rules and which every app calls;
• the same access rights, defined once according to each person’s role.

Each app then becomes a way in suited to its context: complete on a computer, pared down to the essentials on a phone.

A real example: a law firm, on desktop and mobile

In Sydney, a law firm wanted a single, secure tool to manage its cases, clients and documents, both at the office and on the move. Our founder, Anass Chabbab, led this project as IT director at DIGIIT Solutions: a custom CRM/ERP available on desktop, iOS and Android, with role-based access and automatically generated documents.

A first version was in use in under six months. The tool was adopted by more than 100 users and cut processing time by 40%. It is the “both” scenario in its most complete form: one piece of software, present in every work situation. Read the full case study.

Checklist: seven questions to settle before you decide

1. Where are your users when they use the tool: at the office, in the field, at home?
2. Do they need to work without a signal, and for how long?
3. Which phone features are essential: camera, scanning, location, notifications?
4. Who are the users: your teams, your customers, the general public?
5. On which devices: company-issued phones, or personal ones?
6. What budget for the first version, and for maintenance each year?
7. Who will keep the app running in three years’ time, and with what skills?

If most of the answers bring you back to the office and a reliable connection, start with the web. If field work dominates, plan for mobile from the first version.

Frequently asked questions

Can a web app work offline?

Partly. A progressive web app can store pages and data on the device, and hold entries until the connection returns. For long, frequent offline work with a lot of data or photos, a mobile app is still more reliable.

Can we start with the web and add mobile later?

Yes, if the application is built from the start around an API that holds the business rules. The mobile app then plugs into it, without rewriting the core of the software. It is often the safest route: prove the tool on the web, then invest in mobile for the uses that call for it.

In short

The right choice follows from how the tool will be used, not from the technology in fashion. A web app covers many business needs on a controlled budget. Mobile becomes the obvious choice with field work, offline work and phone features. And when you need both, a shared core saves you from paying for everything twice.

Not sure which way to go with your project? Book a free 30-minute discovery call: we review how the tool will be used and recommend the simplest combination that meets those needs.