Build a web platform first if your users are at a desk, the product involves data entry or long sessions, or you need to change it quickly and avoid app store review. Build a mobile app first if the product depends on the phone: camera, location, push notifications, offline use, or moments away from a computer. Many first products are best served by a responsive web app that works on phones, with native apps added once the idea is proven.
Founders often assume a startup means an app in the store. Sometimes it does. Often the first version is better as a web platform, and the app store is where the second or third release goes. This guide gives you the questions that decide it, and the cases where the answer is obvious.
What is the actual difference?
A web platform runs in a browser. Users reach it by a link, on any device, with no installation. You update it whenever you want. A mobile app is installed from the App Store or Google Play. It can use the phone's hardware fully, sits on the home screen, and sends push notifications. Both talk to the same backend, so the choice is about the front door, not the whole house.
Which questions decide it?
| Question | Points to web | Points to mobile |
|---|---|---|
| Where are users when they use it? | At a desk, in an office, at home on a laptop | Out and about, on site, in a shop, in a car |
| How long is a session? | Minutes to hours, lots of reading or typing | Seconds to minutes, quick actions |
| Does it need the phone's hardware? | No | Camera, GPS, Bluetooth, sensors, offline storage |
| How do users come back? | Email, bookmarks, a link from another system | Push notifications, a home screen icon, habit |
| How often will you change it? | Weekly or faster, especially early | Monthly is fine, releases can wait for review |
| Who are the buyers? | Businesses, teams, administrators | Consumers, field staff, drivers |
| How will people find it? | Search engines, links, sales conversations | App store search, word of mouth, existing audience |
When is web clearly right?
- Business software. Dashboards, admin tools, booking management, anything a person uses at a desk for a while. Nobody wants to run a business from a phone screen.
- Marketplaces and directories at launch. Search engines can index a web platform. They cannot index the inside of an app. Early supply and demand often arrive through search.
- Anything still changing fast. In the first months you will change the product weekly. On the web that takes minutes. In the app store it takes a release and a review.
- Products that need to be shared by link. A quote, a document, a listing, an invitation. A link that opens instantly beats a link that asks the recipient to install something.
When is mobile clearly right?
- The phone is the point. Photographing a receipt, scanning a code, tracking a run, navigating to a job, paying at a counter.
- Notifications drive the product. Messaging, alerts, reminders, anything where the app has to reach the user rather than wait for them.
- Offline or poor connectivity. Field workers, ships, rural sites, basements.
- Daily habit is the business model. If success means the user opens it every day, a home screen icon matters.
What is the middle option?
A responsive web app, sometimes called a progressive web app, is built once and works in a desktop browser and on a phone. Modern web apps can be added to the home screen, work partially offline and, on Android and increasingly on iOS, send notifications. They cannot do everything a native app can, and they are not in the app stores, but for a first release they cover a large share of products at a fraction of the cost of web plus two native apps.
The pattern we recommend most often to founders: a responsive web app first, measure where users actually use it, then build native apps for the platform that data points to. It keeps the first budget small and makes the second decision with evidence instead of guesswork.
What about both at once?
Possible, and sometimes necessary, for example when the customer books on a phone and the business manages on a desktop. Even then, ask which side proves the idea first and whether the other side can start as a simple web page or a manual process. Building two front doors before you know which one people walk through is the most common way to double an MVP budget. Our post on what an MVP should leave out covers this trade-off.
Choose web first if
- Users are at a desk or the product is used for long sessions.
- You expect to change the product often in the first months.
- Search engines or shared links are how people will find it.
- Your buyers are businesses.
Choose mobile first if
- The product depends on camera, location, sensors or offline use.
- Push notifications are core to the experience.
- Users are consumers or field staff, on the move.
- Daily habit is how the product wins.
How 7L approaches the choice
This is one of the first questions in our discovery phase, and the answer comes from your users, not from what we prefer to build. We build web platforms, native and cross-platform mobile apps, so there is no incentive to steer you. If you are weighing the choice, tell us about your users and we will tell you which door to open first. Once you have chosen mobile, the next question is native or cross-platform.
Frequently asked questions
Is a mobile app more expensive than a web platform?
Usually, for a first release, because you need at least one native or cross-platform app plus the backend, and often a web admin panel too. A web platform is one front end. See our guide to app costs for the ranges.
Can a web app be put in the app stores?
Wrapped web apps can be submitted, and some are accepted, but Apple in particular rejects apps that are only a website in a shell. If the store presence matters, plan a proper native or cross-platform app.
Will I lose users if I do not have an app?
Only if your users expect one for the kind of product it is. Consumers expect apps for daily-use products. Business users are used to web tools. Ask your interviewees where they would expect to find it.
Can I start with web and add an app later without rebuilding?
Yes, if the backend is built as an API from the start, which any competent team will do. The mobile app then talks to the same backend, and the web platform keeps working.
What about a desktop application?
Rarely needed for a new product. Modern web platforms cover almost every desktop use case. The exceptions are heavy hardware integration, very large files, or environments without reliable internet.