A lot of founders walk into their first product conversation assuming they need a native mobile app, because that's what "looking legitimate" seems to require. That assumption is rarely true on day one, and betting your early runway on it is one of the more expensive mistakes we see.
The case for web first
The case for building web first is mostly about speed of learning. You can iterate faster without app store review cycles standing between you and your users. You can share a link for early user testing instead of asking someone to install something. And for most B2B products and anything content-heavy, the browser is simply where your users already are — there's no real friction you're removing by going native first.
The case for mobile first
The case for mobile first is narrower but real. If push notifications or camera and location access are core to how the product works — not a feature you'd like to add, but the actual mechanism of the product — that points toward mobile. If offline usage is a hard requirement, not a nice-to-have, that points toward mobile. And if your target audience is a consumer group that genuinely lives in an app store and expects high-frequency daily use, that's a legitimate reason to start there.
The middle path: PWA first
There's a middle path we recommend more often than either extreme: a well-built responsive web app first, wrapped in a minimal store presence once you have real traction to justify it, rather than committing to two codebases before you know if either one is needed. This avoids the most expensive version of getting it wrong — building and maintaining two separate apps for a product that hasn't yet proven anyone wants version one.
Signals to watch before committing to native
The signals worth watching before committing to native mobile: engagement and retention numbers from your web version, and — importantly — actual support requests specifically asking for an app, not a hypothetical assumption that users want one. If people are using your web product daily from their phone's browser already, that's a much stronger signal than a founder's gut feeling.
Treat mobile as a decision you earn with usage data, not a checkbox you tick to look credible to investors or early customers. The apps that succeed are the ones built because the data demanded them, not because the roadmap said it was time.
Making the call
If you're trying to figure out where to start — web, mobile, or both — that's exactly the kind of product-scoping conversation our team has with founders before any design or engineering work begins. Reach out through our contact page and we'll help you think it through.