![Ideogram Technology Solutions [P] Ltd.](/assets/img/ideogram-logo.png){kind=logo}
"Should we build an app?" is one of the most common questions we hear. Sometimes the answer is yes. Often a good website does the job better and at a fraction of the cost. Here is how to decide.
What each does best
| Website | Mobile app | |
|---|---|---|
| Found on Google | Yes | No, found in app stores |
| Needs installation | No | Yes |
| Works on every device | Yes, through a browser | Separate Android and iOS builds |
| Push notifications | Limited | Yes |
| Works offline | Limited | Yes |
| Phone features (camera, GPS, biometrics) | Some | Full access |
| Updates | Instant | Through app store releases |
A website is usually the right first step if
- People need to find you on Google before they know your name
- Visitors come occasionally, for information, enquiries or one-off purchases
- You want to reach everyone, on any device, without asking them to install anything
- Your budget and team are limited
For most businesses, schools and institutions, a fast, mobile-friendly website comes first. It is your public front door.
An app makes sense when
- People use your service often: daily orders, bookings, school updates for parents, banking
- You need push notifications to bring people back
- The service needs phone features, such as the camera, location tracking, offline use or fingerprint login
- You have logged-in users who benefit from a personalised experience
- You can commit to maintaining it with updates for new Android and iOS versions
An app nobody opens is expensive. Be honest about how often your users will need it.
The middle path: progressive web apps
A progressive web app (PWA) is a website that can be added to a phone's home screen, open like an app, work partly offline and, on supported devices, send notifications. It is one codebase, found on Google and installable. For many organisations it delivers most of the benefit of an app at much lower cost.
Questions to decide
- How often will each user need this: daily, weekly or rarely?
- Do you need notifications, offline use or phone features?
- Do users log in to see their own information?
- How will people discover it?
- Who will maintain it after launch?
If your answers are "rarely", "no", "no", "Google" and "a small team", start with a website.
Examples
- School: a website for admissions and information; an app for parents if you send daily updates, attendance and fee reminders. See our school website checklist
- Hospital or clinic: a website for doctors, departments and appointments; an app if patients regularly access reports and bookings
- Retailer: an e-commerce website first; an app once you have loyal repeat customers
- News publisher: a fast website first; an app for loyal readers who want notifications
Next step
We build both websites and Android, iOS and cross-platform apps, and will tell you honestly which you need first. See our mobile app development and website design services, or book a free consultation.
