# App or mobile website: how to choose

14 November 2026

A customer on a phone can reach you two ways. One is a website that reads cleanly on a small screen. The other is an app they install and open again. They look similar. They are different jobs. This post is the choice, and what each build includes if you ask us to do it.

## Start with the job

Write what the person does. Book a visit. Reorder the same item. Check a balance. Find the hours and call. If they do it once, a website is the tool. If they do it on a regular week, an app can earn a place on the phone.

Name who it is for. Regulars, members, people who already buy from you, or a new visitor who only needs the address. A new visitor should not have to install an app to see your hours. A member who books every week might.

Websites are on the [web design page](/web-design/). Apps are on the [mobile apps page](/mobile-apps/).

## What a mobile website is for

A website is a set of pages. On a phone it has to load quickly and read cleanly. If the current site is hard to read on a phone, fix that before you talk about an app. People who will not install anything still need a way to call.

Calls, forms, and booking links sit where a visitor looks for them. Titles, descriptions, and the order of the pages are written so a search engine can read the business. Every page is checked on phone sizes and on desktop sizes before you see it. A second reviewer checks the work against your brief.

You send the brief: what the business does, who it serves, and what a visitor should do. We design the pages, build them, test them, and review them. You approve the site before it is published, and we keep it running. We do not publish a fixed count of days. The timeline comes after the first call, once the pages are known. The price is quoted after that call, from the pages and the features.

The site can connect to the AI front desk. The front desk can answer calls and chat for the business, and book into your calendar. That is the website plus the phone. It is not an app.

## What an app is for

An app is something people keep. The mobile apps page scopes it to the business: bookings, orders, suggestions, or member tools. On the call you say what the app does, who uses it, and what a good first version looks like.

The screens are for a thumb: clear screens, large tap targets, one-handed use. A long article, a price list, and the story of the shop belong on the website. The app keeps the action.

It connects to the systems you already use, where those systems allow it. Connections to those tools are confirmed in writing during scoping, before you commit. Usually it can also connect to the AI front desk. The answer is written down before you commit.

We check the app on real phone sizes before you see it: the phones, the flows, the errors, and the wording. A second AI reviewer checks the work against your brief. You try it and approve it before it is published. Then we publish it and keep it running.

The app price is quoted after a 30-minute scoping call, based on what the app must do. Ask how long the first version will take.

![Two phones. One holds a long page. The other holds one large button. The labels are Site and App.](img-1-site-or-app.png)

A site is a page a person scrolls. An app is one action, large enough for a thumb.

## A short way to decide

1. They need hours, an address, or a way to call. That is a site.
2. They repeat the same action on later weeks. That can be an app.
3. The action writes into a record you already keep, such as a booking or an order. A site can take the first one from search or from a text. An app fits when they come back for the next one on their own.
4. You cannot name the one action. Do not build the app yet. A website can take calls and bookings while you rewrite the sentence.
5. The current site fails on a phone. Repair it first. That page is what people open when they skip an install.

Keep the phone number and the website either way. If the app is the only door, you miss the person who only wanted to call.

![One large button on a phone, for a visit the customer makes again. The label is Again.](img-2-open-again.png)

The return visit is one action, not a second copy of the website.

## What you send

Both builds start the same way. You send a brief. We design, build, test, and review. You approve before anything is published. The price comes after the call, when the work is known.

The briefs are different sheets. For a site, list the pages and the action on each one. For an app, write the one job, who repeats it, and what done looks like the first time. A brief that asks for a site and an app is two jobs. Split them, or ship the site and see which action people repeat.

The front desk is optional. On a website it answers calls and chat, and books the calendar. On an app, a connection is usually possible, and only after it is confirmed in writing. You can buy one without the other.

## What to leave off the brief

Leave the app price and the app timeline off your brief. The price is quoted after a 30-minute scoping call, based on what the app must do. Ask how long the first version will take. Connections to the tools you already use are confirmed in writing during scoping. A website timeline is given after the first call, once the pages are known.

A page that reads well on a phone, with a call button and a booking link, is a complete product for plenty of shops. The app is for customers who come back without a prompt.

## Five lines to bring

1. The one job, in a sentence a customer would say.
2. Who it is for.
3. Site, app, or site first.
4. The system it has to reach, if any.
5. What you will look at before you approve it.

Bring the page to a [30-minute call](https://cal.com/vidhaniai/30min). Read [mobile apps](/mobile-apps/) if the answer is an app, or [web design](/web-design/) if the answer is a site. If line 3 is blank, wait. The blank line is cheaper than the wrong build.
