Why we build web apps, not mobile-first, and when that flips

"We need an app" is usually the second sentence in a first meeting. Our usual answer surprises people: you probably need a web app first. Here's the reasoning we walk clients through, and the specific cases where we reverse it.

The browser is the platform

A modern web app runs on every device your team already owns, office desktops, warehouse laptops, the accountant's five-year-old machine, and yes, every phone, from a single codebase, updated instantly for everyone the moment you deploy. No app store review, no "please update your app" support calls, no version fragmentation. For business software, where the users are your staff and customers rather than app-store browsers, this is decisive.

Two codebases is a tax you pay forever

Native iOS + Android + a web dashboard means three implementations of every feature, three test passes for every release, three places for the same bug. For an SMB budget, that tax doesn't just slow the first version, it slows every version after it, forever. Most businesses feel this in year two, when the "simple change" quote comes back tripled.

Choose the architecture you can afford to change, not just the one you can afford to build.

When mobile-first genuinely wins

We do build native and cross-platform apps, it's one of our core services, because some jobs truly need them:

• Field operations: drivers, delivery staff and surveyors who need offline capture, GPS tracking and camera workflows that keep working in a dead zone.
• Hardware access: barcode scanners, Bluetooth devices, printers and sensors integrate more reliably natively.
• Consumer products: if your users find you through app stores and expect push-driven engagement, be where they look.

The pragmatic middle: responsive + PWA

Most of our ERP and SaaS work lands here: a responsive web app that's excellent on a phone browser, installable as a PWA for a home-screen icon and offline basics, with a focused native app added later only for the field roles that demonstrably need one. You get 90% of the mobile experience at 30% of the lifetime cost, and you can always add the native piece when the data says so.

Our rule of thumb

Start with the web unless the job involves offline field work, device hardware, or app-store discovery. When one of those appears, build a small, single-purpose mobile app for that role, not a mobile clone of your whole system. That's how we've kept 14 years of clients fast, and their costs affordable.