Choosing a Mobile App or Mobile Web App Developer: Questions to Ask First
"We need a mobile app" is where most businesses start, but it's the wrong first question — the right first question is what problem the app needs to solve, because that determines whether you actually need a native app, a cross-platform app, or whether a well-built mobile web app (no App Store required) solves the problem for a fraction of the cost and timeline.
Question 1: Does This Actually Need to Be an App, or a Mobile-Optimized Website?
If the core need is displaying information, taking bookings, or processing orders — without requiring camera access, push notifications, offline functionality, or device-specific hardware features — a fast, mobile-optimized website (sometimes built as a Progressive Web App, installable without an app store) does the job at a fraction of the cost, with no App Store approval delays and no separate iOS/Android codebases to maintain. Ask any developer to justify why a native or cross-platform app is actually necessary for your specific use case before accepting that scope.
Question 2: Native, or Cross-Platform (Flutter/React Native)?
Native development (separate Swift/Kotlin codebases for iOS and Android) gives the best possible performance and access to every platform-specific feature, at roughly double the development cost and timeline of a single cross-platform codebase. Cross-platform frameworks like Flutter now produce genuinely near-native performance for the large majority of business app use cases — the gap that used to justify native-only development has narrowed considerably. Ask a prospective developer to justify native specifically if that's what they're recommending; for most business apps (not games, not apps needing deep hardware integration), it's usually not necessary.
Question 3: What Does Their Portfolio Actually Demonstrate?
Ask to see an app they've built actually live in the App Store or Play Store, not just design mockups — a shipped, published, currently-maintained app is a meaningfully different signal than a Figma prototype. Download it if possible and use it; you'll learn more about the developer's real quality bar in five minutes of actual use than from any portfolio page.
Question 4: What Happens After Launch?
Mobile apps require ongoing maintenance in a way many first-time buyers don't anticipate: OS updates (a new iOS or Android version can break existing functionality), App Store policy changes requiring updates to stay compliant, and server-side backend maintenance if the app talks to an API. Ask explicitly what the post-launch maintenance arrangement and cost look like — an app that works perfectly at launch and is never updated again typically starts breaking within a year or two as the underlying platforms evolve.
Realistic Pricing Ranges
| Type | Typical range (NPR) |
|---|---|
| Mobile-optimized website / PWA | 25,000–70,000 |
| Simple cross-platform app (Flutter/React Native) | 100,000–300,000 |
| Complex cross-platform app with backend | 300,000–800,000+ |
| Native (separate iOS + Android) | Roughly 1.5-2x the cross-platform equivalent |
Frequently Asked Questions
How long does App Store and Play Store approval actually take?
Play Store approval is often within a day or two; Apple's App Store review typically takes several days and can involve rejection-and-resubmission cycles if guidelines aren't followed carefully — build this into your launch timeline expectations.
Can a mobile web app send push notifications like a native app?
Modern PWAs can support push notifications on Android and, more recently, iOS as well, though the setup and reliability still generally favor native apps for notification-heavy use cases.
Not sure whether you need a native app or a mobile web app? See our development services or tell us the problem you're solving and we'll recommend honestly.
