All posts

Web app or mobile app: which should you build first?

Native app, web app or progressive web app? How to decide what to build first, based on how your customers or team will actually use it.

"Do we need an app?" is one of the first questions businesses ask. Often the real question is "do we need something people can use on their phone?", and that's a different thing.

Three options

OptionWhat it isBest for
Web appRuns in the browser on any deviceMost new products, portals and internal tools
Progressive web app (PWA)A web app that can be added to the home screen and work partly offlineProducts used often on phones, without app store hassle
Native appBuilt for iPhone and Android, installed from the app storesHeavy device features, offline use, app-store presence

Why web usually comes first

  • One codebase. It works on phones, tablets and computers.
  • No app store approval. Updates go live instantly.
  • Easier to find and share. A link is all anyone needs.
  • Faster to change. In the early days, you'll change things often.

The Kaladi Kitchens booking platform is a good example: members book kitchen time and complete checklists with photos on their phones, all through a web app, with no download required.

When native is worth it

Some products genuinely need a native app:

  • Camera, AR or sensors are central. The augmented-reality apps we built for Rupertsland Institute and Shell rely on the phone's camera and tracking in ways the browser can't match.
  • Reliable offline use. Field teams working without signal.
  • Push notifications are core to the product.
  • Your customers expect to find you in the app store.

You don't have to choose forever

Many products start as a web app, prove that people want them, then add native apps once customers ask. Built well, the web app and the native apps can share the same back end, so you're not starting again.

Common questions

Is a progressive web app as good as a native app?

For many uses it's close, and much cheaper to build and maintain. It falls short on some device features and on app-store discoverability.

Can one codebase produce both iPhone and Android apps?

Yes. Cross-platform frameworks let you build once for both, which is what we usually recommend when native is needed.

Do internal tools need a mobile app?

Rarely. Staff tools almost always work well as a web app, unless the team needs offline access in the field.

Which should we start with?

Tell us how people will use it and we'll give you a straight recommendation. Our web apps and mobile apps pages cover both in more detail.

Want this looked at for your business?

A short call, no pitch. Tell us how things run today and we'll tell you honestly what's worth doing first.