Web app vs mobile app: which should you build first?
For most new products the answer is a responsive web app first, and a mobile app when a feature genuinely needs the phone. Here’s how to tell, what each route costs in time and fees, and where PWAs and cross-platform frameworks fit.
By the METHODSS team
Where to start
On this page
The short answer
For most new products, build a responsive web app first and add a mobile app when a specific feature needs the phone. A web app reaches every device from one codebase, ships changes the moment they are ready, and needs no store approval, which is what a product still finding its shape needs most.
Start with a mobile app instead when the core of the product depends on what only an installed app does well:
- Working offline or in the field, such as inspections, deliveries or farm work, where a signal can’t be assumed.
- Deep device access: the camera all day, background location, Bluetooth hardware, health sensors.
- Daily habit and notifications at the centre of the experience, as in consumer apps people open many times a day.
- Your users expect the store. In some consumer markets an app is how people judge whether a product is real.
Whichever you choose, the web version has to work well on phones anyway. In September 2026, phones accounted for 58.99% of web page views worldwide, 53.56% in the UK and 49.1% in the US, according to Statcounter. “Web first” means mobile-first web, not a desktop site.
How they differ in practice
| Web app | Mobile app | |
|---|---|---|
| Reaching users | A link, search results, an email | An app store listing and an install |
| Shipping changes | Live as soon as you deploy | Store review, then users update |
| Device features | Camera, location and notifications, with limits | Full access, including background work and hardware |
| Offline use | Possible, but limited | Designed in from the start |
| Selling digital goods | Your own payments, such as Stripe | Store billing rules and commission apply |
| Codebases | One | One cross-platform, or two native |
| Discovery | Search engines and links | Store search and rankings |
| Ongoing store rules | None | Yearly platform updates: Google Play requires new apps and updates to target an Android version released within the past year |
The second row is the one founders feel most. On the web, a bug found at 10am can be fixed by lunch. In an app, the fix waits for store review and then for each user to update. Apple says it typically reviews “at least 50% of submissions in less than 24 hours and 90% in less than 48 hours”; Google says some reviews take “up to seven days or longer in exceptional cases”.
What the app stores charge
Publishing an app costs little up front; selling through one is where the stores take their share.
| Apple App Store | Google Play | |
|---|---|---|
| To publish | 99 USD a year (Apple Developer Program) | US$25, once |
| Commission on digital goods | 30% standard; 15% in the Small Business Program (up to 1 million USD a year in proceeds, after commission) | For users in the US, UK and EEA since 30 June 2026: 10% plus a 5% billing fee on the first $1M a year; 20% to 25% plus the billing fee above it |
These rules are moving. Apple has separate terms for apps in the EU from 1 October 2026, including a 26% commission on in-app purchases there; its guidelines now allow apps on the US storefront to link to outside purchases while the related Epic v. Apple dispute is before the US Supreme Court. Google applies its new fee table in Australia and Japan from 30 September 2026, and its older 15% and 30% tiers elsewhere. Physical goods and services used outside the app, such as deliveries, bookings or B2B services, are generally paid through your own payment provider in either case. Check the current rules for your category and region before you design pricing.
Progressive web apps: the middle path
A progressive web app (PWA) is a web app that can be installed to the home screen, work offline for some tasks and send notifications. It keeps one codebase and instant updates, and covers more of the “app” experience than many people assume.
- Since iOS and iPadOS 16.4 (2023), web apps added to the Home Screen can send push notifications, as long as the permission request responds to a user action “such as tapping on a ‘subscribe’ button provided by the web app”.
- Support can change quickly. In February 2024 Apple said it would remove Home Screen web apps in the EU to comply with the Digital Markets Act, then reversed course within weeks: “we will continue to offer the existing Home Screen web apps capability in the EU.”
The limits are real, mostly on iPhone: background work, some hardware access and how installation is surfaced to users. A PWA suits products that need to feel like an app now and then; it doesn’t replace a native app for field work or hardware.
If you need an app: native or cross-platform?
Most business apps don’t need two separate native codebases. The common routes:
| Approach | What it is | Suits |
|---|---|---|
| React Native | Native Android and iOS apps “using React”: “written in JavaScript, rendered with native code” | Teams already using React on the web; sharing logic and skills |
| Flutter | An open-source framework for “natively compiled, multi-platform applications from a single codebase” | The same pixel-precise design on every device |
| Capacitor | “A cross-platform native runtime for web apps”: your web app in a native shell, with plugins for device features | Turning an existing web app into a store app, with native plugins |
| Native (Swift, Kotlin) | Separate apps written in each platform’s own language | Heavy use of platform features, or the highest performance |
Our Farm Portal case study is a React Native app on a NestJS API that brings a farm’s daily work, herd, milk records and finances into one mobile app: work that happens around the farm rather than at a desk, which is the case where mobile comes first. Choosing between these routes is part of every web and mobile app project we plan.
Decide with five questions
| Question | If yes | If no |
|---|---|---|
| Must it work without a connection? | Mobile app | Web is fine |
| Does it need background location, Bluetooth or sensors? | Mobile app | Web is fine |
| Will most users find it through search or a link? | Web app first | Consider the store |
| Are you still changing the product every week? | Web app first | Either |
| Will you sell digital goods inside it? | Plan around store rules | No store commission to plan for |
If none of the mobile answers is a clear yes, start on the web. You can add an app later without starting again, if you plan for it.
Plan for both from day one
Starting on the web doesn’t mean painting yourself into a corner. A few early decisions make a mobile app an addition rather than a rebuild:
- An API-first backend, so web and mobile clients use the same services and business rules.
- Authentication that works for both, with tokens and sessions designed for apps as well as browsers.
- A design system with tokens and components that translate to mobile.
- Analytics from the first release, so you can see which features people use on their phones and build the app around them.
For what the first release itself costs, see how much an MVP costs.
Sources
Every source below was read on 26 October 2026. Prices and product details change; check the current page before relying on a figure.
- Statcounter Global Stats: Desktop vs Mobile vs Tablet Market Share Worldwide, September 2026
- Statcounter Global Stats: Desktop vs Mobile vs Tablet Market Share, United States
- Statcounter Global Stats: Desktop vs Mobile vs Tablet Market Share, United Kingdom
- Apple: App Review
- Apple: App Review Guidelines
- Apple: App Store Small Business Program
- Apple Newsroom: Apple announces App Store Small Business Program
- Apple: Changes for apps in the European Union
- Apple (archived copy, 4 March 2024): Update on apps distributed in the European Union
- Apple: Apple Developer Program
- Google: Service fees (Play Console Help)
- Google: Publish your app (Play Console Help)
- Google: Target API level requirements for Google Play apps
- Google: Get started with Play Console
- WebKit: Web Push for Web Apps on iOS and iPadOS
- React Native: React Native
- Flutter: Flutter
- Capacitor: Capacitor