Every week someone asks us to quote “an app,” and the honest first answer is usually another question: what does the phone have to do that a browser cannot?
It sounds like a technicality. It is actually the single biggest fork in the road for your budget, your timeline, and how much the thing costs to keep alive. Here is how we walk clients through it.
What a responsive web app gives you
A responsive web application is one product that adapts its layout to whatever screen it lands on: a phone in the field, a tablet at the counter, a monitor in the office. There is nothing to install, nothing to update on anyone’s device, and no app store standing between you and your users.
- One codebase. Every feature you pay for exists once, not three times.
- Instant updates. Fix a bug in the morning and everyone has the fix by lunch.
- No store review. No waiting on Apple, no rejection emails, no annual developer fees.
- Every device, day one. iPhone, Android, tablet, desktop: covered by definition.
What genuinely requires a native app
Some jobs cannot be done well in a browser, and pretending otherwise produces software people hate. A native app earns its keep when you need:
- Offline work. A crew capturing inspections in a basement with no signal needs local storage and sync, not a spinner.
- Hardware access. Barcode scanning at speed, Bluetooth peripherals, background GPS.
- Push notifications. If the product’s core loop depends on reaching users when the app is closed.
- Heavy device integration. Camera pipelines, secure enclave storage, platform share sheets.
The mistake we see most
Companies commission a native app because it feels more “real,” then spend two years paying to maintain three codebases (iOS, Android, and the web version they needed anyway) for a product whose users only ever open it at a desk. The app was a status decision, not an engineering one, and the invoice difference runs well into six figures over the software’s life.
Build responsive by default. Go native when the phone has a job only a phone can do.
A quick self-test
Answer these honestly and you mostly have your answer:
- Will people use this where there is no reliable connection?
- Does it need the camera, scanner, or GPS as a core function, not a nice-to-have?
- Is being on the user’s home screen genuinely important to how often it gets used?
Three noes? Responsive web app, and put the savings into making it excellent. Any yes? Now a native app is worth pricing, and cross-platform frameworks mean it still does not have to mean two teams.
Not sure which side your project lands on? That is exactly the kind of question our first conversation is for.
