Native, cross platform or web: choosing how to build an app
A plain comparison of native, cross platform and web apps, covering cost, feel and maintenance so you can choose the right approach.
There are three broad ways to build an app, and the choice affects what you pay, how the app feels and how much work it is to keep alive.
Here is each option in plain terms, followed by how we would choose.
Native apps
A native app is written specifically for one platform. One version for iPhone using Apple's tools, another for Android using Google's. They are two separate pieces of software that happen to look alike.
What you get:
- The smoothest feel. Scrolling, animations and gestures behave exactly as the phone's owner expects.
- Full access to the device: camera, sensors, Bluetooth, background tasks, widgets, and new features as soon as the platform releases them.
- The best performance for demanding work such as video, maps with lots of moving parts, or games.
What it costs you:
- Two codebases. Every feature is built twice, tested twice and fixed twice.
- Often two sets of specialist developers, or one team that is stretched.
Native is the right call when the app is the business, when it depends on hardware features, or when polish is a selling point in itself.
Cross platform apps
A cross platform app is written once and packaged for both iPhone and Android. Frameworks such as React Native and Flutter are the well known names here. The result is installed from the app stores just like a native app, and most users could not tell the difference.
What you get:
- One codebase for both platforms, which generally means less work to build and to maintain.
- Access to most device features, either built in or through add ons.
- A real store presence on both platforms from one team.
What it costs you:
- A small gap in feel. With care it is barely noticeable. Without care, the app can feel slightly off on one platform or both.
- A wait, sometimes, before brand new phone features are supported.
- Reliance on the framework and its add ons staying healthy. When a phone operating system updates, you depend on those pieces catching up.
For most small business apps, things like bookings, ordering, member areas, checklists and loyalty, cross platform is a sensible default.
Web apps
A web app runs in the browser. Built well, it can be added to the home screen, work offline to a degree and feel a lot like an installed app. You may hear the term progressive web app for this.
What you get:
- One product that works on phones, tablets and computers.
- No app store approval. You publish updates whenever you like.
- Usually the lowest cost to build and maintain of the three.
- People can use it from a link, with nothing to install first.
What it costs you:
- Weaker access to some device features, with differences between iPhone and Android that shift over time.
- No automatic listing in app stores, so people cannot stumble on it there.
- Installing to the home screen is less familiar to many people.
A web app suits tools where the audience already knows you, the features are mostly forms, lists and content, and reach matters more than store presence.
How do they compare side by side?
Without quoting prices, which swing enormously with scope, the usual pattern is:
- Upfront cost: native is typically highest, cross platform in the middle, web lowest.
- Ongoing maintenance: same order. Two native apps mean two of everything. A web app means one.
- Feel and performance: native leads, cross platform is close behind, web is good for simple tasks and weaker for demanding ones.
- Device features: native has everything, cross platform has most, web has some.
- Speed of updates: web is immediate. Both store options wait for review.
- Being found: store apps appear in store searches. Web apps appear in Google.
Do not forget maintenance
Whichever you choose, the build is the start of the spending, not the end. Phone operating systems change every year. App stores update their requirements and can remove apps that fall behind. Payment and login services retire old versions. Security fixes need applying.
Ask any developer quoting on your app what a normal year of upkeep involves and who will do it. If the answer is vague, treat that as a risk. An app nobody is looking after tends to degrade quietly until the day it stops opening.
How we would choose
Work through these in order and stop at the first one that fits.
- Can it be done in a browser, for people who already know your business? Build a web app. Start here unless you have a reason not to.
- Do you need to be in the app stores, or need push notifications and device features that the web handles poorly? Go cross platform.
- Does the app rely on advanced hardware, heavy graphics or the very best feel as a competitive point? Go native, and budget for two platforms.
- Do your customers overwhelmingly use one kind of phone? A single native app for that platform can be a reasonable first step. Check your website's visitor data before assuming.
Then put two questions to whoever is quoting: why are you recommending this approach for us in particular, and what would make you recommend a different one? A good developer will have a clear answer to both.