Buyer’s guide · 5 min read
Website, PWA or mobile app: what should your business build first in 2027?
Most businesses should not start with an app. Some absolutely should. A simple test for which one you are, and what a progressive web app changes.
Quite a few of the app enquiries we get would be better served, at least to begin with, by a fast website. I’m not saying that to be difficult. An app costs several times more to build, it has to be approved by Apple and Google, and then it has to persuade people to install it on phones that are already full. For some businesses all that effort pays back handsomely. For others it’s a very expensive icon nobody ever opens.
So before you brief anyone, work out which kind of business you are. It takes about a minute.
The one-minute test
Be honest with these:
- Will your customers use this at least once a week?
- Do they need to be logged in to get anything out of it, to track orders, book again or check a balance, say?
- Does it need the phone’s hardware, like the camera, GPS in the background, Bluetooth or biometrics?
- Would push notifications bring customers back in a way they’d actually welcome?
- Do you already have customers asking for an app?
Three or more “yes” answers and an app is probably worth building. Zero or one, and a good website will do more for you, sooner, for less money. If you landed on two, look closely at the middle option: a progressive web app.
The three options, briefly
A website
Works on every device. People find it through Google, you can update it instantly, and nobody has to install anything. It’s the cheapest and fastest way to get in front of customers.
A progressive web app (PWA)
A website that behaves like an app. It can sit on the home screen, open full-screen, work partly offline and send notifications (on iPhones too, once added to the home screen, since iOS 16.4). There’s no app store, no approval process and only one codebase. Flipkart’s “Lite” web app was one of the early, well-known examples here in India.
A mobile app
Native or cross-platform apps, installed from the App Store and Google Play. You get the richest experience and full access to the phone, and you pay the highest cost to build it and keep it updated.
How they compare
| Website | PWA | Mobile app | |
|---|---|---|---|
| Typical first-version budget | ₹60,000 – ₹2 lakh | ₹2 – ₹8 lakh | ₹3 – ₹20 lakh+ |
| Time to launch | 3–6 weeks | 6–12 weeks | 8–20 weeks |
| Found on Google | Yes | Yes | Mostly no, only the store listing |
| Needs installing | No | Optional | Yes |
| Push notifications | No | Yes, with some limits on iPhone | Yes |
| Works offline | No | Partly | Yes |
| Camera, GPS, Bluetooth, biometrics | Limited | Partial | Full |
| App store fees and approval | None | None | Yes |
The budgets are indicative for professionally built projects in India, excluding GST. Our more detailed guides on website costs and app costs break them down further.
When a website is enough
- Customers find you once, enquire, and then deal with your team from there. That describes most B2B services, clinics, schools, builders and consultants.
- People buy from you a few times a year, rather than a few times a month.
- Your main growth channel is Google search or ads. Search engines index websites. They don’t index app screens.
- You’re still testing whether customers want what you offer.
When an app earns its keep
- Frequent, repeat use, such as groceries, food, fitness, learning, banking or bookings you make every week.
- Logged-in utility like order tracking, statements, loyalty points or saved preferences.
- Features that need the phone itself: scanning, location tracking for delivery staff, offline forms for field teams.
- A loyal customer base you want to reach directly, without paying for every single visit through ads.
Where a PWA fits, especially in India
Plenty of Indian customers are careful about storage on budget phones, and careful about data use too. Asking them to download a 60 MB app for something they’ll open twice a month is a big ask. A PWA takes that barrier away. It opens from a link, installs in one tap if the customer wants it, and weighs a fraction of what a native app does.
PWAs work particularly well for ordering from a local business, customer portals, internal staff tools, event and booking apps, and content-heavy apps like news or learning. They’re weaker for anything that needs deep hardware access or a lot of background processing.
The sequence we usually recommend
- Start with a fast, well-built website that ranks and converts. It’s where most customers will meet you anyway.
- Add PWA features once you see repeat visitors and logged-in use. On a well-built site that’s often only a few weeks of extra work.
- Build the app when the numbers justify it, meaning enough weekly active users, or a feature a browser simply can’t deliver.
If you do go straight to an app, keep the first version tight. Our MVP development guide explains how, and Flutter vs React Native covers which framework to build it in.
What changes in 2027
Search keeps getting more conversational, with Google’s AI Overviews and AI Mode summarising the web for people. Those systems read websites. They can’t read app screens. So if your business depends on being discovered, your website matters more now than it did a few years ago, even if your main product is an app.
Meanwhile, what customers expect from apps keeps going up. A slow or buggy app now does more damage than having no app at all, because the reviews are public and they stick around. Build one when you can afford to build it well.
Talk it through with us
We build websites and PWAs as well as mobile apps, so we don’t mind which one you choose. If you’re unsure, send us a few lines about your customers and how often they’d use it, and we’ll give you a straight recommendation.
