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 receive would be better served, at least to begin with, by a fast website. That isn’t us being difficult. An app costs several times more to build, has to be approved by Apple and Google, and has to persuade people to install it on phones that are already full. For some businesses that effort pays back handsomely. For others it is a very expensive icon nobody opens.
So before you brief anyone, work out which kind of business you are. It takes about a minute.
The one-minute test
Answer these honestly:
- Will your customers use this at least once a week?
- Do they need to be logged in to get value from it, for example to track orders, book again or check balances?
- 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 would welcome?
- Do you already have customers who ask for an app?
Three or more “yes” answers and an app is probably worth it. Zero or one, and a good website will do more for you, sooner, for less. Two means it’s time to look closely at the middle option: a progressive web app.
The three options, briefly
A website
Works on every device, found through Google, updated instantly, no installation. The cheapest and fastest way to be in front of customers.
A progressive web app (PWA)
A website that behaves like an app. It can be added to the home screen, open full-screen, work partly offline and send notifications, including on iPhones added to the home screen since iOS 16.4. No app store, no approval process, and one codebase. Flipkart’s “Lite” web app was one of the early, famous examples in India.
A mobile app
Native or cross-platform apps installed from the App Store and Google Play. The richest experience, full access to the phone, and the highest cost to build and keep 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 |
Budgets are indicative for professionally built projects in India, excluding GST. Our 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, as with most B2B services, clinics, schools, builders and consultants.
- People buy from you a few times a year, not a few times a month.
- Your main growth channel is Google search or ads. Search engines index websites, not app screens.
- You are still testing whether customers want what you offer.
When an app earns its keep
- Frequent, repeat use: groceries, food, fitness, learning, banking, bookings you make every week.
- Logged-in utility such as 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 visit through ads.
Where a PWA fits, especially in India
A lot of Indian customers are careful about storage on budget phones and about data use. Asking them to download a 60 MB app for something they’ll use twice a month is a big ask. A PWA removes that barrier: it opens from a link, installs in a tap if the customer wants it, and weighs a fraction of a native app.
PWAs work particularly well for ordering from a local business, customer portals, internal tools for staff, event and booking apps, and content-heavy apps like news or learning. They are weaker for anything that needs deep hardware access or heavy 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 when you see repeat visitors and logged-in use. That is often a few weeks of extra work on a well-built site.
- Build the app when the numbers justify it: 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, not app screens. If your business depends on being discovered, the website has become more important, not less, even for companies whose main product is an app.
On the other side, customer expectations of apps keep rising. A slow or buggy app now does more damage than no app, because the reviews are public and permanent. 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 have no stake in 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.
