"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
| Option | What it is | Best for |
|---|---|---|
| Web app | Runs in the browser on any device | Most new products, portals and internal tools |
| Progressive web app (PWA) | A web app that can be added to the home screen and work partly offline | Products used often on phones, without app store hassle |
| Native app | Built for iPhone and Android, installed from the app stores | Heavy 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.
