Every startup founder I meet wants to build an app. iOS and Android, native experience, push notifications, the whole thing. When I ask why, the answer is usually some version of “because that’s what startups do.”

Here’s what they should hear instead: you probably don’t need an app. At least not yet.

The App Store Dream Is Mostly Dead

The fantasy goes like this: build an app, launch it, people discover it through the App Store, growth takes off. Except App Store discovery hasn’t worked like that since about 2012.

There are millions of apps in the App Store. The vast majority get zero downloads. Getting featured by Apple is harder than getting into Harvard. Paid acquisition is expensive and getting more expensive every year as privacy changes kill traditional tracking.

Unless you’ve got a massive marketing budget or existing distribution, nobody’s finding your app organically. You’ll need to drive people there yourself through your website, social media, email – channels that work just fine with a web app.

The Cost Is Higher Than You Think

Building a native mobile app means building it twice – once for iOS, once for Android. Even if you use React Native or Flutter to share code, you’re still dealing with two platforms, two sets of review processes, two update cycles.

Then there’s maintenance. Every time Apple or Google updates their OS, you might need to update your app. Breaking changes happen. APIs deprecate. What worked fine last year suddenly doesn’t.

Compare this to a mobile-responsive website: build once, works everywhere, updates instantly for all users without app store review delays. No installation friction. No storage space requirements. No permission requests before someone can even see what you do.

What Actually Requires an App

Don’t get me wrong – some things genuinely need native apps:

• Heavy offline functionality: If your core feature requires working without internet, you need an app.
• Hardware integration: Camera, GPS, sensors, NFC – apps have better access to these than web browsers (though the gap is narrowing).
• Performance-critical features: Games, video editing, anything requiring maximum processing power.
• Push notifications: Still the biggest reason. Though web push is getting better and works on Android Chrome.

If your startup doesn’t need these specific things, a web app is probably fine.

Progressive Web Apps Are Underrated

PWAs are the middle ground nobody talks about. They’re websites that can be installed on home screens, work offline (if designed for it), and feel surprisingly app-like.

Twitter’s PWA is actually pretty good. Same with Starbucks. These aren’t small companies cutting corners – they’ve done the math on what makes sense to build.

The main limitation is iOS, where Apple deliberately kneecaps PWA functionality to protect App Store revenue. It’s frustrating but improving slowly. On Android, PWAs work great.

When to Actually Build an App

You should build a native app when:

1. You’ve validated the business model: Don’t build expensive infrastructure before you know if anyone wants what you’re selling.

2. You have specific technical requirements: The features listed above that genuinely need native capabilities.

3. You can afford to do it properly: Half-assing a native app is worse than having a good web app. Users expect polish in native apps.

4. User engagement justifies it: If people are using your service daily, an app makes sense. If it’s monthly or less, probably not.

The Validation Problem

This is the real issue: founders want to build apps before they’ve proven anyone wants their product. An app feels “real” in a way a website doesn’t. It’s a credibility thing.

But credibility doesn’t matter if you’re building the wrong thing. Start with the cheapest way to test your hypothesis. Usually that’s a web app, maybe even just a landing page and some manual processes behind the scenes.

I know folks at Team400 who work with startups on this exact decision – the answer is almost always “not yet” on the native app question. Build the core business first.

The Instagram Exception

Someone always brings up Instagram as proof that apps are necessary. Instagram launched as an iPhone app in 2010 when the mobile ecosystem was completely different.

There was less competition, Apple featured new apps regularly, and mobile web capabilities were genuinely terrible. Instagram wouldn’t launch the same way today because the environment has changed.

Also, Instagram had to be an app – it was built around the iPhone camera. That’s the “specific technical requirement” case.

What to Build Instead

Start with a mobile-responsive website that works great on phones. This means:

• Fast loading times
• Readable text without zooming
• Touch-friendly buttons and forms
• Sensible navigation on small screens

Use modern web frameworks that handle responsive design well. Test on actual phones, not just browser dev tools. Make sure it feels smooth and native-ish.

If you need app-like features, investigate PWAs. You can get 80% of the native app experience with 20% of the development cost.

The Path Forward

Here’s the typical path for successful startups:

1. Landing page + manual processes to validate concept
2. Web app with core functionality
3. Mobile-responsive improvements based on actual usage data
4. Native app if and when the data shows it’s worth the investment

Most startups die somewhere in steps 1-2. Spending six months building native apps before you know if the business works is a good way to join them.

The Unsexy Truth

Web apps aren’t sexy. They don’t feel like “real” startups to investors or friends. You can’t say “download my app” at parties.

But they’re cheaper to build, faster to iterate, easier to maintain, and accessible to everyone with a browser. For most startups, especially pre-product-market fit, that’s what matters.

Build the app when it makes business sense, not when it makes you feel legitimate. The users don’t care how they access your service. They care whether it solves their problem.

Focus on that first. The native app can wait.