A responsive website is enough when people come occasionally to learn about a service, book, buy or look something up. An app is the more realistic choice when the same user does the same job again and again, needs notifications, the camera, location or offline use, or when the service should become part of a daily routine. Many organisations ask for an app when the real problem is that the website is slow, awkward on a phone, or cannot handle one important action.
A website and an app are not a hierarchy where the app is the next step up. They solve different problems, cost different amounts and need different operations. These are the criteria that help most when deciding.
Start with the user, not the technology
The most useful question is not whether the company should have an app, but who uses the solution, how often and in what situation. A customer who books twice a year has little reason to install an app. An employee logging work in the field several times a day has a very good reason. One business can have both groups, and then the answer is sometimes a website for one and an app for the other.
Most people use only a handful of apps regularly. An app that is opened rarely competes for space with apps used every day, and it needs a clear benefit before anyone bothers to install it. A website has no such barrier. A link in an email, a search result or a QR code opens it instantly.
The website is enough when this is true
- Users mostly arrive from search, email, ads or social media and should be able to finish their task right away.
- The job is to present, book, buy, apply or look up information, and it happens occasionally rather than daily.
- The content needs to be found in search engines, which content inside an app is not in the same way.
- The information must be available without installing anything, for example for visitors, new customers or people at a desktop.
- Updates should go live immediately, without waiting for review and release in the App Store and Google Play.
An app makes sense when this is true
- The user repeats the same task daily or several times a week, and every second spent logging in and searching matters.
- Camera, location, notifications, Bluetooth or offline use are part of the core task rather than nice extras.
- Staff or guests need a tool that is always at hand, for example in the field, in a warehouse or while travelling.
- The service should be a lasting part of daily use, with a signed-in user, history and personal settings.
- The experience needs to be faster and more integrated than a browser allows, such as launching from the home screen and working with the operating system.
Middle paths that are often overlooked
The choice is not always either-or. A progressive web app, or PWA, is a website that can be added to the home screen, works partly offline and can send notifications in most modern browsers. On iPhone, however, the user must first add the site to the home screen before notifications work, so a PWA fits best when notifications are not critical.
Another middle path is to fix the part of the website that matters most: make booking or checkout fast and simple on a phone, simplify login and shorten the path to the key action. That often solves the problem that prompted the app request. If an app is chosen later anyway, the work is not wasted, since a well-built backend and API carry over.
Some products do both. Tímabox, a time-tracking system Novamedia operates, works in the browser and as an iOS and Android app with the same login, because staff often clock in on site. Skilagátt, a data-reception system, deliberately has no app, because a person submitting an application or document should not have to install anything — the browser is enough. In both cases the usage decided the answer.
The cost is different for a reason
A custom website starts with us from 80 hours, or ISK 1,430,400 excluding VAT at our ISK 17,880 hourly rate. A focused first app release starts from 160 hours, or ISK 2,860,800 excluding VAT. The difference comes from the backend and API the app needs, testing on real devices with different screen sizes and OS versions, and the release process in the App Store and Google Play, including review by Apple and Google.
Operations differ too. A website can be updated at any time. An app needs updating when Apple and Google change their requirements or new versions of iOS and Android ship, and every release goes through review. Users also run different app versions at the same time, so the backend must support older versions for a while. Priority operations, at ISK 119,000 per month, is the plan that includes App Store and Google Play release management.
If the website solves the problem, the app is a more expensive path to the same result. If the app is necessary, you are paying for a different surface, not just a smaller screen.
A checklist for the decision
- Describe the main user groups and how often each would use the solution: daily, weekly or a few times a year.
- Write down the one to three actions the solution must handle very well, and test how the current website performs them on a phone.
- Mark whether notifications, camera, location or offline use are essential to the core task or merely desirable.
- Look at where users come from today and whether search engines matter for people finding the service.
- Check whether there is an existing backend or API the app could use, or whether it has to be built from scratch.
- Plan long-term operations, including updates for new iOS and Android versions, and who is responsible for releases.
- Check whether a ready-made product solves the task before committing to a custom build.
Common questions
Can we start with a website and add an app later? Yes, and that is often the most sensible order. If the backend and API are built well from the start, the same foundation serves the app, and the website gives you real data on how people use the service.
Do we need two apps, one for iOS and one for Android? Not necessarily. With a shared codebase, for example in React Native or Flutter, you can release on both platforms from the same code, although you still test on both and some features need platform-specific work.
How long does App Store and Google Play review take? Usually from a few hours to a few days, but new apps and apps with login, payments or sensitive data can receive feedback that has to be addressed. Build that into the release plan.
Can an app work offline? Yes, but it has to be designed that way from the start: what data is stored on the device, how it syncs and what happens when two people change the same item.
How to get started
Start with the checklist and the single action that matters most. If it happens occasionally and users arrive from search or email, a better website is probably the answer. If it is repeated, daily and depends on device features, an app is probably justified.
If you are unsure, Discovery and planning with Novamedia, a fixed ISK 214,560 excluding VAT for 12 hours, can settle the question before you invest in a build. You get prioritised recommendations with an indicative scope, phases and cost estimate, whether the route ends in a website, an app or a ready-made product.