Start with a website if people find you by searching, you need to be easy to try, or you are still testing the idea. Build an app first if the product depends on the camera, sensors, high performance or daily repeat use on a phone. Many products start as a mobile friendly website and add an app later.
The right answer depends on how customers will find you and how often they will come back. Once you know that, the budget question gets easier.
01. When should a website come first?
- Customers find you by searching, and a website is what they land on.
- People use the product once or now and then, not every day.
- You want people to try it from a link, with nothing to install.
- You are still testing whether the idea works.
- Your customers use many different phones and computers.
02. When should an app come first?
- People will use it daily, and being on their home screen matters.
- It needs the camera, sensors or other phone features.
- Performance is central to the experience.
- You already have an audience, so you do not rely on search to be found.
- The product is mainly used on the go.
03. Is there a middle option?
Yes. A progressive web app is a website that people can install on their phone without going through an app store. It will not suit every product, but it is worth asking about if you are unsure, because it can cost less than building separate apps.
04. How do the costs and timelines compare?
These are our starting points. App projects are quoted after a call because they vary so much.
| Option | Starting point | Timeline |
|---|---|---|
| Website, 3 to 5 pages | From $5,500 | 3 to 4 weeks |
| Website, 10 or more pages | From $9,000 | 5 to 7 weeks |
| App design on its own | From $6,000 | 3 to 4 weeks |
| A typical first version of a mobile app | $12,000 to $40,000 | 8 to 16 weeks |
An app also has costs a website does not. Apple charges a yearly developer fee and Google a one time fee, both paid in your own name. Apps need updating as phone software changes, so plan for a monthly update plan too.
05. One codebase or two?
For most businesses, one codebase built in Flutter or React Native runs on both iPhone and Android and costs less than building twice. A native iPhone app in SwiftUI makes sense when the app depends on the camera, sensors or high performance.
Flutter suits heavily custom designs. React Native suits a team that already uses React on the web. We recommend one on the call and explain why.
06. Which four questions decide it?
- Will people use it daily, or now and then?
- Do they need a phone feature a website cannot reach?
- Do they find you by searching, or do you already have an audience?
- Are you testing an idea, or scaling one that works?
Now and then, no phone feature, search, and testing all point to a website first. Daily, phone features, an existing audience and scaling point to an app. If you are testing an idea, how to scope an MVP shows how to keep version one small.
07. Will you need a website anyway?
Usually, yes, a simple one. An app needs a page for its store listing, a privacy policy and a support page. It can be built alongside the app.
Frequently asked questions
Can I start with a website and add an app later?
Yes, and it is a sensible way to prove demand before spending more. Plan the design and data so the app can reuse them.
Do I need both?
Often you end up with both. The question is which to build first.
Who owns the app and the store accounts?
You do. From launch, the code, store accounts and app listing belong to you.
Can you take over an app someone else built?
Yes. We review the existing code first and give you a written assessment of its condition before quoting.
