Do you need a mobile app, or is a web app enough?

“Should we have an app?” usually means “should we be in the app stores?” — and the answer is no more often than people expect. A well-built web app already works on every phone. A native app makes sense when it earns its place. Here's how to tell.

What a web app already does on a phone

A modern web app is responsive, fast, and installable to the home screen. Users can log in, upload photos, get email or SMS notifications, and do real work from a browser on any device. For most internal tools, portals, and dashboards, that's the whole requirement — with no app-store submission, no review delays, and one codebase to maintain.

When a native app earns its place

• Push notifications are core. Web push exists, but if timely alerts are the product, native is more reliable and what users expect.
• The camera, location, or offline use are central — not occasional.
• Home-screen presence matters for habit. If people should open it daily, an icon they installed from the store helps.
• Your audience expects it. Some products are judged by whether they're in the App Store, and that's a real consideration.
• The web product already works. The best time to add a mobile app is when there's a proven backend to plug into.

How to get both without building twice

The expensive mistake is building a web app and a mobile app as separate products with separate backends. I build them as one system with multiple front doors: a shared backend and API, a web client, and mobile clients on top. Features and data stay in sync everywhere, and adding the second platform later is an addition rather than a rebuild.

Which mobile approach fits — native SwiftUI and Kotlin, or a cross-platform wrapper around the web codebase — depends on how much the app leans on device features. I've shipped both: a national member platform with native iOS and Android clients, and a pet-care tracker delivered on the web and iOS from a single codebase. It's a discovery decision, not a default.

A sensible order

• Start with the web app, especially if the product is new. It's faster to launch and easier to change while you learn what users actually do.
• Add mobile when the case is clear: a device feature you need, an audience that expects it, or a habit you want to build.
• If you're certain from day one — a field-service tool, a consumer product built around the camera — plan both from the start so the backend is designed for it.

Not sure?

Describe how people would use it — where they are, what they're holding, how often — and I'll tell you honestly whether it needs the app store.