Website or mobile app? A decision guide for small businesses in Chennai

"We need an app" is one of the most common opening lines in an enquiry, and about half the time the honest answer is "you need a website, and here is why". The other half need the app. This is how to tell.

What a website is for

A website is where people who do not know you yet find you. Someone searches for a service in Chennai, sees your site, decides in a few seconds whether you look real and competent, and calls or messages. It is also where every other channel lands: your Google Business Profile, your Instagram bio, your WhatsApp catalogue, your flyers.

A website needs no installation, works on every device, is indexed by Google, and can be updated in an hour. Every business needs one. There is no business for which an app replaces it.

What a mobile app is for

An app is for people who have already chosen you and will come back repeatedly. It lives on their home screen, can send notifications, can work with the camera and location, and can remember them. Those are advantages only when there is a reason to open it weekly:

• Ordering food, groceries or products from you regularly
• Booking classes, appointments or services on a schedule
• Tracking something: a delivery, a workout, a child's progress, an invoice
• A loyalty or membership programme
• A tool your staff use in the field

If you cannot name what a customer will do in the app in a typical week, the app will be installed once, forgotten and eventually deleted. That is not a failure of the build; it is what apps without a weekly job do.

The costs are different in kind, not just size

A website is one build, hosted cheaply, changed freely. An app is two store accounts, a review process on every release, a closed test with 12 testers before Google Play allows production for a new personal account, and yearly work to stay compatible with new iOS and Android versions. The app cost guide and the publishing guide go through both.

None of that is a reason not to build an app. It is a reason to build one only when the weekly job exists.

The simple test

Answer these three:

1. Will new customers find you through it? Websites yes, apps no. Nobody searches the App Store for a plumber.
2. Will an existing customer open it every week? If yes, an app earns its notifications and its home-screen icon.
3. Does it need the phone's hardware or offline use? Camera scanning, GPS tracking in the field, working without signal. Apps do this properly; websites do it partly.

If you answered yes to the first and no to the other two: website. If you answered yes to the second or third: app, and still a website. If you are a startup whose product *is* the app, the website is the marketing page for it.

When you need both

A restaurant with a menu site and an ordering app. A gym with a site for new members and an app for class bookings. A logistics business with a site for clients and an app for drivers. In these cases, build them from a shared codebase: a React website and a React Native app can share the backend, the business logic and much of the code, which is how UgeWorks keeps a two-platform project affordable. See the mobile app and small business website pages for the two halves.

A middle option worth knowing

A well-built website can be installed to a phone's home screen and work offline as a progressive web app, without either store. It cannot do everything a native app can, and it does not appear in the stores, but for a booking or ordering flow it is often enough and it is far cheaper to run. Ask about it before committing to two store accounts.

Questions people ask

Sources

1. Google Play closed testing requirements — 12 testers, 14 days