"We need an app."
But do you need an app that lives on the App Store? Or is a mobile-friendly website enough? The answer matters — it affects cost, timeline, and maintenance forever.
The Options
Native Mobile App
Apps built specifically for iOS (iPhones/iPads) and Android. Downloaded from App Store or Google Play.
Examples: Instagram, banking apps, games
Web App (Mobile-Friendly Website)
A website that works well on mobile browsers. No download required.
Examples: Most e-commerce sites, news sites, many business tools
Progressive Web App (PWA)
A hybrid — a web app that can be "installed" on a phone's home screen and work offline. Lives between native apps and websites.
Examples: Twitter Lite, Starbucks PWA
Cross-Platform Mobile App
One codebase that compiles to both iOS and Android. Built with tools like React Native or Flutter.
Examples: Many startup apps, Facebook's ads manager
When Native Mobile Apps Win
Hardware Access
Need the camera, GPS, accelerometer, Bluetooth, or other phone sensors?
Native apps have full access. Web apps have limited access.
Performance-Intensive
Games, video editing, complex animations, real-time graphics.
Native apps perform better for demanding tasks.
Offline Functionality
Need to work without internet? Process transactions offline and sync later?
Native apps handle offline better (though PWAs are catching up).
Push Notifications
Want to send notifications even when the app isn't open?
Native apps do this well. Web apps can (PWA), but it's more limited.
App Store Presence
Being discoverable in the App Store/Google Play matters for some businesses.
Consumer apps benefit from store presence and reviews.
Platform Integrations
Need Siri shortcuts, Apple Watch integration, home screen widgets?
Only native apps can fully integrate with platform features.
When Web Apps Win
Broad Accessibility
Everyone with a browser can use it immediately. No download.
Lower barrier to entry means more users.
Cross-Platform by Default
Build once, works everywhere — phones, tablets, desktops.
Instant Updates
Push an update, and everyone gets it immediately.
No waiting for app store approval. No users on old versions.
No App Store Restrictions
Apple takes 30% of in-app purchases. Their review process can reject or delay you.
Web apps bypass this entirely.
SEO
Web apps can be indexed by search engines.
App store optimization is its own beast.
Lower Cost
One codebase instead of two (or three). Faster to build, cheaper to maintain.
Business-to-Business
B2B users typically don't want to download apps. Web apps fit better.
The Cost Reality
Web app: $30,000 - $100,000
- One codebase
- Works everywhere
Native app (iOS only): $50,000 - $150,000
- Only reaches iPhone users
- Need separate Android build
Native apps (iOS + Android): $80,000 - $250,000+
- Two codebases to build and maintain
- Double the testing
- Ongoing platform updates
Cross-platform app: $50,000 - $150,000
- One codebase, both platforms
- Some limitations vs. native
- Still more than web
Maintenance:
- Web: 15-20% of initial cost annually
- Mobile: 20-30% of initial cost annually (more platform changes)
Decision Framework
Choose Native Mobile App If:
✅ You need deep hardware access (camera, sensors, Bluetooth) ✅ Performance is critical (games, media editing) ✅ Offline functionality is essential ✅ Push notifications are central to your value proposition ✅ App Store presence drives discovery ✅ You have the budget for ongoing maintenance
Choose Web App If:
✅ Accessibility is priority (no download friction) ✅ You want fast, frequent updates ✅ Your users are primarily on desktop or mix of devices ✅ It's a B2B application ✅ Budget is limited ✅ You want SEO benefits
Consider PWA If:
✅ You want "app-like" experience without App Store ✅ Offline capability needed but not extreme ✅ Want installation without download ✅ Budget is between web and native
Consider Cross-Platform If:
✅ You need mobile app features ✅ Budget doesn't allow separate iOS and Android ✅ Some performance trade-off is acceptable ✅ Team can work in React Native/Flutter
The Honest Truth
Most business software should be a web app.
The native app is often desired for ego ("we have an app!") rather than actual user need.
Ask yourself:
- Will users actually download this?
- How often will they use it?
- What can we do in a native app that we can't on web?
If you can't answer those clearly, start with a web app. You can always add a native app later if there's genuine demand.
What to Ask Your Development Partner
- "Why do you recommend native/web/hybrid?" (They should explain based on your needs)
- "What features require native?" (Get specifics, not generalities)
- "What's the total cost of ownership over 3 years?" (Include maintenance)
- "Can we start with web and add native later?" (Often yes)
- "What's your experience with [platform]?" (Match expertise to choice)
Not sure which approach fits your needs? Let's figure it out together