# Does your small business need an app? Decide this before anyone writes code

About nine in ten US adults (91%) own a smartphone. That does not mean every business needs an app. Here are five questions to answer first, and what a sensible first version looks like.

Pew Research Center reported in October 2026 that 91% of US adults own a smartphone. In Pew's first survey of smartphone ownership, in 2011, the figure was 35%. Most of your customers have one. The question is whether they want your business on it as an app, or whether a fast website does the job.

![91 percent of US adults own a smartphone, up from 35 percent in 2011. Source: Pew Research Center, October 2026.](img-1-smartphones.png)

Smartphone ownership in the US. Source: Pew Research Center Mobile Fact Sheet.

An app is worth building when people will open it again and again. A website is enough when people visit once to find your hours or your phone number. Most small businesses sit somewhere in between. These five questions help you work out which side you are on.

## 1. What will people do in the app every week?

Write down the action, not the feature. "Book my next class." "Reorder the same coffee." "Check my rent balance." "Pick tonight's dinner spot." If you cannot name something a customer would do at least a few times a month, a mobile-friendly website is probably the better first step.

## 2. Who exactly is it for?

"Our customers" is too wide. Is it your regulars, your members, your staff in the field, or tourists who are new to town? Each group needs different screens. An app for staff can be plain and fast. An app for new customers has to explain itself in seconds.

## 3. What does a good first version look like?

The best first versions do one job well. A booking app that only books. A members app that only shows the schedule and lets people check in. You can add rewards, chat and payments later, once you know people use the first thing.

A short brief helps here. One page is enough: what the app does, who uses it, and what a good first version looks like. If you can write that page, you are ready to talk to a builder. If you cannot, spend another week on it before you spend money.

## 4. What does it need to connect to?

Most useful apps talk to something you already run: a booking calendar, a point-of-sale system, a spreadsheet, a customer list. List those systems before you start. Some have open connections and some do not, and that one fact can change the cost and the timeline more than the screens do. Ask your builder to confirm, in writing, which of your tools they can connect before you commit.

## 5. Who will look after it?

An app is not done when it launches. Phones update, app store rules change, and your menu, prices or class times change. Decide who updates the content, who answers when something breaks, and who decides what goes into the next version.

## Three mistakes that waste the first version

- **Copying the website into an app.** If the app shows the same pages as your site, people will not keep it. Give it a job the website cannot do as well, like one-tap rebooking.
- **Building every feature at once.** A long feature list means a long wait and a bigger bill before you learn anything. Launch the one job, watch how people use it, then add the next thing.
- **Forgetting about small screens and one hand.** People use apps on the bus, at the counter, with a coffee in the other hand. Buttons need to be large and the main action needs to be easy to reach with a thumb.

## How we build apps at Vidhani AI

You hold the process at both ends: you send the brief, and you approve the app before it is published.

![Four steps: you send a brief; we design and build; we test on real phone sizes and a second AI reviewer checks the work against the brief; you try and approve the app before it is published.](img-2-brief-to-live.png)

From brief to live app. You start it and you sign off on it.

- You send a brief: what the app does, who uses it, and what a good first version looks like.
- Our team designs the screens, builds the app and writes the code to your brief.
- We test it on real phone sizes. A second AI reviewer checks the work against your brief.
- You try it and approve it before it is published. Then we keep it running.

We build apps for small businesses such as booking, trip planning, suggestions and customer tools. Pricing is quoted after a call, based on what the app needs to do. If you also use our AI front desk, the app can usually connect to it; we confirm that during scoping.

## A quick test before you call anyone

Ask five of your best customers one question: "If we had an app, what would you use it for?" If three of them give you the same answer, you have your first version. If they all shrug, put the money into your website first.

**Have an app idea for your business?** Book a 30-minute call. Bring your one-page brief, or bring the idea and we will scope the first version on the call.

[Book a 30-minute call](https://cal.com/vidhaniai/30min)

Facts about our process match vidhani.ai/mobile-apps as of November 2026.

## Sources

1. Pew Research Center, "Mobile Fact Sheet", 19 October 2026 (survey conducted Jan. 30 to June 18, 2026). https://www.pewresearch.org/internet/fact-sheet/mobile/
2. Vidhani AI, Mobile apps. https://vidhani.ai/mobile-apps/
